dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-008: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-008: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-008:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P1-REQ-13-7-008 ======
  
 +[[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 impact analysis across conceptual, logical, implementation, deployment, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] layers.
 +
 +===== Source =====
 +
 +Part 1, Section 13.7: Traceability Requirements.
 +
 +===== Rationale =====
 +
 +Impact analysis depends on traceability across architectural layers. A change to a conceptual concern may affect logical elements, implementation artifacts, deployment artifacts, and evidence. A change to evidence, deployment, implementation, or logical material may also affect the interpretation of architectural support.
 +
 +This requirement supports change control, review, governance, and risk management across the architecture lifecycle.
 +
 +===== Applies To =====
 +
 +This requirement applies to traceability relationships used for impact analysis.
 +
 +It applies specifically to impact analysis across:
 +
 +  * Conceptual layers
 +  * Logical layers
 +  * Implementation layers
 +  * Deployment layers
 +  * Evidence layers
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that Traceability supports impact analysis across conceptual, logical, implementation, deployment, and Evidence layers.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Traceability identifies affected upstream elements
 +  * Traceability identifies affected downstream elements
 +  * Impact analysis spans the required architectural layers
 +  * Impact analysis distinguishes one-to-one, one-to-many, many-to-one, and many-to-many relationships where applicable
 +
 +===== 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-006:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-007:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-009:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>