Revision History

Go to Terms and Definitions

A Revision History identifies the Revisions of an 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

history identifying the revisions of an artifact and the relationships that order those revisions over time

Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

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.

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.