dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005c

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005c [2026/07/20 08:48] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005c [2026/07/30 05:26] (current) – [Delivery Phase] nick_dido
Line 1: Line 1:
-====== MO-005c — Infrastructure Baseline Version Control ======+====== MO-005c — Infrastructure Baseline Revision Control ======
  
 [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:start|Go to MO-005 — Reusable and Version-Controlled Infrastructure Baselines]] [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:start|Go to MO-005 — Reusable and Version-Controlled Infrastructure Baselines]]
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL place each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] under [[dido:99_annexes:annex-b-terms-and-definitions:v:version_control|Version Control]].+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL maintain each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] under [[dido:99_annexes:annex-b-terms-and-definitions:v:version_control|Version Control]].
  
 ===== Derived From ===== ===== Derived From =====
Line 17: Line 17:
 > //The system SHALL establish infrastructure as a reusable and version-controlled asset.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] > //The system SHALL establish infrastructure as a reusable and version-controlled asset.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-MO-005c preserves the portion of the Original Requirement that requires infrastructure to be version controlled by identifying the controlled subject as an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]].+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: The separate requirements derived from MO-005 address:
Line 23: Line 23:
   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005a|MO-005a — Infrastructure Baseline Artifact Management]]   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005a|MO-005a — Infrastructure Baseline Artifact Management]]
   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005b|MO-005b — Infrastructure Baseline Identification]]   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005b|MO-005b — Infrastructure Baseline Identification]]
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005d|MO-005d — Infrastructure Baseline Selection]]+  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005d|MO-005d — Approved Infrastructure Baseline Selection]]
   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005e|MO-005e — Infrastructure Baseline Reuse]]   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005e|MO-005e — Infrastructure Baseline Reuse]]
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005f|MO-005f — Approved Baseline Immutability]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005f|MO-005f — Approved Infrastructure Baseline Preservation]] 
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005g|MO-005g — Baseline Revision Deployment Traceability]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005g|MO-005g — Infrastructure Deployment Baseline Traceability]]
- +
-===== Assessment ===== +
- +
-The Original Requirement uses **version-controlled** without identifying the controlled subject or the behaviors associated with Version Control. +
- +
-The phrase **version-controlled asset** does not identify: +
- +
-  * The object placed under Version Control +
-  * The distinction between the Infrastructure Baseline identifier and a revision identifier +
-  * The relationship between successive revisions +
-  * The content associated with each revision +
-  * The mechanism used to retrieve a prior revision +
-  * The mechanism used to compare revisions +
-  * The change record associated with a revision +
-  * The approval status associated with a revision +
-  * The Provenance associated with a revision +
-  * The Evidence required to demonstrate Version Control +
- +
-MO-005c: +
- +
-  * Identifies [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor +
-  * Identifies the Infrastructure Baseline as the subject placed under Version Control +
-  * Uses the defined term [[dido:99_annexes:annex-b-terms-and-definitions:v:version_control|Version Control]] +
-  * Separates Version Control from Artifact management and unique Artifact identification +
-  * Separates Version Control from baseline selection, reuse, immutability, and deployment traceability+
  
 ===== Rationale ===== ===== Rationale =====
  
-Version Control preserves the revision history of an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]].+[[dido:99_annexes:annex-b-terms-and-definitions:v:version_control|Version Control]] preserves the revision history of an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]].
  
 A version-controlled Infrastructure Baseline can maintain: A version-controlled Infrastructure Baseline can maintain:
Line 67: Line 42:
   * The reason for each revision   * The reason for each revision
   * The approval status of each revision   * The approval status of each revision
-  * The Provenance associated with each revision +  * The [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] associated with each revision 
-  * The Traceability relationships associated with each revision+  * The [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships associated with each revision
  
 Version Control supports: Version Control supports:
  
   * Retrieval of a specific Infrastructure Baseline revision   * Retrieval of a specific Infrastructure Baseline revision
-  * Comparison of two Infrastructure Baseline revisions+  * Comparison of Infrastructure Baseline revisions
   * Identification of changes between revisions   * Identification of changes between revisions
   * Reproduction of an Infrastructure Deployment from a selected revision   * Reproduction of an Infrastructure Deployment from a selected revision
   * Preservation of approved revisions   * Preservation of approved revisions
-  * Creation of a new revision when baseline content changes+  * Creation of a new revision when Infrastructure Baseline content changes
   * Recovery from an unintended change   * Recovery from an unintended change
-  * Auditability of baseline evolution +  * Auditability of Infrastructure Baseline evolution
-  * Preservation of Provenance +
-  * Maintenance of Traceability+
  
-The stable Artifact identifier identifies the Infrastructure Baseline across revisions. A revision identifier distinguishes one controlled state of the Infrastructure Baseline from another controlled state.+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 establishes that requirement.+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 establishes approved baseline immutability.+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 applied revision. MO-005g establishes that requirement.+This requirement does not require an Infrastructure Deployment to record the revision used. MO-005g addresses that Traceability.
  
 ===== Applies To ===== ===== Applies To =====
Line 107: Line 80:
   * Artifact repositories   * Artifact repositories
   * Artifact catalog records   * Artifact catalog records
-  * Infrastructure definitions 
-  * Configuration definitions 
-  * Machine Image references 
-  * Image-layer references 
-  * Package and dependency references 
-  * Security configuration 
-  * Compliance configuration 
-  * Deployment parameters 
-  * Validation criteria 
   * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]   * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
   * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]   * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
Line 124: Line 88:
 Verification confirms that: Verification confirms that:
  
-  - Each Infrastructure Baseline is maintained within a Version Control mechanism+  - Each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] is maintained within a [[dido:99_annexes:annex-b-terms-and-definitions:v:version_control|Version Control]] mechanism
   - Each controlled revision is distinguishable from every other revision of the same Infrastructure Baseline   - Each controlled revision is distinguishable from every other revision of the same Infrastructure Baseline
   - Each revision remains associated with the stable Artifact identifier of the Infrastructure Baseline   - Each revision remains associated with the stable Artifact identifier of the Infrastructure Baseline
Line 131: Line 95:
   - The changes between two revisions can be identified   - The changes between two revisions can be identified
   - A prior revision can be retrieved without replacing or altering another revision   - A prior revision can be retrieved without replacing or altering another revision
-  - The revision history preserves the applicable Provenance and Traceability+  - Each revision record identifies the actor or process responsible for the revision 
 +  - Each revision record identifies the reason for the revision 
 +  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] for the revision history
  
-Verification includes:+===== Referenced By =====
  
-  * Infrastructure Baseline inspection +The following pages reference this requirement:
-  * Version Control configuration inspection +
-  * Artifact identifier inspection +
-  * Revision identifier inspection +
-  * Revision-history inspection +
-  * Revision-relationship inspection +
-  * Revision retrieval testing +
-  * Prior-revision retrieval testing +
-  * Revision comparison testing +
-  * Change-record inspection +
-  * Approval-record inspection +
-  * Artifact repository inspection +
-  * Artifact catalog inspection +
-  * Evidence inspection +
-  * Provenance inspection +
-  * Traceability inspection+
  
-The verification record identifies:+{{backlinks>.#dido:02-crusible}}
  
-  - The Infrastructure Baseline +===== Delivery Phase =====
-  - The stable Artifact identifier +
-  - Each inspected revision identifier +
-  - The Version Control mechanism +
-  - The location of the controlled revision history +
-  - The relationship between successive revisions +
-  - The content associated with each inspected revision +
-  - The result of each revision retrieval test +
-  - The result of each revision comparison test +
-  - Each detected missing, duplicate, or conflicting revision +
-  - Each identified failure or exception +
-  - The observed result +
-  - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]+
  
-===== Requirements Realized By =====+Implemented and Verified.
  
-This requirement is realized by:+===== Implementation Status =====
  
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start|FR-CFG-001 through FR-CFG-005]] +<todo>Assess whether the current Crucible implementation maintains each Infrastructure Baseline under Version Control.</todo>
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:start|FR-DEP-001 through FR-DEP-007]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-metadata-catalog-and-provenance:start|FR-MC-001 through FR-MC-005]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:start|FR-BAS-001 through FR-BAS-004]]+
  
-===== Related Architecture Sections =====+===== Requirement Status =====
  
-  * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] +<todo>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.</todo>
-  * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]] +
-  * [[dido:02-crusible:10-reproducibility-provenance-and-traceability:start|10. Reproducibility, Provenance, and Traceability]]+
  
-===== Referenced By =====+---- 
 +===== Issues =====
  
-The following pages reference this requirement:+The following unresolved issues affect this requirement:
  
-{{backlinks>.#dido:02-crusible}}+<todo>Define the Version Control mechanism used for Infrastructure Baselines.</todo>
  
-===== Delivery Phase =====+<todo>Define the revision identifier assigned to each controlled Infrastructure Baseline revision.</todo>
  
-Phase 1 and subsequent phases+<todo>Define the relationship recorded between successive Infrastructure Baseline revisions.</todo>
  
-===== Implementation Status =====+<todo>Define the change record required for each Infrastructure Baseline revision.</todo>
  
-Not Assessed+<todo>Define the approval-status information recorded for each Infrastructure Baseline revision.</todo>
  
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation places each Infrastructure Baseline under Version Control. +<todo>Define the retention and retrieval requirements for prior Infrastructure Baseline revisions.</todo>
- +
-===== Requirement Status ===== +
- +
-Draft +
- +
-This requirement derives from MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft.+
  
 ---- ----
Line 212: Line 141:
 This page is a leaf requirement page and omits a trailing '':start'' from its namespace. This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-Changes to the Statement should preserve the Infrastructure Baseline Version Control intent derived from MO-005.+The parent MO-005 page is a non-leaf page and retains a trailing '':start'' in its namespace. 
 + 
 +Changes to the Statement should preserve: 
 + 
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor 
 +  * The [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] as the controlled subject 
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:v:version_control|Version Control]] as the required management mechanism 
 +  * Preservation and retrieval of distinguishable Infrastructure Baseline revisions
  
 The Version Control record should identify: The Version Control record should identify:
Line 224: Line 160:
   * The reason for the revision   * The reason for the revision
   * The approval status   * The approval status
-  * The associated Provenance +  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] 
-  * The associated Traceability +  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * The supporting Evidence+
  
-Material changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.+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: To reference this requirement Statement from another wiki page, insert:
  • dido/02-crusible/99-annexes/annex-c-requirements/01-mission-objectives/mo-005/mo-005c.1784562515.txt.gz
  • Last modified: 2026/07/20 08:48
  • by nick_dido