Skip to content

02-Requirements — Stage completion gate

Version: 0.3 | Project ID: PRJ-001 | Product version / SHA: a6b4429e3165 | Gate date: Pending

Records

  • [ ] 01 Product Requirements Document (PRD) — checklist ../03-Checklists/PRD-Checklist.md complete, or written disposition approved.
  • [ ] 02 Use Case Specification — checklist ../03-Checklists/Use-Case-Specification-Checklist.md complete, or written disposition approved.
  • [ ] 03 User Story — checklist ../03-Checklists/User-Story-Checklist.md complete, or written disposition approved.
  • [ ] 04 Software Requirements Specification (SRS) — checklist ../03-Checklists/Software-Requirements-SRS-Checklist.md complete, or written disposition approved.
  • [ ] 05 Acceptance Criteria — checklist ../03-Checklists/Acceptance-Criteria-Checklist.md complete, or written disposition approved.
  • [ ] 06 PHI Data Inventory and Data Protection Impact Assessment (DPIA) — checklist ../03-Checklists/PHI-Data-Inventory-DPIA-Checklist.md complete, or written disposition approved.
  • [ ] 07 Requirements Traceability Matrix (RTM) — checklist ../03-Checklists/Requirements-Traceability-Matrix-Checklist.md complete, or written disposition approved.
  • [ ] 08 Requirements Change Request — checklist ../03-Checklists/Requirements-Change-Request-Checklist.md complete, or written disposition approved.

Stage exit criteria

  • [ ] Every requirement has a unique REQ- ID, a source and a verification method.
  • [ ] No requirement uses untestable words (fast, user-friendly, robust) without a threshold.
  • [ ] Nonfunctional, security, privacy and (where relevant) clinical-safety and AI requirements are covered.
  • [ ] DPIA is complete and its required controls are in the SRS.
  • [ ] RTM lists every REQ with its planned verification; gaps are flagged.
  • [ ] The requirements baseline is approved and change control is active.

Gate controls

  • [x] All cross-stage links (REQ, DES, API, TC, RISK, REL) used in this stage resolve.
  • [ ] No open critical safety, privacy or security blocker without an authorized written disposition.
  • [x] Product version, commit SHA and record revisions are consistent across the stage.
  • [ ] Gate decision, conditions and approver are stored in the durable system of record.
Role Name Decision Date
Independent reviewer Independent reviewer (name to be assigned — OPEN-021) Pending Pending
Gate approver Sponsor (name to be assigned — OPEN-001) Pending Pending

Gate status, 2026-10-28 (Claude Code): all 8 records drafted (Draft v0.1, a6b4429); the two gate controls ticked were verified by sdlc.py validate and sdlc.py trace. No record is reviewed or approved; open blockers are listed in COMPLETENESS-REPORT.md. The gate decision is for the gate approver.