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

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 [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:c:change [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Change ======
 +
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Change is an alteration to an identifiable entity. The term is intentionally general so it can be applied consistently across software, hardware, data, Configurations, Test Assets, documentation, Requirements, Policies, and other governed entities.
 +
 +A Change may alter:
 +
 +  * Content
 +  * Structure
 +  * Behavior
 +  * [[public:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
 +  * Relationships
 +  * Interfaces
 +  * State
 +  * Deployment
 +  * Applicable constraints
 +
 +A Change may be proposed, assessed, authorized, implemented, verified, rejected, deferred, canceled, superseded, or rolled back. These descriptions indicate the state or disposition of the Change and do not create different kinds of Change.
 +
 +===== Definition =====
 +
 +//alteration to an identifiable entity//
 +
 +===== Source =====
 +
 +Dido Solutions, Inc. and Jackrabbit Consulting, Inc., derived from the change and configuration-management concepts in ISO/IEC/IEEE 12207:2017 and ISO 10007:2017
 +
 +===== Note =====
 +
 +A Change identifies what is altered. It does not, by itself, indicate that the alteration is authorized, implemented, successful, acceptable, or incorporated into a [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]].
 +
 +A proposed Change describes an alteration submitted for consideration. An authorized Change is permitted by a [[public:99_annexes:annex-b-terms-and-definitions:c:change_authorization|Change Authorization]]. An implemented Change describes an alteration that was made to the applicable entity.
 +
 +The actual alteration may differ from the proposed or authorized Change because implementation may fail, stop early, be partially completed, or be rolled back. DIDO-TE preserves these distinctions through [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] and [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]].
 +
 +===== Example =====
 +
 +Replacing one [[public:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]] version with another is a Change to a [[public:99_annexes:annex-b-terms-and-definitions:t:test_asset|Test Asset]]. The Change is not authorized merely because it has been proposed or technically prepared.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>