public:99_annexes:annex-b-terms-and-definitions:c:change_authorization

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
public:99_annexes:annex-b-terms-and-definitions:c:change_authorization [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:c:change_authorization [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Change Authorization ======
 +
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Change Authorization is a decision by an [[public:99_annexes:annex-b-terms-and-definitions:a:authority|Authority]] that permits a specified [[public:99_annexes:annex-b-terms-and-definitions:c:change|Change]] under stated conditions.
 +
 +A Change Authorization may identify:
 +
 +  * The authorized Change
 +  * The entity that may be changed
 +  * The permitted alterations
 +  * The applicable [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]
 +  * The effective period
 +  * The responsible actors or roles
 +  * Required verification and regression testing
 +  * Applicable [[public:99_annexes:annex-b-terms-and-definitions:r:requirement|Requirements]]
 +  * Applicable [[public:99_annexes:annex-b-terms-and-definitions:p:policy|Policies]]
 +  * Applicable [[public:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraints]]
 +  * Conditions, limitations, or exceptions
 +
 +A Change Authorization may permit a Change without requiring that the Change be implemented. An authorized Change may subsequently be deferred, canceled, superseded, or allowed to expire.
 +
 +===== Definition =====
 +
 +//decision by an authority permitting a specified change under stated conditions//
 +
 +===== Source =====
 +
 +Dido Solutions, Inc. and Jackrabbit Consulting, Inc., derived from the change-control and configuration-management concepts in ISO/IEC/IEEE 12207:2017 and ISO 10007:2017
 +
 +===== Note =====
 +
 +A Change Authorization is issued by an Authority. DIDO-TE may record, validate, and enforce the authorization but does not invent the authorization or silently substitute another Authority.
 +
 +The stated conditions establish the scope within which the Change is permitted. A separate “Authorized Change Scope” term is unnecessary because that scope is part of the Change Authorization.
 +
 +A Change Authorization should remain distinguishable from:
 +
 +  * A proposed Change
 +  * A request for authorization
 +  * An implemented Change
 +  * A verification result
 +  * A [[public:99_annexes:annex-b-terms-and-definitions:m:maintenance_outcome|Maintenance Outcome]]
 +
 +Conflicting Change Authorizations are recorded and surfaced without DIDO-TE inventing precedence. The appropriate Community of Interest or designated Authority resolves the conflict.
 +
 +===== Example =====
 +
 +An Authority permits replacement of an identified [[public:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]] in a specified Baseline, requires regression testing, and limits the authorization to a stated release window. That decision is the Change Authorization.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>