# Supplementary Specification Template

## Purpose

Capture requirements that are not easily expressed in use cases, including non-functional constraints, regulatory needs,
and domain rules.

## Ownership & Collaboration

- Document Owner: System Analyst
- Contributor Roles: Requirements Reviewer, Software Architect, Test Architect
- Automation Inputs: Vision document, non-functional requirements backlog
- Automation Outputs: `supplementary-spec.md` covering sections 1–14

## Completion Checklist

- All quality attributes quantified where feasible
- Compliance, localization, and operational needs captured
- Traceability maintained to business objectives and risks

## Document Sections

1. **Introduction**
   - State purpose, scope, and intended readership.
2. **Overall Description**
   - Provide context, product perspective, and assumptions.
3. **Functional Requirements**
   - Detail functions not covered by specific use cases.
4. **Usability Requirements**
   - Define accessibility, localization, or ergonomics expectations.
5. **Reliability Requirements**
   - Outline availability, recovery, and fault tolerance targets.
6. **Performance Requirements**
   - Document response times, throughput, scalability, and resource usage.
7. **Supportability Requirements**
   - Describe maintainability, monitoring, deployment, and configurability needs.
8. **Security Requirements**
   - List authentication, authorization, auditing, and privacy constraints.
9. **Compliance and Regulatory Requirements**
   - Capture standards, certifications, or legal requirements.
10. **Environmental Requirements**
    - Note hardware, software, and network constraints.
11. **Design Constraints**
    - Specify mandated technologies, patterns, or coding standards.
12. **Documentation Requirements**
    - Identify user guides, training materials, or API docs required.
13. **Internationalization and Localization**
    - Document language support, locale handling, and cultural considerations.
14. **Assumptions, Dependencies, and Open Issues**
    - Record outstanding questions and related risks.

## Agent Notes

- Use measurable statements; avoid vague adjectives.
- Cross-reference risk list entries when a requirement mitigates a known risk.
- Coordinate with Architecture and QA to maintain consistency across artifacts.
- Verify the Automation Outputs entry is satisfied before signaling completion.