Requirements
102 approved requirements, partitioned into five categories. Each requirement
has a stable identifier of the form REQ-CAT-NNN
where CAT is one of the codes below.
| Category | Code | Description | Count |
|---|---|---|---|
| Functional Requirements | REQ-FUN-NNN | Behavioral capabilities the system must provide. | 64 |
| Non-Functional Requirements | REQ-NFR-NNN | Performance, security, reliability, and quality attributes. | 27 |
| Business Requirements | REQ-BUS-NNN | Organizational outcomes and governance constraints. | 3 |
| Stakeholder Requirements | REQ-STK-NNN | Needs traceable to specific stakeholder roles. | 5 |
| Transition Requirements | REQ-TRN-NNN | Migration, rollout, and cutover obligations. | 3 |
REQ-ID convention
REQ-FUN-*— functional capabilities; the verbs the system performs.REQ-NFR-*— non-functional attributes; performance, security, reliability, observability.REQ-BUS-*— business and governance constraints; sponsor authority, approval gates.REQ-STK-*— stakeholder-traceable needs; mapped to specific roles in the stakeholder register.REQ-TRN-*— transition and rollout obligations; migration, pilot, cutover.
IDs are immutable once assigned. Superseded requirements remain in the catalog with a closed status and a relation pointing to the replacement.