Edition 3 at DIS ballot, stage 40.20/ Planning date 12 September 2027, an estimate/ ISO/IEC/IEEE 29148:2018 applies today
ISO 29148 Revision CheckerThe requirements record, clause by clause, and the edition that follows it
A.2.3
ISO/IEC/IEEE 29148:2018
Annex A

Annex A.2.3: OpsCon: referenced documents

Current editionISO/IEC/IEEE 29148:2018, Annex A, A.2.3Edition 3 at DIS ballotNo public change recorded

The OpsCon lists each referenced document's number, title, revision and date.

What annex A.2.3 asks

The OpsCon lists each referenced document's number, title, revision and date. Where a document is not available through normal channels, the source is identified. The reference list is part of the content requirement, not a bibliography added at the end.

Annex A is normative content and part of a full conformance claim.

Why it matters

A reference without a version is a moving target. The clause asks for the revision and the date so a reader can tell which version informed the concept. The source note for an unavailable document is the honest alternative to a bare citation.

In the public record

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 references in a table with number, title, revision, date and source. Update the table when a referenced document changes. Reference the OpsCon itself from the SyRS and the StRS so the chain is visible.

Evidence an assessor asks for

The assessor will pick a reference and ask for the version used. A list with titles only cannot answer.

  • Reference table Number, title, revision, date and source for each referenced document
  • Availability note The source for any document not available through normal channels
  • Update record The date the reference table was last checked against the current documents
  • Cross-reference The SyRS and StRS sections that cite the OpsCon

Where it commonly fails

  • References are cited by title only, with no version or date
  • A referenced document has been superseded and the OpsCon still points at the old version
  • The OpsCon is not referenced from the requirements specifications it informs

What to do before the revision

Put the reference table under the same change control as the OpsCon. A stale reference is a small defect that undermines a large document.

Read across

← A.2.2 OpsCon: scope and system overview A.2.4 OpsCon: the current system or situation →

Full register / Revision record

Source for annex A.2.3: ISO/IEC/IEEE 29148:2018, Annex A.2.3, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.