====== P1-REQ-13-9-005 ======

[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]

===== Statement =====

The [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Architecture]] / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] SHALL NOT bind logical elements to [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]], [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]], [[dido:99_annexes:annex-b-terms-and-definitions:p:python|Python]], [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes|Kubernetes]], [[dido:99_annexes:annex-b-terms-and-definitions:k:k3s|K3s]], [[dido:99_annexes:annex-b-terms-and-definitions:d:docker|Docker]], [[dido:99_annexes:annex-b-terms-and-definitions:r:rti_connext_dds|RTI Connext DDS]], [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|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, 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 =====

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

===== Traceability =====

Related source section:

  * [[fxdemo:01-part:13-conceptual-requirements:13-9-relationship-to-logical-architecture-pim-requirements]]

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-004:start]]
  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-003:start]]
  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-008:start]]
  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-003:start]]

===== Status =====

Draft

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>