dido:99_annexes:annex-d-requirements:part-02:p2-req-16-8-009

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-8-009 [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-02:p2-req-16-8-009 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P2-REQ-16-8-009 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +The Logical Governance Model SHALL remain independent of repositories, workflow tools, requirements-management systems, policy engines, rules engines, access-control products, ticketing systems, approval systems, configuration systems, and runtime governance services.
 +
 +===== Source =====
 +
 +Part 2, Section 16.8: Logical Governance Requirements.
 +
 +===== Rationale =====
 +
 +The Logical Governance Model defines governance principles rather than governance technologies. Maintaining independence from repositories, workflow systems, policy engines, and other governance tools preserves platform independence and enables multiple implementation environments to realize the same governance model without altering its architectural meaning.
 +
 +===== Applies To =====
 +
 +This requirement applies to the Logical Governance Model and all profiles that realize it.
 +
 +It applies specifically to:
 +
 +  * Logical Governance Model;
 +  * Domain Logical Profiles;
 +  * Implementation Profiles;
 +  * Deployment Profiles; and
 +  * Technology mappings.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Logical Governance Model remains independent of governance technologies and runtime governance services.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * governance responsibilities are defined independently of tooling;
 +  * repositories and workflow systems are not treated as architectural elements;
 +  * technology mappings preserve logical governance semantics; and
 +  * implementation choices do not redefine the Logical Governance Model.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability between the Logical Governance Model and the implementation mechanisms that realize governance while preserving platform independence.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-8-001]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-8-008]]
 +  * [[fxdemo:dido_99_annexes:annex-c-requirements:part-02:p2-req-16-10-007]]
 +
 +Related source section:
 +
 +  * [[fxdemo:02-part:16-logical-requirements:16-8-logical-governance-requirements:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>