P2-REQ-16-8-009

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 realise the same governance model without altering its architectural meaning.

Applies To

This requirement applies to the Logical Governance Model and all profiles that realise it.

It applies specifically to:

Logical Governance Model;Domain Logical Profiles;Implementation Profiles;Deployment Profiles; andTechnology 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; andimplementation choices do not redefine the Logical Governance Model.

Traceability

This requirement supports traceability between the Logical Governance Model and the implementation mechanisms that realise governance while preserving platform independence.

Related requirement identifiers:

Related source section:

Status

Draft

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.