P1-REQ-13-7-007
Statement
Traceability SHALL support backward review from Evidence to conceptual concern.
Source
Part 1, Section 13.7: Traceability Requirements.
Rationale
Backward review allows a reviewer to start with Evidence and follow the trace path back to the conceptual concern it supports. This direction of traceability supports audit, reconstruction, defensibility, and verification of architectural purpose.
This requirement prevents evidence, deployment artifacts, implementation artifacts, and logical elements from existing without a traceable conceptual basis.
Applies To
This requirement applies to traceability relationships that start from Evidence or lower-level artifacts and lead back to conceptual concerns.
It applies specifically to backward review across:
-
Evidence
-
Deployment artifacts
-
Implementation artifacts
-
Logical elements
-
Conceptual concerns
Verification
Verification SHALL confirm that Traceability supports backward review from Evidence to conceptual concern.
Verification activities include review checks confirming that:
-
Evidence traces to the item it supports
-
Supported items trace through deployment, implementation, and logical material where applicable
-
The trace path identifies the related conceptual concern
-
Backward review supports audit and reconstruction
Traceability
Related source section:
Related requirement identifiers:
Status
Draft
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.