dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-007:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-007:start [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-007:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P1-REQ-13-7-007 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] SHALL support backward review from [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|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:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-7-traceability-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-001:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-002:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-003:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-004:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-005:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>