Logical Endpoint Traceability [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Logical Endpoint Traceability ======

[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]]

===== Discussion =====

Logical Endpoint Traceability relates a Logical Communication Endpoint to its participating Logical Nodes, Communication Roles, Logical Data Structure Definitions, Runtime Plane classification, governance constraints, and evidence expectations.

Logical Endpoint Traceability supports review of information movement. It identifies which Logical Nodes produce information, which Logical Nodes consume information, which information structures the endpoint carries, which Runtime Plane frames the exchange, and which constraints or evidence expectations apply.

Logical Endpoint Traceability also protects the distinction between logical endpoints and implementation mechanisms. A later implementation profile maps a Logical Communication Endpoint to a selected technology, but the logical endpoint remains the architectural relationship to trace.

===== Definition =====

//Traceability relationship connecting a Logical Communication Endpoint to participating Nodes, Communication Roles, information structures, Runtime Planes, governance constraints, and evidence expectations.//

===== Source =====

Specialization of Communication Endpoint, Runtime Plane, Data Structure Definition, Traceability, and Evidence from Part 1, Sections 7.6, 7.5, 7.7, 7.10, and 7.9; generalised from endpoint, topic, publish/subscribe, and interaction material in the original FX Demo Reference Architecture.

===== Note =====

Logical Endpoint Traceability does not imply a DDS Topic, REST resource, RPC method, message queue, event stream, file, or network route.

===== Example =====

A logical Node Status endpoint traces to reporting Logical Nodes, the Health Monitoring Node, the Node Status definition, the Logical Health and Observability Plane, and evidence expectations for operational review.

----

[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]]

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>