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-001 [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-001 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P2-REQ-16-9-001 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +The Logical Architecture / PIM SHALL define a Logical Traceability Model.
 +
 +===== Source =====
 +
 +Part 2, Section 16.9: Logical Traceability Requirements.
 +
 +===== Rationale =====
 +
 +The Logical Traceability Model establishes the platform-independent relationships that connect logical architectural elements to their conceptual origins and to later implementation, deployment, testing, and evidence artifacts. Defining a Logical Traceability Model ensures that architectural intent remains understandable, reviewable, and governable throughout the architecture lifecycle.
 +
 +===== Applies To =====
 +
 +This requirement applies to the Logical Traceability Model.
 +
 +It applies specifically to:
 +
 +  * Logical Traceability Model;
 +  * Logical Architecture / PIM;
 +  * Domain Logical Profiles; and
 +  * Implementation Profiles.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Logical Architecture / PIM defines a Logical Traceability Model.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * a Logical Traceability Model is explicitly defined;
 +  * traceability relationships are identified;
 +  * the model remains platform independent; and
 +  * later profiles preserve the Logical Traceability Model.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability between the Logical Architecture, its conceptual foundations, and later implementation and deployment artifacts.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-9-002]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-9-003]]
 +  * [[fxdemo:dido_99_annexes:annex-c-requirements:part-02:p2-req-16-10-008]]
 +
 +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>