Annex D: Requirements Traceability
Annex D maps the canonical leaf requirements in Annex C: Requirements to the Crucible pages that reference them.
Annex C remains the canonical source for requirement titles, Statements, rationale, and verification information. Annex D provides traceability links and coverage information without restating or redefining the requirements.
Requirements Traceability Index
The Requirements Traceability Index lists the canonical leaf requirements alphabetically by title.
The Requirement Title column links to the canonical requirement page. The Referenced By column identifies the Crucible pages that link to that requirement.
A requirement with no references requires review to determine whether:
-
The requirement lacks ConOps coverage
-
The requirement belongs outside the ConOps
-
The requirement represents a future capability
-
The requirement page or backlink is incomplete
-
The requirement requires an additional operational page
Notes for Editors
-
Each requirement title is displayed from the canonical requirement page
-
Do not add custom display text to requirement links
-
Confirm the canonical page title and namespace for each requirement
-
Add every remaining Annex C leaf requirement
-
Exclude true parent requirements that contain child requirements
-
Retain
startfor leaf requirements implemented as namespace index pages -
Sort the completed table alphabetically by the displayed canonical page title
-
Treat a requirement with no returned backlinks as requiring coverage review
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
Notes for Editors
-
Confirm each displayed title against the canonical requirement page
-
Add every remaining Annex C leaf requirement
-
Exclude parent requirements that contain child requirements
-
Retain
startfor leaf requirements implemented as namespace index pages -
Sort the final table alphabetically by canonical displayed title
-
A requirement with no returned backlinks requires coverage review
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
Contents
Traceability Rules
The traceability information follows these rules:
-
Include only canonical leaf requirements
-
Treat a requirement implemented as a namespace
startpage as a leaf when it has no child requirements -
Exclude parent requirements that have leaf children
-
Link each requirement title to its canonical Annex C page
-
Sort the Requirements Traceability Index alphabetically by displayed title
-
Identify every Crucible page that directly references the requirement
-
Do not copy or paraphrase the canonical requirement Statement
-
Record requirements without references as uncovered until reviewed
-
Record ConOps pages without supporting requirements as unsupported until reviewed
Coverage Status
Detailed traceability pages can use the following coverage statuses:
| Status | Meaning |
|---|---|
| Complete | The referenced Crucible content provides operational coverage consistent with the requirement Statement |
| Partial | The referenced content addresses only part of the requirement Statement |
| Not Covered | No current Crucible page provides identifiable coverage |
| Outside ConOps Scope | The requirement applies to another specification, design, implementation, verification, or governance artifact |
| Future Capability | The requirement applies to a capability outside the current operational baseline |
| Review Required | The available requirement or coverage information is insufficient to determine the appropriate status |
Relationship to Annex E
Annex E: Issues records problems discovered during traceability review.
Examples include:
-
A requirement without operational coverage
-
A ConOps capability without a supporting requirement
-
A requirement that requires further decomposition
-
An ambiguous or incomplete requirement Statement
-
An incorrect parent or leaf classification
-
A missing requirement page
-
An inconsistent requirement namespace or title
-
A proposed future capability
Annex D records the traceability condition. Annex E records the issue and its resolution status.
Notes for Editors
Populate the Requirements Traceability Index only after confirming the complete Annex C leaf-requirement inventory.
Do not list true parent requirements when their leaf children provide the normative Statements.
Where a leaf requirement uses a namespace start page for numerical ordering, link to the actual start page.
The Referenced By column should derive from direct links to the canonical requirement page wherever the available DokuWiki backlink mechanism permits dynamic generation.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.