21.4 Logical Node Mapping Requirements
Go To Phase 0 Implementation Requirements
This section identifies the normative requirements established for mapping FX logical Nodes to Phase 0 implementation artefacts. The canonical requirement statements are maintained in Annex D: Requirements, Part 4, Section 21.4.
Table 21-3: Logical node mapping requirements.
| Requirement ID | Statement |
|---|---|
| P4-REQ-21-4-001 |
The Phase 0 Implementation Profile / PSM SHALL map selected FX logical Nodes to implementation artefacts. |
| P4-REQ-21-4-002 |
Each implementation node artefact SHALL identify the FX logical Node or Nodes it realises. |
| P4-REQ-21-4-003 |
Each implementation node artefact SHALL identify the FX logical Node Role or Roles it performs. |
| P4-REQ-21-4-004 |
Each implementation node artefact SHALL identify the Runtime Plane or Runtime Planes it supports. |
| P4-REQ-21-4-005 |
Each implementation node artefact SHALL identify the DDS Topics, IDL structures, generated types, configuration artefacts, scripts, and supporting modules it uses. |
| P4-REQ-21-4-006 |
Each implementation node artefact SHALL preserve traceability to the relevant Part 3 FX logical Node definition. |
| P4-REQ-21-4-007 |
Each implementation node artefact SHALL follow applicable Phase 0 Developer Handbook rules. |
| P4-REQ-21-4-008 |
Each implementation node artefact SHALL report or record observable behaviour according to the Phase 0 logging and exception-handling baseline. |
| P4-REQ-21-4-009 |
The Phase 0 Implementation Profile / PSM SHALL allow one implementation artefact to realise more than one FX logical Node when the mapping records that choice. |
| P4-REQ-21-4-010 |
The Phase 0 Implementation Profile / PSM SHALL allow more than one implementation artefact to realise one FX logical Node when the mapping records that choice. |
| P4-REQ-21-4-011 |
Runtime packaging SHALL NOT redefine FX logical Nodes or FX logical Node Roles. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.