MO-005c — Infrastructure Baseline Revision Control

Go to MO-005 — Reusable and Version-Controlled Infrastructure Baselines

Crucible SHALL maintain each Infrastructure Baseline under Version Control.

This requirement derives from:

• MO-005 — Reusable and Version-Controlled Infrastructure Baselines

The Original Requirement states:

The system SHALL establish infrastructure as a reusable and version-controlled asset.[C1]

MO-005c preserves the portion of the Original Requirement that requires infrastructure to be version controlled by identifying the controlled subject as an Infrastructure Baseline.

The separate requirements derived from MO-005 address:

• MO-005a — Infrastructure Baseline Artifact Management
• MO-005b — Infrastructure Baseline Identification
• MO-005d — Approved Infrastructure Baseline Selection
• MO-005e — Infrastructure Baseline Reuse
• MO-005f — Approved Infrastructure Baseline Preservation
• MO-005g — Infrastructure Deployment Baseline Traceability

Version Control preserves the revision history of an Infrastructure Baseline.

A version-controlled Infrastructure Baseline can maintain:

• A stable Artifact identifier
• A distinct identifier for each revision
• The content associated with each revision
• The relationship between successive revisions
• The date and time associated with each revision
• The actor or process responsible for each revision
• The reason for each revision
• The approval status of each revision
• The Provenance associated with each revision
• The Traceability relationships associated with each revision

Version Control supports:

• Retrieval of a specific Infrastructure Baseline revision
• Comparison of Infrastructure Baseline revisions
• Identification of changes between revisions
• Reproduction of an Infrastructure Deployment from a selected revision
• Preservation of approved revisions
• Creation of a new revision when Infrastructure Baseline content changes
• Recovery from an unintended change
• Auditability of Infrastructure Baseline evolution

The stable Artifact identifier identifies the Infrastructure Baseline across revisions. A revision identifier distinguishes one controlled state of the Infrastructure Baseline from another.

This requirement does not assign the stable Artifact identifier. MO-005b addresses Infrastructure Baseline identification.

This requirement does not prohibit modification of an approved revision. MO-005f addresses preservation of approved Infrastructure Baseline revisions.

This requirement does not require an Infrastructure Deployment to record the revision used. MO-005g addresses that Traceability.

This requirement applies to:

• Crucible
• Infrastructure Baselines
• Artifacts
• Version Control
• Artifact identifiers
• Revision identifiers
• Revision histories
• Revision relationships
• Change records
• Approval records
• Artifact repositories
• Artifact catalog records
• Evidence
• Provenance
• Traceability

Verification confirms that:

1. Each Infrastructure Baseline is maintained within a Version Control mechanism
2. Each controlled revision is distinguishable from every other revision of the same Infrastructure Baseline
3. Each revision remains associated with the stable Artifact identifier of the Infrastructure Baseline
4. The content associated with each revision is retrievable
5. The relationship between successive revisions is recorded
6. The changes between two revisions can be identified
7. A prior revision can be retrieved without replacing or altering another revision
8. Each revision record identifies the actor or process responsible for the revision
9. Each revision record identifies the reason for the revision
10. The verification record preserves Provenance and Traceability for the revision history

The following pages reference this requirement:

Implemented and Verified.

Assess whether the current Crucible implementation maintains each Infrastructure Baseline under Version Control.

Review and accept MO-005c as a proposed derived requirement created from the evaluation and decomposition of MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft.

The following unresolved issues affect this requirement:

Define the Version Control mechanism used for Infrastructure Baselines.

Define the revision identifier assigned to each controlled Infrastructure Baseline revision.

Define the relationship recorded between successive Infrastructure Baseline revisions.

Define the change record required for each Infrastructure Baseline revision.

Define the approval-status information recorded for each Infrastructure Baseline revision.

Define the retention and retrieval requirements for prior Infrastructure Baseline revisions.

This requirement page should retain the stable requirement identifier MO-005c.

This page is a leaf requirement page and omits a trailing :start from its namespace.

The parent MO-005 page is a non-leaf page and retains a trailing :start in its namespace.

Changes to the Statement should preserve:

• Crucible as the responsible actor
• The Infrastructure Baseline as the controlled subject
• Version Control as the required management mechanism
• Preservation and retrieval of distinguishable Infrastructure Baseline revisions

The Version Control record should identify:

• The stable Infrastructure Baseline Artifact identifier
• The revision identifier
• The predecessor revision
• The revision date and time
• The actor or process responsible for the revision
• The revision description
• The reason for the revision
• The approval status
• The associated Provenance
• The associated Traceability

Material changes should receive review and should update the verification criteria, source records, and Issues section.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005c#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.