====== 18.5 Topic Implementation Traceability ======

[[fxdemo:04-part:18-phase-0-implementation-traceability-model:start | Go To Phase 0 Implementation Traceability Model ]]

Topic implementation [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] relates an FX logical Communication Endpoint to the DDS Topic that realizes it.

A topic implementation trace must identify:

  - FX logical Communication Endpoint realized
  - DDS Topic name
  - FX logical information structure carried
  - IDL structure and generated type used
  - Producing implementation participant or [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] Role
  - Consuming implementation participant or Node Role
  - Runtime Plane classification
  - QoS profile family
  - Configuration artifacts used
  - Version and compatibility expectations
  - Traceability record linking the DDS Topic back to Part 3

Topic implementation traceability protects the distinction between logical communication endpoints and DDS Topics. The DDS Topic realizes the endpoint; it does not redefine the endpoint.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>