dido:99_annexes:annex-d-requirements:part-02:p2-req-16-9-012

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-02:p2-req-16-9-012 [2026/07/11 12:57] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-02:p2-req-16-9-012 to dido:99_annexes:annex-d-requirements:part-02:p2-req-16-9-012 nick_didodido:99_annexes:annex-d-requirements:part-02:p2-req-16-9-012 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== P2-REQ-16-9-012 ====== ====== P2-REQ-16-9-012 ======
  
-[[dido:99_annexes:annex-c-requirements:part-02:start| Return to Requirements]]+[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
  
 ===== Statement ===== ===== Statement =====
  
-Logical [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] SHALL support later traceability from logical elements to Domain Logical Profile elements, implementation artefacts, deployment artefacts, test scenarios, runtime observations, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] records.+Logical [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] SHALL support later traceability from logical elements to Domain Logical Profile elements, implementation artifacts, deployment artifacts, test scenarios, runtime observations, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] records.
  
 ===== Source ===== ===== Source =====
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-The Logical Architecture serves as the foundation for later architectural products. Maintaining traceability from logical elements to Domain Logical Profiles, implementation artefacts, deployment artefacts, testing, runtime observations, and Evidence records supports lifecycle governance, verification, auditability, and architectural evolution.+The Logical Architecture serves as the foundation for later architectural products. Maintaining traceability from logical elements to Domain Logical Profiles, implementation artifacts, deployment artifacts, testing, runtime observations, and Evidence records supports lifecycle governance, verification, auditability, and architectural evolution.
  
 ===== Applies To ===== ===== Applies To =====
Line 34: Line 34:
 Verification activities should include review checks confirming that: Verification activities should include review checks confirming that:
  
-  * logical elements trace to later architectural artefacts;+  * logical elements trace to later architectural artifacts;
   * deployment and testing relationships are preserved;   * deployment and testing relationships are preserved;
   * runtime observations can be related to logical elements; and   * runtime observations can be related to logical elements; and
Line 45: Line 45:
 Related requirement identifiers: Related requirement identifiers:
  
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-10-001]]+  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-001]]
   * [[fxdemo:dido_99_annexes:annex-c-requirements:part-02:p2-req-16-10-008]]   * [[fxdemo:dido_99_annexes:annex-c-requirements:part-02:p2-req-16-10-008]]
   * [[fxdemo:dido_99_annexes:annex-c-requirements:part-02:p2-req-16-10-010]]   * [[fxdemo:dido_99_annexes:annex-c-requirements:part-02:p2-req-16-10-010]]
  • dido/99_annexes/annex-d-requirements/part-02/p2-req-16-9-012.1783799871.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido