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] – removed - external edit (Unknown date) 127.0.0.1dido: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 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== 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 artifacts, deployment artifacts, test scenarios, runtime observations, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] records.
 +
 +===== Source =====
 +
 +Part 2, Section 16.9: Logical Traceability Requirements.
 +
 +===== Rationale =====
 +
 +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 =====
 +
 +This requirement applies to the Logical Traceability Model.
 +
 +It applies specifically to:
 +
 +  * Domain Logical Profiles;
 +  * Implementation Profiles;
 +  * Deployment Profiles;
 +  * Test scenarios;
 +  * Runtime observations; and
 +  * Evidence records.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that Logical Traceability supports later lifecycle traceability.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * logical elements trace to later architectural artifacts;
 +  * deployment and testing relationships are preserved;
 +  * runtime observations can be related to logical elements; and
 +  * Evidence records maintain architectural context.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability from the Logical Architecture throughout implementation, deployment, testing, operations, and evidence collection.
 +
 +Related requirement identifiers:
 +
 +  * [[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-010]]
 +
 +Related source section:
 +
 +  * [[fxdemo:02-part:16-logical-requirements:16-9-logical-traceability-requirements:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>