Use Cases describe specific scenarios where an actor achieves a goal through the system. They bridge business need to system behavior and answer: Who does what, when?

UID prefix: UC- Traces up to: Capabilities (CAP-) Traces down to: Features (FEAT-)

• CAP-000

  1. Capability Template UID: CAP-000 STATUS: Template RELATIONS (Child):

  • UC-000 Use Case Template

  STATEMENT:

  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 UID: UC-000 STATUS: Template RELATIONS (Parent):

• CAP-000 Capability Template

RELATIONS (Child):

• FEAT-000 Feature Template

STATEMENT:

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 UID: FEAT-000 STATUS: Template RELATIONS (Parent):

  • UC-000 Use Case Template

  RELATIONS (Child):

  • FN-000 Function Template
  • DATA-000 Data Entity Template
  • INTF-000 Interface Template

  STATEMENT:

  The system shall provide [feature description].

  Scope: - [included]

  Out of scope: - [excluded]

  Dependencies: [other features or systems required]