Requirements Templates¶
Purpose¶
These templates support ES-102 — Requirements and Constraints.
Use this family to define what the system must do, what qualities it must exhibit, what constraints shape the work, what use cases express stakeholder goals, how requirements trace to evidence, and whether planning work may begin.
Recommended workflow¶
Vision Readiness Summary
↓
Requirements Overview
↓
Functional Requirements
↓
Non-Functional Requirements
↓
Constraints
↓
Use Cases
↓
Traceability Matrix
↓
Requirements Review
↓
Requirements Readiness Summary
↓
ES-103 Planning and Work BreakdownCopy location¶
Do not edit the reusable templates directly. Copy completed project versions into:
docs/project-workspace/requirements/
Template set¶
Requirements Overview
Summarize sources, themes, scope alignment, risks, and requirement areas.
02Functional Requirements
Define system behaviors with source, rationale, priority, verification, and acceptance criteria.
03Non-Functional Requirements
Define quality attributes, trustworthiness expectations, operations, security, AI, and governance requirements.
04Constraints
Record technical, data, legal, policy, operational, AI, and governance constraints.
05Use Cases
Describe actor goals, main flows, alternate paths, failures, and evidence produced.
06Traceability Matrix
Connect requirements to source evidence, stakeholders, use cases, verification, and downstream impact.
07Requirements Review
Review clarity, testability, scope alignment, trust implications, and unresolved gaps.
08Requirements Readiness Summary
Summarize readiness to begin ES-103 planning and work breakdown.
Completion expectations¶
| Question | Evidence |
|---|---|
| What vision evidence drives requirements? | requirements_overview.md |
| What must the system do? | functional_requirements.md |
| What qualities and trust properties must the system exhibit? | non_functional_requirements.md |
| What limits or obligations constrain the work? | constraints.md |
| What stakeholder goals and workflows must be supported? | use_cases.md |
| How are requirements traceable? | traceability_matrix.md |
| Have requirements been reviewed? | requirements_review.md |
| Is planning ready to begin? | requirements_readiness_summary.md |
Do not write requirements as implementation tasks. Requirements describe required behavior, qualities, constraints, and evidence needs before planning, architecture, or design decisions are finalized.
Good requirements make later engineering decisions less speculative. They preserve the connection between stakeholder need, system behavior, trust expectation, verification, and downstream impact.