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:g:governance_constraint [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:g:governance_constraint [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Governance Constraint ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A governance constraint identifies a rule or control mechanism governing the definition, modification, | ||
| + | |||
| + | Governance constraints support the retention of authority, lifecycle control, semantic and structural consistency, | ||
| + | |||
| + | A governance constraint differs from an implementation constraint. An implementation constraint is a limit or condition imposed by a selected technology, product, language, runtime, or deployment environment. A governance constraint defines control over architectural meaning, structure, lifecycle, and authority within the [[dido: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //rule or control mechanism governing the definition, modification, | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Structured Information Processing [[dido: | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A governance constraint preserves controlled meaning, structure, lifecycle, and authority for architectural artifacts. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A governance constraint requires approved authority review before a [[fxdemo: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||