Project Requirement Analysis and Design
Analysis and Design Process covers two major phases of the software development lifecycle. The two phases are often overlapped due to the recursive nature of the requirements. The process usually starts with getting know-how of customer business processes and existing systems, understanding customer needs, expectations, constraints, and elicitation of requirements. Requirements conflicts are removed, and issues and concerns are addressed to develop a clear understanding of customer requirements. These requirements are then used to define the functionality of a proposed system and to determine what the systems are intended to do. System functionality and architecture is documented, and after reviewing internally, communicated to the customer for the purpose of validation. This document then gets mature as a result of customer feedback and serves as the basis for further development.
Maintaining Traceability between requirements and other project’s work product is another important function that ensures the successful control of requirements as well as facilitates to conduct an effective impact analysis when a requirements change request is received.
Analysis and Design Process Diagram
| Role | Activity | Artifacts/Templates | ||
| Project Manager, Development Team Lead, Development Team |  | Understanding of Requirements | | Requirements Specification |
 | ||||
| Development Team Lead, Development Team | | Requirement Analysis | | Analysis and Design Specification |
| ||||
| Development Team Lead, Development Team | | Application Design | | Analysis and Design Specification |
| ||||
| Project Manager/ Development Manager, Quality Assurance Team | | Analysis and Design Review | | Analysis and Design Specification |
| ||||
| Customer | | Analysis and Design Approval | | Analysis and Design Specification |
| ||||
| Assigned Role(s) | | Establish and Maintain Requirement Traceability | | Requirement Traceability Matrix |