33 lines
1.3 KiB
Markdown
33 lines
1.3 KiB
Markdown
# Requirements Document
|
|
|
|
## Introduction
|
|
{{INTRODUCTION}}
|
|
|
|
<!-- Optional when scope could be misread or the feature touches adjacent systems/specs -->
|
|
## Boundary Context (Optional)
|
|
- **In scope**: {{IN_SCOPE_BEHAVIORS}}
|
|
- **Out of scope**: {{OUT_OF_SCOPE_BEHAVIORS}}
|
|
- **Adjacent expectations**: {{ADJACENT_SYSTEM_OR_SPEC_EXPECTATIONS}}
|
|
|
|
## Requirements
|
|
|
|
### Requirement 1: {{REQUIREMENT_AREA_1}}
|
|
<!-- Requirement headings MUST include a leading numeric ID only (for example: "Requirement 1: ...", "1. Overview", "2 Feature: ..."). Alphabetic IDs like "Requirement A" are not allowed. -->
|
|
**Objective:** As a {{ROLE}}, I want {{CAPABILITY}}, so that {{BENEFIT}}
|
|
|
|
#### Acceptance Criteria
|
|
1. When [event], the [system] shall [response/action]
|
|
2. If [trigger], then the [system] shall [response/action]
|
|
3. While [precondition], the [system] shall [response/action]
|
|
4. Where [feature is included], the [system] shall [response/action]
|
|
5. The [system] shall [response/action]
|
|
|
|
### Requirement 2: {{REQUIREMENT_AREA_2}}
|
|
**Objective:** As a {{ROLE}}, I want {{CAPABILITY}}, so that {{BENEFIT}}
|
|
|
|
#### Acceptance Criteria
|
|
1. When [event], the [system] shall [response/action]
|
|
2. When [event] and [condition], the [system] shall [response/action]
|
|
|
|
<!-- Additional requirements follow the same pattern -->
|