38 lines
842 B
Markdown
38 lines
842 B
Markdown
---
|
|
status: draft
|
|
system: <system-slug>
|
|
created: YYYY-MM-DD
|
|
owners:
|
|
- <owner>
|
|
---
|
|
|
|
# <Capability> Requirements
|
|
|
|
## Overview
|
|
|
|
Explain what the capability does and why an actor or consumer needs it. State
|
|
why this system owns the contract when another system exposes the behavior.
|
|
|
|
## Terminology
|
|
|
|
- **Term:** Give a short and precise definition.
|
|
|
|
## Requirements
|
|
|
|
### REQ-<SYSTEM>-<CAPABILITY>-001: <Requirement title>
|
|
|
|
**Intent:** Explain the outcome and its value.
|
|
|
|
**User story:** As a <role>, I want <action>, so that <outcome>.
|
|
|
|
#### Acceptance criteria
|
|
|
|
- **AC-<SYSTEM>-<CAPABILITY>-001.1:** When <condition>, the system shall
|
|
<observable behavior>.
|
|
- **AC-<SYSTEM>-<CAPABILITY>-001.2:** When <condition>, the system shall
|
|
<observable behavior>.
|
|
|
|
## Out of scope
|
|
|
|
- List an explicit exclusion, including adjacent system contracts.
|