top of page
What’s inside
- Purpose and scope. What this builds, for whom, and what is out of scope.
- Stakeholders. Who has a stake, what they need, who signs off.
- Functional requirements. Numbered 'The system shall' statements, each testable.
- Non-functional requirements. Performance, security, reliability and accessibility, with measurable targets.
- Assumptions and acceptance criteria. How you will know each requirement is met.
How to use it
- Agree purpose and scope with stakeholders first.
- Number every requirement so tests can trace back to it.
- Put a number on every non-functional requirement.
- Link acceptance criteria to the Traceability Matrix.
bottom of page