Traceability SHALL support backward review from Evidence to conceptual concern.
Part 1, Section 13.7: Traceability Requirements.
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.
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:
Verification SHALL confirm that Traceability supports backward review from Evidence to conceptual concern.
Verification activities include review checks confirming that:
Related source section:
Related requirement identifiers:
Draft
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.