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:v:version-controlled_condition [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:v:version-controlled_condition [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Version-Controlled Condition ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A version-controlled condition is one in which artifacts are uniquely identified and managed through explicit version identifiers and change control mechanisms. | ||
| + | |||
| + | Version-controlled conditions support traceability, | ||
| + | |||
| + | A version-controlled condition differs from an informal change state. An informal change state lacks governed identification, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //state in which artifacts are uniquely identified and managed through explicit version identifiers and change control mechanisms// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Structured Information Processing [[dido: | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A version-controlled condition provides a controlled basis for determining which artifact version applies in a governed architectural, | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A [[dido: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||