Requirements Review
Template Library
Requirements Review Template
Review requirements for clarity, traceability, testability, trustworthiness, scope alignment, and readiness to support planning.
ES-102
Review
Quality Gate
Template purpose
Use this template to review the ES-102 requirements package before declaring readiness for planning.
The review should identify ambiguity, missing evidence, scope conflicts, weak verification, AI or governance gaps, and downstream engineering risks.
Project
<Project name>
Document control
| Field |
Value |
| Artifact owner |
<owner> |
| Primary reviewers |
<reviewers> |
| Status |
<draft / in review / accepted / revised> |
| Last updated |
<YYYY-MM-DD> |
| Related Engineering Stage |
ES-102 — Requirements and Constraints |
| Project workspace target |
docs/project-workspace/requirements/requirements_review.md |
| Field |
Value |
| Review Date |
<date> |
| Reviewers |
<names or roles> |
| Requirements Version |
<version or commit> |
| Review Type |
<self / team / peer / instructor / stakeholder / governance> |
| Scope of Review |
<all artifacts / selected artifacts / changes only> |
Artifacts reviewed
| Artifact |
Reviewed? |
Notes |
requirements_overview.md |
<yes / no> |
<notes> |
functional_requirements.md |
<yes / no> |
<notes> |
non_functional_requirements.md |
<yes / no> |
<notes> |
constraints.md |
<yes / no> |
<notes> |
use_cases.md |
<yes / no> |
<notes> |
traceability_matrix.md |
<yes / no> |
<notes> |
Review checklist
- [ ] Requirements align with ES-101 vision evidence.
- [ ] Functional requirements are clear.
- [ ] Non-functional requirements are explicit.
- [ ] Constraints are documented.
- [ ] Major requirements are traceable.
- [ ] Use cases cover major stakeholder goals.
- [ ] AI-related requirements preserve human accountability.
- [ ] Requirements are testable or marked for refinement.
- [ ] Scope conflicts are identified.
- [ ] Data, security, privacy, and governance concerns are visible.
- [ ] Operational and monitoring needs are considered.
- [ ] Open questions are recorded.
Findings
| ID |
Finding |
Severity |
Affected Artifact |
Action |
Owner |
Status |
| RRF-001 |
<finding> |
<low / medium / high> |
<artifact> |
<action> |
<owner> |
<open / closed> |
Ambiguity review
| Requirement / Area |
Ambiguity |
Resolution Needed |
<ID or area> |
<ambiguity> |
<resolution> |
Verification review
| Requirement / Area |
Verification Concern |
Action |
<ID or area> |
<concern> |
<action> |
Scope and constraint review
| Issue |
Impact |
Action |
<scope conflict, constraint conflict, prohibited behavior concern> |
<impact> |
<action> |
AI, trust, and governance review
| Concern |
Requirement / Artifact Affected |
Action |
<AI, oversight, transparency, auditability, safety, privacy, security, fairness, accountability concern> |
<ID or artifact> |
<action> |
Review decision
<Accepted / Accepted with revisions / Not ready>
Required revisions before readiness
| Revision |
Owner |
Due |
<revision> |
<owner> |
<date or stage> |
Reviewer notes
<Optional reviewer comments.>