This is an old revision of the document!
Change Authorization
Discussion
A Change Authorization is a decision by an Authority that permits a specified Change under stated conditions.
A Change Authorization may identify:
-
The authorized Change
-
The entity that may be changed
-
The permitted alterations
-
The applicable Baseline
-
The effective period
-
The responsible actors or roles
-
Required verification and regression testing
-
Applicable Requirements
-
Applicable Policies
-
Applicable 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
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 Test Executable in a specified Baseline, requires regression testing, and limits the authorization to a stated release window. That decision is the Change Authorization.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.