dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-007:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-007:start [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-007:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P1-REQ-13-5-007 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +The Conceptual Architecture SHALL distinguish [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]] from implementation mechanisms.
 +
 +===== Source =====
 +
 +Part 1, Section 13.5: Runtime Plane Requirements.
 +
 +===== Rationale =====
 +
 +Runtime Planes classify runtime communication and behavior by architectural purpose. Implementation mechanisms realize selected aspects of those planes in a particular technology environment.
 +
 +Distinguishing Runtime Planes from implementation mechanisms prevents DDS topics, middleware constructs, APIs, services, scripts, generated types, containers, or other mechanisms from redefining the conceptual plane.
 +
 +===== Applies To =====
 +
 +This requirement applies to all Runtime Plane definitions and references within the Conceptual Architecture.
 +
 +It applies specifically to distinctions between Runtime Planes and:
 +
 +  * Middleware mechanisms
 +  * DDS mechanisms
 +  * APIs
 +  * Services
 +  * Scripts
 +  * Generated types
 +  * Containers
 +  * Deployment tooling
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Conceptual Architecture distinguishes Runtime Planes from implementation mechanisms.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Runtime Planes classify architectural purpose
 +  * Implementation mechanisms realize Runtime Planes without redefining them
 +  * Technology examples do not become conceptual plane definitions
 +  * Later profiles preserve the conceptual meaning of each Runtime Plane
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-5-runtime-plane-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-001: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-2-003:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-004:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>