dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-001: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-001: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-001:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P1-REQ-13-7-001 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +The Conceptual Architecture SHALL define [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] across conceptual elements, logical elements, implementation artifacts, deployment artifacts, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].
 +
 +===== Source =====
 +
 +Part 1, Section 13.7: Traceability Requirements.
 +
 +===== Rationale =====
 +
 +Traceability connects architectural meaning to logical refinement, implementation realization, deployment execution, and evidence support. Defining traceability across these layers supports review, impact analysis, verification, auditability, and controlled evolution of the architecture.
 +
 +This requirement prevents conceptual, logical, implementation, deployment, and evidence material from becoming disconnected or ungoverned.
 +
 +===== Applies To =====
 +
 +This requirement applies to traceability definitions and references within the Conceptual Architecture.
 +
 +It applies specifically to traceability across:
 +
 +  * Conceptual elements
 +  * Logical elements
 +  * Implementation artifacts
 +  * Deployment artifacts
 +  * Evidence
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Conceptual Architecture defines Traceability across conceptual elements, logical elements, implementation artifacts, deployment artifacts, and Evidence.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Traceability spans the required architectural layers
 +  * Traceability relationships identify source and target elements
 +  * Traceability supports review across abstraction levels
 +  * Evidence remains connected to the claims or artifacts it supports
 +
 +===== 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-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>