This phase is the main focus of our project managers and software engineers. Meeting with managers, stake holders and users are held in order to gather and analyze your business unique requirements. After the requirements are gathered from the client, a scope document is created in which the scope of the project is determined and documented.
In this phase the software design is prepared from the requirement specifications which were studied in the first phase. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture. The system design specifications serve as input for the next phase of the model.
During this phase, systems are developed or acquired based on detailed design specifications. Since, in this phase the code is produced so it is the main focus for the developer. This is the longest phase of the software development life cycle.
The system is validated through a sequence of unit, integration, performance, system, and acceptance testing. The objective is to ensure that the system functions as expected and that sponsor’s requirements are satisfied. All system components, communications, applications, procedures, and associated documentation are developed/acquired, tested, and integrated. This phase requires strong user participation in order to verify thorough testing of all requirements and to meet all business needs.
During this phase, the new or enhanced system is installed first in the laboratory environment, users are trained, data is converted (as needed), the system is turned over to the sponsor, and business processes are evaluated. This phase includes efforts required to implement, resolve system problems identified during the implementation process, and plan for sustainment.
Every step in the project is documented for future reference and for the improvement of the software in the development process.
After successful testing the product is delivered / deployed to the production environment for the customer’s use.
Software maintenance is done for future reference. Software improvement and new requirements (change requests) can take longer than the time needed to create the initial development of the software.