Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-b-terms-and-definitions:a:architectural_governance_layer [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:a:architectural_governance_layer [2026/07/11 11:14] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Architectural Governance Layer ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An architectural governance layer identifies the abstraction layer at which lifecycle control, authority retention, structural governance, and semantic governance are defined. | ||
| + | |||
| + | The architectural governance layer separates governance obligations from implementation technologies. This separation allows the [[dido: | ||
| + | |||
| + | An architectural governance layer differs from an implementation governance mechanism. An implementation governance mechanism realizes governance through a selected technology. The architectural governance layer defines the governance meaning, responsibilities, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Structured Information Processing [[dido: | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | An architectural governance layer provides the basis for defining governance responsibilities before those responsibilities are mapped to implementation technologies. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A [[dido: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||