3. REQUIREMENTS AND ANALYSIS
Proper Requirement analysis and specification is critical for any project.
The primary objective of this phase is to create a Software requirement
specification document(SRS) which has all the details of the customer’s
requirements.
Exit Criteria: Software Requirement Specification document(SRS)
4. DESIGN
There are two design phases:
High level Design
Logical view of the software is designed.
Entry criteria: SRS
Exit criteria: Functional architechture, Database design
Low level Design
Detailed design phase. Modules are designed
Entry criteria: HLD
Exit criteria: Functional specification document, unit test plans
5. DEVELOPMENT
This is the coding phase.
Coding is done based on the project functional specifications in any
programming language.
Certain industry standards are followed by the project team.
Entry criteria: Functional specification document
Exit criteria: programs ready for unit testing
6. TESTING
This is the phase where the actual product/module is tested against the
requirements. It has four basic phases.
Unit Testing
Unit testing is testing the individual units/modules of source code
Usually done by developers
Integration Testing
Testing after integrating one or more modules
System Testing
Testing the complete product by validating it against the user needs
Entry criteria: Programs/modules, test plan, test cases
Exit criteria: Test execution reports
7. DEPLOYMENT
Here the product is testing in the operational environment.
Acceptance testing is done by the user to ensure it passes the
acceptance criteria
Once it is accepted, it is deployed in customer’s production environment.
Entry criteria: Tested software
Exit criteria: Customer sign off
8. MAINTENANCE
Once the software is installed in customer’s environment, it should be
maintained regularly and should be upgraded with any other new
specifications.
