====== P4-REQ-21-5-010 ====== [[dido:99_annexes:annex-d-requirements:part-04:start| Return to Requirements]] ===== Statement ===== Each DDS Topic mapping SHALL preserve traceability to the Part 3 FX logical Communication Endpoint. ===== Source ===== Part 4, Section 21.5: Communication Endpoint Mapping Requirements. ===== Rationale ===== Each DDS Topic is an implementation realization of a logical communication definition and must remain connected to that authoritative Part 3 source. Preserving traceability prevents Topic names, data representations, QoS profiles, or runtime configuration from becoming disconnected implementation decisions. ===== Applies To ===== This requirement applies to: * DDS Topic mappings; * FX logical Communication Endpoints; * configuration metadata; * mapping tables; and * implementation traceability records. ===== Verification ===== Verification SHALL confirm that each DDS Topic mapping preserves traceability to its applicable Part 3 FX logical Communication Endpoint. Verification activities should include review checks confirming that: * the applicable endpoint is identifiable; * mapping records connect the Topic to its logical source; * changes preserve or explicitly update the traceability relationship; and * reviewers can navigate from DDS Topic to Part 3 endpoint definition. ===== Traceability ===== This requirement establishes backward traceability from Phase 0 DDS Topics to their authoritative Part 3 FX logical Communication Endpoints. 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-009]] * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-5-011]] Related source section: * [[fxdemo:04-part:21-phase-0-implementation-requirements:21-5-communication-endpoint-mapping-requirements:start]] ===== Status ===== Draft ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.