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-014: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-014:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P1-REQ-13-5-014 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] SHALL support later logical realization through policy enforcement, policy decision, policy administration, policy information, obligation, release, and audit/evidence capabilities.
 +
 +===== Source =====
 +
 +Part 1, Section 13.5: Runtime Plane Requirements.
 +
 +===== Rationale =====
 +
 +The Conceptual Architecture defines the Policy and Release Plane before later logical realization. Policy enforcement, policy decision, policy administration, policy information, obligation, release, and audit/evidence capabilities provide logical refinement paths for the conceptual plane.
 +
 +This requirement supports later logical modeling while preserving the conceptual distinction between runtime plane purpose and logical capability design.
 +
 +===== Applies To =====
 +
 +This requirement applies to Policy and Release Plane definitions and references within the Conceptual Architecture.
 +
 +It applies specifically to later logical realization through:
 +
 +  * Policy enforcement
 +  * Policy decision
 +  * Policy administration
 +  * Policy information
 +  * Obligation
 +  * Release
 +  * Audit/evidence capabilities
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Policy and Release Plane supports later logical realization through the identified capabilities.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Policy enforcement maps to Policy and Release Plane purpose
 +  * Policy decision maps to Policy and Release Plane purpose
 +  * Policy administration maps to Policy and Release Plane purpose
 +  * Policy information maps to Policy and Release Plane purpose
 +  * Obligation, release, and audit/evidence capabilities map to Policy and Release Plane purpose
 +  * Later logical capabilities do not redefine the conceptual 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-005:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-013:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-010:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-006:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>