- Assessment
- Market assay
- Specification
Before starting work, we conduct an analysis of clients’ business, target audience and competitors’ products. A list of functional requirements, software advantages and software peculiarities is being prepared. Based on the data, a specification is developed that contains the description of all functional peculiarities of the software being developed. The price-list, the estimate and the project schedule of the software development are formed.
- Conclusion af a contract
- Prototyping
- Specifications
After signing the contract, the business analyst starts prototyping the future product. Detailed interactive prototypes are prepared with an explanation of all the peculiarities and structure of the program. The main elements of the UI concept are developed and approved with the client.
After prototyping, a detailed technical task is formed with a description of the using technologies and the functionality of site. The technical task is agreed with the client what is a part of the contract.
- Web Design
- Mobile Design
- Design approval
A designer develops a UX concept of software product on the grounds of developed and agreed prototypes. All unique templates of design are prepared in the PSD file format. The designer also makes the concept of vision logic for working with mobile and laptop devices.
Sources of approved design templates are transferred to the customer.
- HTML and CSS
- Front-end
- Back-end
Based on the developed design, HTML coding of design templates is made and the front-end logic is programmed, if it necessary. Layout is created in accordance with W3C standards and agreed requirements for cross-browser work of the project.
The prepared layout templates are integrated with the selected back-end system in accordance with the development specifications.
- Functional QA
- Automated QA
- Test-drive development
The developed software goes through several stages of testing if necessary. We chose testing that the most closely corresponds to the budget and the result. Simple projects are tested by the functional method. For projects that are more complex, we use automated testing. If necessary, we can develop the product initially in the TDD paradigm.
- 4 hours of training with the product
- Wiki document
- Swagger files
After finishing the development, the responsible specialists of the client take a course on how to work with the software product. Wiki documentation on the necessary features and distinctions is being prepared. If the system is working with the API, we prepare the documentation and Swagger files.
- 2 year software warranty
- Preparation of acts
- Closing the contract
- Documentation
- Source
- Intellectual property
- Assessment
- Market assay
- Specification
- Conclusion af a contract
- Prototyping
- Specifications
- Web Design
- Mobile Design
- Design approval
Before starting work, we conduct an analysis of clients’ business, target audience and competitors’ products. A list of functional requirements, software advantages and software peculiarities is being prepared. Based on the data, a specification is developed that contains the description of all functional peculiarities of the software being developed. The price-list, the estimate and the project schedule of the software development are formed.
After signing the contract, the business analyst starts prototyping the future product. Detailed interactive prototypes are prepared with an explanation of all the peculiarities and structure of the program. The main elements of the UI concept are developed and approved with the client.
After prototyping, a detailed technical task is formed with a description of the using technologies and the functionality of site. The technical task is agreed with the client what is a part of the contract.
A designer develops a UX concept of software product on the grounds of developed and agreed prototypes. All unique templates of design are prepared in the PSD file format. The designer also makes the concept of vision logic for working with mobile and laptop devices.
Sources of approved design templates are transferred to the customer.
- HTML and CSS
- Front-end
- Back-end
- Functional QA
- Automated QA
- est-drive development
- 4 hours of training with the product
- Wiki document
- Swagger files
Based on the developed design, HTML coding of design templates is made and the front-end logic is programmed, if it necessary. Layout is created in accordance with W3C standards and agreed requirements for cross-browser work of the project.
The prepared layout templates are integrated with the selected back-end system in accordance with the development specifications.
The developed software goes through several stages of testing if necessary. We chose testing that the most closely corresponds to the budget and the result. Simple projects are tested by the functional method. For projects that are more complex, we use automated testing. If necessary, we can develop the product initially in the TDD paradigm.
After finishing the development, the responsible specialists of the client take a course on how to work with the software product. Wiki documentation on the necessary features and distinctions is being prepared. If the system is working with the API, we prepare the documentation and Swagger files.
The developed software goes through several stages of testing if necessary. We chose testing that the most closely corresponds to the budget and the result. Simple projects are tested by the functional method. For projects that are more complex, we use automated testing. If necessary, we can develop the product initially in the TDD paradigm.
After finishing the development, the responsible specialists of the client take a course on how to work with the software product. Wiki documentation on the necessary features and distinctions is being prepared. If the system is working with the API, we prepare the documentation and Swagger files.
- 2 year software warranty
- Preparation of acts
- Closing the contract
- Documentation
- Source
- Intellectual property