public:99_annexes:annex-b-terms-and-definitions:r:revision_history

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:r:revision_history [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:r:revision_history [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Revision History ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Revision History identifies the [[public:99_annexes:annex-b-terms-and-definitions:r:revision|Revisions]] of an [[public:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] and the relationships that order those Revisions over time.
 +
 +A Revision History may identify:
 +
 +  * Each Revision
 +  * The content associated with each Revision
 +  * The immediately preceding Revision
 +  * The immediately succeeding Revision
 +  * Branching relationships
 +  * Merging relationships
 +  * Change authors
 +  * Change timestamps
 +  * Change descriptions
 +  * Approval or release states
 +
 +The applicable requirements determine the required Revision History content.
 +
 +A Revision History allows an actor or process to:
 +
 +  * Distinguish Artifact states
 +  * Determine the order of Revisions
 +  * Identify a preceding Revision
 +  * Compare Revisions
 +  * Retrieve an identified Revision
 +  * Reconstruct an earlier Artifact state
 +  * Determine how an Artifact changed over time
 +
 +A Revision History differs from a Revision:
 +
 +  * A Revision identifies one distinguishable Artifact state
 +  * A Revision History identifies multiple Revisions and the relationships among them
 +
 +===== Definition =====
 +
 +//history identifying the revisions of an artifact and the relationships that order those revisions over time//
 +
 +===== Source =====
 +
 +Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +===== Note =====
 +
 +A Revision History may be linear or may include branches and merges.
 +
 +A Revision History does not by itself establish:
 +
 +  * Approval of a Revision
 +  * Release of a Revision
 +  * Authorization to deploy a Revision
 +  * Required retention periods
 +  * The reason a Revision was accepted or rejected
 +
 +Separate governance and lifecycle controls establish those conditions.
 +
 +===== Example =====
 +
 +The Revision History of an Infrastructure Configuration identifies Revisions 1, 2, and 3 and records that Revision 2 succeeds Revision 1 and Revision 3 succeeds Revision 2.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>