Annex A.2.8: OpsCon: appendices and glossary
The appendices carry material that supports the concept but would interrupt the main text: detailed data, a glossary, a list of abbreviations, supporting analysis and references to related documents.
What annex A.2.8 asks
The appendices carry material that supports the concept but would interrupt the main text: detailed data, a glossary, a list of abbreviations, supporting analysis and references to related documents. The glossary defines the terms used by the OpsCon, and the abbreviations list makes the document readable without a separate key.
Annex A is normative content and part of a full conformance claim.
Why it matters
The appendices are not optional decoration when the concept uses specialist terms. A glossary that is missing or inconsistent with the requirements specifications causes review defects. The clause expects the supporting material to be part of the controlled document.
No clause level change is public for this unit; the DIS keeps the title and scope, and the requirement text is not released.
What good looks like
Keep the glossary in one place and reuse it across the OpsCon and the requirements specifications. Add an abbreviation the first time it is used. Put long tables in an appendix and reference them from the text.
Evidence an assessor asks for
The assessor will check that a term in the OpsCon means the same thing in the SyRS. A glossary that is not shared is a source of defects.
- Glossary The terms used by the OpsCon, with one meaning for each, consistent with the specifications
- Abbreviations The abbreviations and acronyms, with the expanded form
- Supporting analysis The detailed tables, models or studies that support the concept
- Related documents The documents that carry the detail, with the version and date
Where it commonly fails
- The glossary is copied from another project and does not match the current terms
- An abbreviation is used before it is defined
- The supporting analysis is referenced but not included or available
What to do before the revision
Make the glossary a shared artefact across the four items. One glossary is cheaper than four inconsistent ones.
Read across
- A.2.1 OpsCon: general, title and preface
- 9.2 General content
- 9.2 General content
- 7 The required information items
← A.2.7 OpsCon: impacts and analysis B Annex B: concept of operations guidance →
Source for annex A.2.8: ISO/IEC/IEEE 29148:2018, Annex A.2.8, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.