|
PROJECT PHASES:
|
|
|
|
|
|
|
|
|
|
Names
|
|
|
Goal
|
|
|
Deliverable
|
|
|
|
|
|
|
|
|
|
|
|
Defining |
|
|
Define project scope, budget, time frame
|
|
|
Vision, Software Development Plan, Project Schedule, Requirements Document
|
|
|
|
|
|
|
|
|
|
|
|
Designing |
|
|
Define the software architecture, create the first prototype of the system
|
|
|
Prototype 1. Software Architecture Document
|
|
|
|
|
|
|
|
|
|
|
|
Development |
|
|
Implement base system functionality (work with database)
|
|
|
Alfa. Code Review Reports
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Develop advanced functionality, interfaces to the other systems
|
|
|
Candidate. Code Review Reports
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Create decorations, like reporting, importing, exporting, help engine, localization
|
|
|
Release. Code Review Reports
|
|
|
|
|
|
|
|
|
|
|
|
Transition |
|
|
Help with installation at the Customer side, with the acceptance testing being carried out by the Customer
|
|
|
Accepted system
|
|
|
|
|
|
|
|
|
|
|
|
Support |
|
|
Fix all the arising problems
|
|
|
Support and Maintenance
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
USUALLY WE PASS THE FOLLOWING STEPS APPROACHING A NEW PROJECT:
|
|
|
|
|
|
|
|
|
|
|
|
STEP 1
|
|
|
NDA
|
|
|
We understand that all information related to your business is confidential, so we always execute NDA before moving forward.
|
|
|
|
|
|
|
|
|
|
REQUEST FOR PROPOSAL
|
|
|
You send us the specifications of your project for estimation. These can be either detailed like a complete functional specification, or general like your business needs description. Our analysts will then assist you in defining the requirements by asking further questions.
|
|
|
|
|
|
|
|
|
TECHNO-COMMERCIAL PROPOSAL
|
|
|
AMSOL estimates your request and submits to you a no-obligation business proposal containing a rough estimation of project costs and suggesting pricing model for approval.
|
|
|
|
|
|
|
|
|
AGREEMENT
|
|
|
Both sides sign an official agreement defining all the aspects of sides’ interaction, level of services, terms of payments etc.
|
|
|
|
|
STEP 2
|
|
|
SOFTWARE ARCHITECTURE
|
|
|
Our analysts are always in close interaction with customer representatives because understanding your requirements correctly means 50% of success in your project. Of course it is impossible to define all the nuances of the project on its first phase, so the process of requirements detailing is built iteratively.
|
|
|
|
|
|
|
|
|
PROTOTYPE DEMO
|
|
|
It is always essential to see how the system you've planned to get will look like.
|
|
|
|
|
STEP 3 |
|
|
IMPLEMENTATION
|
|
|
The stage of transferring project requirements into a working system, i.e. an actual code writing process.
|
|
|
|
|
STEP 4 |
|
|
ACCEPTANCE TEST
|
|
|
Evaluation of code reliability and application stability checks. We utilize feature freezes and clean all remaining bugs.
|
|
|
|
|
STEP 5 |
|
|
SUPPORT AND MAINTENANCE
|
|
|
After the project is completed we enter the support phase. Its duration should be defined in the Agreement. Usually it means that during the support phase all arising problems will be fixed for free.
|
|
|
|
|
|
|
|
|