1. Requirement phase:A clear understanding of the application features from the perspective of stakeholders is established through stakeholders' collaboration. Stakeholders’ collaboration in this phase can determine the efficiency of the outcome. For that reason this collaboration is one of the most important aspects of this phase. As a result initial requirements documents are created. 2. Design phase:Based on the inputs from the requirement analysis phase, HTML Prototype will be created. The requirement analysis phase's inputs will be converted to HTML prototype, UML diagrams to depict data and object layers, and sequence diagrams for complex logic. 3. Development phase:The HTML Prototype, mock-ups and diagrams will guide development phase from the requirement analysis and design phases. Codes are generated based on the previous phases. 4. Quality Assurance and Testing phase:Quality management will be reinsured by weekly internal review and short milestones review with the stakeholders. Although the Quality Assurance team will monitor the product right from the requirement analysis phase, they will come into full swing once the development is nearing completion. They carry out manual and automatic data feeding tests and stress tests. 5. Maintenance phase:Stakeholders will be actively monitoring each progress and once they are completed and satisfied with the features, the system is ready to be deployed. Software training and support is also an important deliverable of this phase. Once deployed, the team is ready to maintain and enhance the system to cope with newly discovered requirements and problems, if any. |
|
| Copyright © 2008 - 2011 Al-Badi For Solutions Pvt. Ltd. |
