Requirement Analysis Phases
The Overall Requirements Engineering Sub-Process
Requirement Analysis (as part of the broader Requirements Engineering process) is typically broken into these sequential phases:
1. Requirement Elicitation / Gathering
Collect raw requirements from stakeholders using interviews, questionnaires, observation, JAD sessions, etc.
2. Requirement Analysis (Classification & Negotiation)
- Organize and classify gathered requirements (functional/non-functional)
- Identify and resolve conflicts between stakeholders
- Prioritize requirements
- Remove ambiguity and redundancy
3. Requirement Modeling
Represent requirements visually/formally using:
- Data Flow Diagrams (DFD)
- Decision Tables / Decision Trees
- Entity-Relationship (ER) Diagrams
- Use Case Diagrams
4. Requirement Specification (Documentation)
Compile the analyzed and modeled requirements into a formal Software Requirements Specification (SRS) document, following a standard (e.g., IEEE 830).
5. Requirement Validation
- Review the SRS with stakeholders to confirm correctness and completeness
- Check requirements against the characteristics of a good requirement (correct, unambiguous, complete, consistent, verifiable, etc.)
- Conduct formal walkthroughs/inspections
6. Requirement Management
- Track changes over the project lifetime
- Maintain a Requirements Traceability Matrix (RTM)
- Handle evolving/volatile requirements through change control
Elicitation → Analysis → Modeling → Specification → Validation → Management
Exam tip: This is essentially the full Requirements Engineering process — draw it as a simple flow diagram with the 6 phases, since it's often asked as "Explain the phases of Requirement Analysis/Requirements Engineering."