aiwg
Version:
Cognitive architecture for AI-augmented software development with structured memory, ensemble validation, and closed-loop correction. FAIR-aligned artifacts, 84% cost reduction via human-in-the-loop, standards adopted by 100+ organizations.
78 lines (45 loc) • 2.37 kB
Markdown
# Supplementary Business Specification Template
## Cover Page
- ``Project Name``
- `Supplementary Business Specification`
- `Version`1.0``
## Revision History
| Date | Version | Description | Author |
| --- | --- | --- | --- |
| ``dd/mmm/yy``|``x.x``|`<details>`|`<name>` |
## Ownership & Collaboration
- Document Owner: Business Process Analyst
- Contributor Roles: System Analyst, Requirements Reviewer, Project Manager
- Automation Inputs: Business rules inventory, compliance obligations, charter goals
- Automation Outputs: `supplementary-business-spec.md` covering sections 1–6
## 1 Introduction
> Provide an overview of the document, including purpose, scope, terminology, references, and structure.
### 1.1 Purpose
> State why this supplementary business specification exists.
### 1.2 Scope
> Describe the scope of this document, the models it supports, and affected business areas.
### 1.3 Definitions, Acronyms, and Abbreviations
> Reference or record terminology needed to interpret the specification.
### 1.4 References
> List supporting documents with title, identifier, date, and source.
### 1.5 Overview
> Explain the remainder of the document and how it is organized.
## 2 Behavior
> Summarize organization-wide behavioral goals not linked to a single business use case.
## 3 Usability
> Capture usability requirements from the perspective of business actors (e.g., training time, task completion targets).
## 4 Reliability
> Document reliability expectations such as availability, accuracy, and fault tolerance for business operations.
## 5 Performance
> Record performance characteristics (response time, throughput, capacity, resource utilization) and associate them with
> relevant business use cases.
## 6 Scaling Issues
> Describe anticipated growth, scaling constraints, and considerations the organization must address.
## Appendices (Optional)
> Attach supporting analyses, calculations, or reference materials if needed.
## Agent Notes
- Keep each requirement measurable and tied back to the business vision objectives.
- Update related business rules or glossary entries when terminology changes.
- Verify the Automation Outputs entry is satisfied before signaling completion.
- Tie each requirement to measurable objectives or policy constraints.
- Synchronize updates with business rules and glossary entries.