P4-REQ-21-4-004

Return to Requirements

Each implementation node artefact SHALL identify the Runtime Plane or Runtime Planes it supports.

Part 4, Section 21.4: Logical Node Mapping Requirements.

Runtime Plane identification preserves separation of concerns in the implementation profile. It makes clear whether an implementation artefact supports Control, Data, Health and Observability, Policy and Release, Audit and Provenance, or another applicable Runtime Plane concern.

Explicit Runtime Plane mapping also supports communication, logging, exception-handling, and later deployment and evidence planning.

This requirement applies to:

• implementation node artefacts;
• Runtime Plane mappings;
• DDS Topic mappings;
• QoS mappings; and
• applicable logging and exception-handling conventions.

Verification SHALL confirm that each implementation node artefact identifies the Runtime Plane or Runtime Planes it supports.

Verification activities should include review checks confirming that:

• applicable Runtime Planes are explicitly identified;
• Runtime Plane mappings agree with Part 3;
• multi-plane support is recorded where applicable; and
• implementation mechanisms do not collapse distinct Runtime Plane concerns.

This requirement connects implementation node artefacts to the Runtime Plane classifications defined by the FX Demo Logical Profile.

Related requirement identifiers:

• P4-REQ-21-4-005
• P4-REQ-21-4-008

Related source section:

• 21.4 Logical Node Mapping Requirements

Draft