P3-REQ-17-7-008

The FX Demo Logical Profile SHALL distinguish FX Runtime Planes from DDS domains, DDS topics, DDS partitions, REST resource groups, RPC service groups, message queues, event streams, Kubernetes namespaces, network segments, security zones, deployment environments, and runtime configuration groupings.

Part 3, Section 17.7: FX Runtime Plane Requirements.

FX Runtime Planes are logical architectural constructs that organize responsibilities according to architectural purpose. Technologies such as DDS domains, DDS topics, DDS partitions, REST resource groups, RPC service groups, Kubernetes namespaces, network segments, security zones, deployment environments, and runtime configuration groupings are implementation mechanisms that may realize one or more Runtime Planes but do not define their architectural meaning.

Maintaining this distinction preserves platform independence and allows multiple Implementation Profiles to realize the same Runtime Plane architecture using different deployment and communication technologies while maintaining architectural consistency.

This requirement applies to every FX Runtime Plane defined within the FX Demo Logical Profile.

It applies specifically to:

  • Runtime Plane architecture;
  • platform-independent modeling;
  • Implementation Profile development;
  • architectural conformance reviews; and
  • architectural governance.

Verification SHALL confirm that Runtime Planes are defined independently of implementation-specific runtime constructs.

Verification activities should include review checks confirming that:

  • Runtime Planes are not represented as implementation technologies;
  • implementation constructs are treated as realizations rather than architectural definitions;
  • platform independence is preserved; and
  • Runtime Plane responsibilities remain clearly separated from deployment and runtime technologies.

This requirement preserves the separation between conceptual architecture, logical Runtime Plane architecture, and implementation-specific runtime constructs established throughout Parts 1, 2, and 3.

Related requirement identifiers:

Related source section:

Draft


© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

  • dido/99_annexes/annex-d-requirements/part-03/p3-req-17-7-008.txt
  • Last modified: 2026/07/21 15:37
  • by owen