dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-001

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-02:p2-req-16-6-001 [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-001 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P2-REQ-16-6-001 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +The Logical Architecture / PIM SHALL define the following Logical Runtime Planes:
 +
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Logical Control Plane]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_policy_and_release_plane|Logical Policy and Release Plane]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]]
 +
 +===== Source =====
 +
 +Part 2, Section 16.6: Logical Runtime Plane Requirements.
 +
 +===== Rationale =====
 +
 +The Logical Runtime Plane Model separates architectural responsibilities according to purpose rather than implementation. Defining a standard set of Logical Runtime Planes provides a common architectural foundation for organizing interactions, governance, traceability, and information movement while preserving platform independence.
 +
 +===== Applies To =====
 +
 +This requirement applies to the Logical Runtime Plane Model.
 +
 +It applies specifically to:
 +
 +  * Logical Runtime Planes;
 +  * Logical Nodes;
 +  * Logical Interaction Patterns; and
 +  * Domain Logical Profiles.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Logical Architecture / PIM defines each required Logical Runtime Plane.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * each Logical Runtime Plane is explicitly defined;
 +  * each Runtime Plane has a distinct architectural purpose;
 +  * Runtime Planes remain platform independent; and
 +  * Domain Logical Profiles preserve the inherited Runtime Plane definitions.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability between Logical Runtime Planes, Logical Interaction Patterns, and Logical Nodes.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-002]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-007]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-7-001]]
 +
 +Related source section:
 +
 +  * [[fxdemo:02-part:16-logical-requirements:16-6-logical-runtime-plane-requirements:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>