Requirement Catalog Template¶
Usage¶
Use this table as the canonical requirement register linked to stories, use cases, risks, and releases.
Requirement Registry¶
Req ID |
Source Story |
Source Use Case |
Requirement Statement |
Type |
Priority |
CP |
KPI Link |
Risk Link |
Release |
Owner |
Verification |
Status |
|---|
Type Definitions¶
FNC: Functional behaviorNFR: Reliability, performance, security, availability, or scalabilityOPS: Operational process and support behaviorCMP: Compliance, legal, privacy, or policy controlDAT: Instrumentation, analytics, reporting, and data quality
Priority Definitions¶
P0: Launch blocker, gate blocker, or legal/compliance blockerP1: High-value requirement needed for committed outcomeP2: Valuable enhancement that can be sequenced laterP3: Optional optimization
Readiness Checklist¶
Source story/use case linked
Measurable acceptance criteria defined
Verification method assigned
KPI link assigned
Risk link assigned
Priority and CP tag assigned
Release target assigned
Status Definitions¶
IntakeDiscovery ValidatedReadyIn ProgressIn ReviewQA ValidatedRelease ReadyReleased