|
|
|
SOFTWARE DEVELOPMENT LIFE CYCLE |
| |
The framework aims for projects to consistently perform a well-defined engineering process that integrates all the software engineering activities to produce correct, consistent software products or applications effectively and efficiently. It encompasses the engineering tasks, conducted in accordance with the project's defined software process and appropriate methods and tools, to build and maintain the software application. |
| |
1. Requirements Definition and Analysis |
| |
The Business Analyst (BA), in close coordination with the client’s process owners, captures the detailed business requirements, going through a requirements gathering cycle, after which, the BA comes up with the Functional Specifications Document. There is a verification and validation of the document first with peers and then with the client to ensure the completeness, clarity, and accuracy of the document. |
| |
The Solutions Architect then defines multiple alternative solutions for the business requirements documented in the approved Functional Specs, and would then recommend the most feasible solution. There is also a verification and validation process for this document. |
| |
2. Design and Test Planning |
| |
The chosen solution will be further detailed down during Design Phase where the Solutions Architect establishes the technical details. At the same time, the Product Test Lead creates the Test Plan, which details the testing scope, strategies, resources, and timetable. It also defines the user acceptance criteria. |
| |
Peer review processes the functional specifications documents. Design and test plans are very important steps to ensure that all the requirements are clearly understood by the project team, that the design is optimal, and that the plans are correct. These steps ensure system quality as defects are corrected early on, preventing costly and time-consuming modifications downstream. |
| |
3. Implementation, Test Preparation, and Test Execution |
| |
The development team codes the requirements during implementation phase. The team follows coding standards to ensure efficiency and maintainability of the code. Senior software engineers and peers then review the code. |
| |
While initial development is ongoing, the product test team designs the test cases and scripts. Once the development team releases their work to the product test team, the test team validates the system and tracks defects through a bug-tracking tool. The product test team will declare that the system is ready for user acceptance test once the system is defect-free. |
| |
The development team also prepares the documentation requirements such as user’s manuals, training materials, and system administrator’s guides. |
| |
4. User Acceptance Test |
| |
The product test team then guides the users through a final verification of the system. The users will validate that the system meets each requirement, and will ensure correctness and accuracy. Should there still be defects, these are again tracked by the product test team, and quickly resolved by the development team. |
| |
5. Support and Maintenance |
| |
When the system is delivered, pertinent documents are released to the users and trainings are conducted. The project team will provide support to the users from user acceptance testing, production deployment to data migration. The project team is also available during the warranty period to conduct maintenance activities pursuant to the agreement with IntelliTech. |
| |
| |
| |
