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
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-001:start [2026/07/11 12:57] – ↷ Links adapted because of a move operation nick_didodido: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 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-The Conceptual Architecture SHALL define [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] across conceptual elements, logical elements, implementation artefacts, deployment artefacts, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].+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 ===== ===== Source =====
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-Traceability connects architectural meaning to logical refinement, implementation realisation, deployment execution, and evidence support. Defining traceability across these layers supports review, impact analysis, verification, auditability, and controlled evolution of the architecture.+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. This requirement prevents conceptual, logical, implementation, deployment, and evidence material from becoming disconnected or ungoverned.
Line 25: Line 25:
   * Conceptual elements   * Conceptual elements
   * Logical elements   * Logical elements
-  * Implementation artefacts +  * Implementation artifacts 
-  * Deployment artefacts+  * Deployment artifacts
   * Evidence   * Evidence
  
 ===== Verification ===== ===== Verification =====
  
-Verification SHALL confirm that the Conceptual Architecture defines Traceability across conceptual elements, logical elements, implementation artefacts, deployment artefacts, and Evidence.+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: Verification activities include review checks confirming that:
Line 38: Line 38:
   * Traceability relationships identify source and target elements   * Traceability relationships identify source and target elements
   * Traceability supports review across abstraction levels   * Traceability supports review across abstraction levels
-  * Evidence remains connected to the claims or artefacts it supports+  * Evidence remains connected to the claims or artifacts it supports
  
 ===== Traceability ===== ===== Traceability =====
  • dido/99_annexes/annex-d-requirements/part-01/p1-req-13-7-001/start.1783799874.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido