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

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-005 [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-005 [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P2-REQ-16-9-005 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:l:logical_endpoint_traceability|Logical Endpoint Traceability]] SHALL relate a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoint]] to participating [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_role|Communication Roles]], information structures, Runtime Planes, governance constraints, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations.
 +
 +===== Source =====
 +
 +Part 2, Section 16.9: Logical Traceability Requirements.
 +
 +===== Rationale =====
 +
 +Logical Endpoint Traceability establishes the complete architectural context for each Logical Communication Endpoint. Relating endpoints to participating Nodes, communication roles, information structures, Runtime Planes, governance constraints, and Evidence expectations supports architectural review, interoperability analysis, governance, and lifecycle management.
 +
 +===== Applies To =====
 +
 +This requirement applies to Logical Endpoint Traceability.
 +
 +It applies specifically to:
 +
 +  * Logical Communication Endpoints;
 +  * Logical Nodes;
 +  * Communication Roles;
 +  * Logical Runtime Planes; and
 +  * Governance relationships.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that Logical Endpoint Traceability relates each Logical Communication Endpoint to its participating architectural elements.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * participating Nodes and Communication Roles are identified;
 +  * information structures are traceable;
 +  * Runtime Plane participation is identified; and
 +  * governance constraints and Evidence expectations are preserved.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability between Logical Communication Endpoints and the architectural elements that participate in each interaction.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-001]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-7-004]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-9-006]]
 +
 +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>