====== P4-REQ-21-14-006 ====== [[dido:99_annexes:annex-d-requirements:part-04:start| Return to Requirements]] ===== Statement ===== Topic implementation traceability SHALL relate FX logical Communication Endpoints to DDS Topics. ===== Source ===== Part 4, Section 21.14: Implementation Traceability Requirements. ===== Rationale ===== DDS Topics provide the selected Phase 0 implementation realization of FX logical Communication Endpoints. Explicit Topic traceability allows reviewers to determine which logical endpoint a DDS Topic realizes while preserving the distinction between the logical communication definition and its DDS implementation mechanism. ===== Applies To ===== This requirement applies to: * FX logical Communication Endpoints; * DDS Topics; * Topic mappings; and * associated implementation participants and configuration. ===== Verification ===== Verification SHALL confirm that Topic implementation traceability relates FX logical Communication Endpoints to DDS Topics. Verification activities should include review checks confirming that: * each governed DDS Topic mapping identifies its logical endpoint; * each implemented endpoint has an identifiable DDS Topic mapping; * mappings are reviewable in both directions; and * DDS Topics do not redefine their logical endpoints. ===== Traceability ===== This requirement establishes implementation traceability between FX logical Communication Endpoints and their Phase 0 DDS Topic realizations. Related requirement identifiers: * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-5-001]] * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-5-002]] * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-5-010]] * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-14-003]] Related source section: * [[fxdemo:04-part:21-phase-0-implementation-requirements:21-14-implementation-traceability-requirements:start]] ===== Status ===== Draft ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.