Untitled Project
Search
Found 9 results.
Clear query
META-001
1. UID Format META-001

All requirements SHALL use the format PREFIX-NNN where: - PREFIX is the type code (CAP, UC, FEAT, FN, DATA, INTF) - NNN is a zero-padded sequential number within that type - UIDs are immutable once assigned

META-002
2. Traceability Convention META-002

Source code referencing a requirement SHALL include a comment with the UID and a verb: - impl -- this code implements the requirement - verify -- this code tests/verifies the requirement - depends -- this code depends on the requirement - related -- this code is related to the requirement

META-003
3. Status Values META-003

Requirements SHALL use one of these statuses: - Draft -- under development, not yet reviewed - Active -- approved and in effect - Obsolete -- superseded or no longer applicable - Template -- example/placeholder, not a real requirement

CAP-000
1. Capability Template CAP-000

The organization shall be able to [capability description].

Business justification: [why this capability matters] Stakeholders: [who benefits] Priority: [critical / high / medium / low]

UC-000
1. Use Case Template UC-000

As a [role], I want to [action], So that [benefit].

Preconditions: - [what must be true before]

Main Flow: 1. [step] 2. [step] 3. [step]

Postconditions: - [what is true after]

Acceptance criteria: - [testable condition] - [testable condition]

FEAT-000
1. Feature Template FEAT-000

The system shall provide [feature description].

Scope: - [included]

Out of scope: - [excluded]

Dependencies: [other features or systems required]

FN-000
1. Function Template FN-000

The system SHALL [specific measurable behavior].

Input: [what triggers this] Output: [what the system produces] Constraints: [timing, format, limits] Verification method: [test / inspection / analysis / demonstration]

DATA-000
1. Data Entity Template DATA-000

The system shall maintain [Entity Name] records with:

Attributes: - [attribute]: [type] [constraints]

Relationships: - [belongs to / has many] [Other Entity]

Constraints: - [uniqueness, validation rules]

Lifecycle: - Created when: [event] - Deleted when: [event or retention policy]

Volume estimate: [expected record count] Sensitive data: [yes/no]

INTF-000
1. Interface Template INTF-000

The system shall integrate with [external system] to [purpose].

Direction: [inbound / outbound / bidirectional] Protocol: [REST / GraphQL / SMTP / webhook / file transfer] Authentication: [API key / OAuth / certificate] Data exchanged: [what flows in/out] Frequency: [real-time / batch / on-demand] Fallback behavior: [what happens when unavailable]