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.
47 lines (34 loc) • 1.76 kB
Markdown
# Business Glossary Template
## Purpose
Maintain a shared vocabulary for business and system stakeholders to reduce ambiguity during requirements and design
work.
## Ownership & Collaboration
- Document Owner: Business Process Analyst
- Contributor Roles: System Analyst, Environment Engineer
- Automation Inputs: Domain terminology list, stakeholder definitions
- Automation Outputs: `business-glossary.md` table with canonical terms
## Completion Checklist
- Terms are sorted alphabetically or by domain
- Definitions are concise (<2 sentences) and reference authoritative sources
- Synonyms, acronyms, and ownership information captured
## Document Sections
1. **Glossary Management Overview**
- Describe update cadence, reviewer roles, and approval workflow.
2. **Term Table**
- Use the table format below and extend as needed.
| Term | Definition | Source/Owner | Notes |
| --- | --- | --- | --- |
| Example Term | Brief definition of the concept. | Team or document reference. | Usage clarifications or links. |
1. **Acronyms and Abbreviations**
- List acronyms with expansions and context.
2. **Retired or Replaced Terms**
- Track terminology that should no longer be used and the replacements.
3. **Open Questions**
- Capture terms requiring clarification or stakeholder decision.
## Agent Notes
- Keep formatting consistent; avoid multi-paragraph definitions.
- Reference source documents by relative path where possible.
- Coordinate updates with Requirements and Architecture disciplines to prevent drift.
- Verify the Automation Outputs entry is satisfied before signaling completion.
- Maintain alphabetical order and include sources for each definition.
- Retire obsolete terms in the dedicated subsection to prevent reuse.