P2-REQ-16-6-007

Return to Requirements

Statement

The Logical Architecture / PIM SHALL distinguish Logical 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.

Source

Part 2, Section 16.6: Logical Runtime Plane Requirements.

Rationale

Logical Runtime Planes classify architectural responsibilities rather than implementation mechanisms. Preserving this distinction allows multiple implementation technologies and deployment environments to realise the same Runtime Plane Model without changing its architectural meaning.

Applies To

This requirement applies to the Logical Runtime Plane Model and all profiles that realise it.

It applies specifically to:

Logical Runtime Planes;Domain Logical Profiles;Implementation Profiles;Deployment Profiles; andTechnology mappings.

Verification

Verification SHALL confirm that Logical Runtime Planes remain distinct from implementation groupings.

Verification activities should include review checks confirming that:

Runtime Planes are defined independently of implementation technologies;deployment mechanisms do not redefine Runtime Planes;technology mappings preserve Runtime Plane semantics; andimplementation groupings remain separate from logical classifications.

Traceability

This requirement supports traceability between Logical Runtime Planes and the implementation mechanisms that realise them while preserving platform independence.

Related requirement identifiers:

Related source section:

Status

Draft

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