P4-REQ-21-7-008

Return to Requirements

Implementation mechanisms SHALL NOT collapse Runtime Plane distinctions.

Part 4, Section 21.7: Runtime Plane Realization Requirements.

Implementation mechanisms such as DDS, shared modules, common logging, repository groupings, or runtime packaging may support multiple architectural concerns. Those mechanisms must not become a substitute for the Runtime Plane distinctions defined by the logical architecture.

This constraint preserves separation of concerns even when Phase 0 uses shared implementation technologies or artifacts.

This requirement applies to:

• DDS Topics and QoS profiles;
• shared modules;
• runtime packaging;
• logging and exception-handling mechanisms;
• repository organization; and
• implementation participant mappings.

Verification SHALL confirm that Phase 0 implementation mechanisms do not collapse Runtime Plane distinctions.

Verification activities should include review checks confirming that:

• distinct Runtime Plane purposes remain identifiable;
• shared mechanisms retain plane-specific mappings where applicable;
• configuration does not erase Runtime Plane classifications;
• runtime packaging does not redefine plane boundaries; and
• review records can distinguish implementation concerns by Runtime Plane.

This requirement preserves the Runtime Plane separation defined by the FX Demo Logical Profile throughout the Phase 0 implementation baseline.

Related requirement identifiers:

• P4-REQ-21-7-001
• P4-REQ-21-7-007
• P4-REQ-21-3-009

Related source section:

• 21.7 Runtime Plane Realization Requirements

Draft