P1-REQ-13-9-005

Return to Part 1 Requirements

Statement

The Logical Architecture / PIM SHALL NOT bind logical elements to DDS, IDL, Python, Kubernetes, K3s, Docker, RTI Connext DDS, Crucible, or other implementation-specific mechanisms.

Source

Part 1, Section 13.9: Relationship to Logical Architecture / PIM Requirements.

Rationale

DDS, IDL, Python, Kubernetes, K3s, Docker, RTI Connext DDS, Crucible, and similar mechanisms belong to implementation or deployment concerns. The Logical Architecture / PIM remains independent of these mechanisms so that later implementation profiles select and map technologies without changing logical meaning.

This requirement prevents implementation selections from entering the Logical Architecture / PIM as logical definitions.

Applies To

This requirement applies to Logical Architecture / PIM elements, relationships, behaviours, and constraints.

It applies specifically to avoiding binding to:

DDSIDLPythonKubernetesK3sDockerRTI Connext DDSCrucibleOther implementation-specific mechanisms

Verification

Verification SHALL confirm that the Logical Architecture / PIM does not bind logical elements to DDS, IDL, Python, Kubernetes, K3s, Docker, RTI Connext DDS, Crucible, or other implementation-specific mechanisms.

Verification activities include review checks confirming that:

Logical elements avoid implementation-specific bindingsPIM elements avoid platform-specific technology dependenciesImplementation technologies appear only in implementation profilesTechnology mappings preserve logical meaning without redefining it

Traceability

Related source section:

Related requirement identifiers:

Status

Draft

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