Computools approach

Computools will guide you with strategic advice on technology, your business goals and operations to adopt the right IT Strategy with the best return on technology investment.

Defining goals

  1. Researching the main idea of ​​the project.
  2. Exploring the high-level main goals of the project.
  3. Identifying project stakeholders, including the hidden ones. Hidden stakeholders can be participants of a project interested in a client’s business who are not clearly represented to the team, that can be state and international regulatory authorities, public organizations, non-obvious participants influencing users of the service directly or indirectly, ​including others.
    • Identifying stakeholders’ goals.
    • Adjustment of high-level goals while taking into account the stakeholders' goals. In order to minimize differences in project vision and move in the right direction, it is critical for the team to clearly understand and share the client’s goals.
  4. Determining all of the client's primary high-level expectations, which are known at this stage.
  5. Vision synchronization of this unit with the client.
  6. Identifying all User Roles and key User Stores.
  7. Gaining access to industry insights from Computools experienced professionals to place you at a competitive advantage and minimize the risk of costly errors.
  8. Building strong communication to ensure that everyone is on the same page that is essential to success. This is done by forming a glossary of project terms.
    • Computools prepares agendas before each meeting and records results in a summary. This summary is shared to all team members in a general channel. This allows the team and client to save time and minimizes human factor and the negative impact of it.
    • Сommonly-accepted terminology in the industry reduces miscommunication.
  9. Forming a complete list of roles.

Analysis & exploration

  1. Creating user stories based on company knowledge and experience.
  2. Researching competitors' existing solutions and technologies.
  3. Researching the groups of client needs to clarify the best user experience.
  4. Analyzing data, ready-made solutions on the market, their real (and not declared) pros and cons as well as who use them.
  5. Decomposing user stories to user roles based on the results of research. Visualizing a tree of user roles, stories and cases via MindMap.
  6. Defining main restrictions and providing solutions for them.
    • system licensing and other legal requirements
    • corporate policies
    • localizations
    • peak number of users online
    • permissible downtime
    • requirements to fail-safe feature
    • requirements to scalability based on potential customer base growth
    • requirements to system expansion speed
      1. modularity
      2. extensibility
      3. code reusability
    • requirements to delivery speed
      1. release delivery speed
      2. speed of certain groups of fixes
      3. replacement speed of certain content or logic (often when using the admin panel or CMS)
    • requirements to security level
      1. system access security level
      2. level of software protection from solution-vendor (operating systems, application servers, VM, etc.)
      3. DDoS Protection
      4. Data encryption in storage
      5. User data protection
      6. Phishing Protection
      7. protection against unique content copying
      8. security analysis of third-party dependencies
      9. other additional options
    • sizes and types of information that will need to be stored
    • repository security requirements
    • system response speed: average and minimum
      1. common
      2. at certain critical points of the system
    • list of end-user devices (device types, operating systems, input device screen extensions, etc.)
    • server device list of client's business to which transfer may be required
    • requirements to external protocols, formats and interfaces
    • reliability requirements
      1. logging
      2. backups
    • system support features
      1. logging
      2. testing (automatic, manual). It includes both coverage and speed of testing cycles
    • domain specific restrictions and requirements
    • general UI and UX design requirement
  7. Identifying the main transitive requirements, such as migration, learning complexity and speed.
  8. Identifying the main risks.

Contact Us

Let's talk about your project.
Use the form to drop a line or write us an e-mail:

Thank you for your message! Your request will be carefully researched by our experts. We will get in touch with you within one business day.

Why Computools?


Access to niche expertise and solutions that focus on quality, efficiency and saving time.


Trusted innovation management and performance valued by world experts at the IMP³rove Academy.

ISO 9001:2015

Certified processes according to international standards and backed by experience.


Access to a multi-technology environment that enhances product development.


Security in knowing that you never have to question where you're at or what's happening in the development process.


Gain stability with a partner who believes in long-term relationships and views it as a fundamental value.


Work with teams that have your business goals in mind. Each step is a step towards improving your overall business processes.


Low staff turnover by to geography and leadership in the region.


A number of International association memberships allow us to understand your needs no matter where in the world you're located.


Collaboration with professionals IT associations and the knowledge exchange that come with it, keep us an industry leader in IT development.


Confidence in the fact that we are respected as global IT-experts with awards and recognitions to prove it.


Regular internal seminars, training, and workshops contribute to the continuous improvement of Computools's engineers and analysts.