COMPANY REGULATIONS

1. Preparatory stage

Cybor Holding (hereinafter referred to as the Developer) offers the Customer work in a comfortable environment for him - uses the “Jira” program and instant messengers to ensure high-quality communication. The key to a successful partnership at this stage is the Developer's ability to hear and take into account the Customer's expectations.

2. Analytics

At this stage, the Customer and the Developer determine the goals to be achieved during development, set business tasks, user requirements, etc. This process takes place in a dialogue format, the participation of both parties is important here. Sometimes the Customer may be unaware of some of the nuances of product development and it turns out in the process of collecting information. The task of the Developer is to foresee all possible risks and offer options for optimizing the development process. The more details the Customer announces, the more accurately the terms of reference will be drawn up and, accordingly, the better the final result will be.

3. Evaluation of the project

The collected data is analyzed and on their basis a product model is created that is equally understandable to both the Customer and the Developer. Next step is the calculation of the preliminary time and labor costs required to create the product. The result of this stage is a presentation that describes in detail the assessment of the project, possible risks, the team for working on the project, various options for implementing tasks, conditions, stages and other details.

4. Projecting

When all issues on the preliminary assessment are settled, the design phase begins, which includes sub-stages:

4.1. Development of a project map with indication of defining points for reconciliation of results;

4.2. Software architecture design;

4.3. Choice of technology stack - development tools that include programming languages, frameworks, database management systems, compilers, etc.

5. Design

After the analytics are completed, the project is evaluated and agreed, the developers can move on to design. This stage includes two blocks:

5.1. UX development - user interface design. UX is responsible for the logic of building system elements, adaptability and usability of the product.

5.2. UI development - drawing interface elements: blocks, buttons, icons, which are assembled into a ready-made layout.

6. Development

This stage involves the implementation of the Customer's ideas already formalized into practical steps (sprints). The developer, in accordance with the project map, carries out the work and presents the Customer the result of each part. Development in the sprint format is convenient and efficient, because allows you to quickly collect feedback, respond to changes and make changes. This approach is based on an agile methodology and is called iterative.

7. Testing

Testing a software product is one of the most important stages in the process of its development. A company must be 100% sure that it will work before the presentation of a new product to consumers. Therefore, it is so important to identify critical bugs in time, check the functionality of the product, conduct a full analysis and implement recommendations for improvement.

To do this, QA engineers can use various methods of testing an IT product: modular, integration, functional, acceptance.

8. Launch

After the testing is done and the bugs are fixed, the finished product will be launched. If earlier the product was available only to a narrow circle of developers and quality control specialists, now it will be a meeting with real users. At this stage, monitoring tools are also set up to help understanding user’s behavior and refine the product, if necessary.

9. Transfer of rights

When the launch is done - the developers have completed their part of the work and transfer the finished product to the owner. At this stage, control over the software part and documentation is completely transferred to the Customer. Detailed conditions for the transfer of rights are prescribed in the cooperation agreement between the Customer and the Development Company.

10. Technical support

After the completion of the work, the product, as a rule, needs further technical support. At this stage, the Developer offers temporary or permanent support in order to reduce the risk of failures after the launch of the new system and ensure rapid recovery in case of problems. Temporary maintenance involves the elimination of possible shortcomings for a limited period. Permanent technical support is convenient if you need to regularly receive the latest software updates. In this case, possible failures must be eliminated quickly and imperceptibly for the customer and users.