Skip to content

Software Requirements Specification (SRS) — Completion checklist

Template: TPL-02-04 ../02-Templates/Software-Requirements-SRS-Template.md | Version: 0.3
How to use: tick an item only after inspecting the completed record and its evidence. Every unticked item needs an OPEN- entry with an owner, or a written, approved disposition.

Content checks

  • [ ] 01. System boundary and operating context — Every external system named appears in the interfaces section.
  • [ ] 02. Atomic functional requirements with REQ IDs — Each REQ is atomic, uses 'shall', traces to a source and names a verification method (test, inspection, analysis, demonstration).
  • [ ] 03. Input and output specifications — Every input has type, range and invalid-input behavior.
  • [ ] 04. Performance availability reliability constraints — Each has a number, percentile/period and load condition.
  • [ ] 05. Usability and accessibility needs — Accessibility target is named (e.g. WCAG 2.2 AA) and safety wording is specified exactly.
  • [ ] 06. Interfaces and security requirements — Each DPIA control and each external interface has a REQ.
  • [ ] 07. Error handling and negative behaviors — Every exception flow in the use cases maps to a REQ.
  • [ ] 08. Measurable verification criteria — Every REQ has a criterion a tester can apply without interpretation.
  • [ ] 09. Baselining and change control — Baseline is versioned and changes go through the change-request template.

Record control checks

  • [x] Document ID follows KAI-<PRODUCT>-SRS-NNN and is unique in the product.
  • [x] Product, version and commit SHA match the related records.
  • [x] No placeholder rows remain; every gap names an owner and an OPEN- item.
  • [x] Every cited link, file path and ID resolves.
  • [ ] Security, privacy, AI/ML and medical-software applicability checked and routed to qualified reviewers where relevant.
  • [x] No patient identifiers, secrets or production data copied into the record.
  • [x] Nothing was taken from the worked examples as if it were evidence.
  • [ ] Named independent reviewer completed review; approval recorded with date.

Reviewer: Technical reviewer (name to be assigned — OPEN-001) | Date: Pending | Outcome: [Complete / Returned with actions]

Self-check by Claude Code, 2026-10-28, at a6b4429. Ticked items were verified mechanically in this session: sdlc.py validate 0 errors (75 records, stages 01–10); sdlc.py trace no duplicate IDs and every REQ linked to design and test; code citations resolve at a6b4429 (except files in the separate Visionary_oral_ML repository, labelled as external). Content checks are left for the named reviewer; every gap is an owned OPEN- item in the record. Reviewer and approval items are for people.