P1-REQ-13-9-005

Return to Part 1 Requirements

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.

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

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.

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

It applies specifically to avoiding binding to:

• DDS
• IDL
• Python
• Kubernetes
• K3s
• Docker
• RTI Connext DDS
• Crucible
• Other implementation-specific mechanisms

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 bindings
• PIM elements avoid platform-specific technology dependencies
• Implementation technologies appear only in implementation profiles
• Technology mappings preserve logical meaning without redefining it

Related source section:

• 13.9 Relationship to Logical Architecture / PIM Requirements

Related requirement identifiers:

• P1-REQ-13-9-004
• P1-REQ-13-2-003
• P1-REQ-13-5-008
• P1-REQ-13-7-003

Draft