Requirements Documentation

Definition

Requirements Documentation captures how individual requirements meet the business needs defined in the business case. It includes functional requirements (what the system/product must do), non-functional requirements (performance, security, usability), acceptance criteria, and traceability to business objectives. The Requirements Traceability Matrix (RTM) links requirements to deliverables, test cases, and business goals — enabling impact analysis when change requests are submitted.

Related concepts

• Scope Domain
• Work Breakdown Structure (WBS)
• Stakeholders Domain
• Planning

Exam angle

• Traceability is required: requirements must be traceable — the RTM connects requirements to scope deliverables; when a change is proposed, the RTM shows what else is affected
• Requirements vs. scope: requirements describe the WHAT (stakeholder needs); scope describes the WORK to deliver it — scope is derived from requirements
• Elicitation techniques: interviews, focus groups, facilitated workshops, prototypes, observations — the exam tests which technique fits which situation

My notes