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

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-005a [2026/07/20 08:45] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005a [2026/07/30 05:25] (current) – [Delivery Phase] nick_dido
Line 22: Line 22:
  
   * [[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-005c|MO-005c — Infrastructure Baseline Version Control]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005c|MO-005c — Infrastructure Baseline Revision Control]] 
-  * [[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 **infrastructure** without identifying the controlled representation subject to management. +
- +
-The Original Requirement also uses **asset** without identifying the applicable managed information object. +
- +
-The phrase **establish infrastructure as an asset** does not identify: +
- +
-  * The representation managed by Crucible +
-  * The content included in the representation +
-  * The metadata associated with the representation +
-  * The storage and retrieval mechanisms +
-  * The relationship between the representation and an Infrastructure Deployment +
-  * The Evidence required to demonstrate Artifact management +
- +
-MO-005a: +
- +
-  * Identifies [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor +
-  * Identifies the [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] as the managed subject +
-  * Replaces the general term **asset** with the defined term [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] +
-  * Separates Artifact management from identification, Version Control, selection, reuse, immutability, and deployment traceability+
  
 ===== Rationale ===== ===== Rationale =====
Line 54: Line 32:
 Managing an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] as an [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] gives the baseline a controlled representation that Crucible can store, retrieve, inspect, compare, approve, select, and apply. Managing an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] as an [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] gives the baseline a controlled representation that Crucible can store, retrieve, inspect, compare, approve, select, and apply.
  
-An Infrastructure Baseline Artifact can include:+An Infrastructure Baseline Artifact can contain or reference:
  
   * Infrastructure definitions   * Infrastructure definitions
Line 66: Line 44:
   * Validation criteria   * Validation criteria
   * Supporting metadata   * Supporting metadata
-  * Provenance information +  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] information 
-  * Traceability information+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] information
  
-Artifact management establishes the foundation for the separate requirements governing:+Artifact management establishes the controlled representation required for identification, revision control, approval, selection, reuse, preservation, and deployment Traceability.
  
-  * Unique identification +This requirement does not define the identifier assigned to the Infrastructure Baseline. MO-005b addresses identification.
-  * Revision management +
-  * Approval +
-  * Selection +
-  * Reuse +
-  * Immutability +
-  * Deployment traceability+
  
-This requirement does not define the identifier assigned to the Artifact. MO-005b establishes that requirement.+This requirement does not establish revision control. MO-005c addresses revision control.
  
-This requirement does not establish Version Control. MO-005c establishes that requirement. +This requirement does not require selection or reuse of the Infrastructure Baseline. MO-005d and MO-005e address those outcomes.
- +
-This requirement does not require selection or reuse of the Artifact. MO-005d and MO-005e establish those requirements.+
  
 ===== Applies To ===== ===== Applies To =====
Line 92: Line 62:
   * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]]   * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]]
   * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]   * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]
-  * Infrastructure definitions +  * Infrastructure Baseline content 
-  * Configuration definitions +  * Infrastructure Baseline metadata
-  * Machine Image references +
-  * Image-layer references +
-  * Package and dependency references +
-  * Security configuration +
-  * Compliance configuration +
-  * Deployment parameters +
-  * Validation criteria +
-  * Artifact metadata+
   * Artifact repositories   * Artifact repositories
-  * Artifact catalog records+  * Artifact storage 
 +  * Artifact retrieval
   * [[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 112: Line 75:
 Verification confirms that: Verification confirms that:
  
-  - Each Infrastructure Baseline has a managed Artifact representation+  - Each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] has a managed [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] representation
   - The Artifact contains or references the content that constitutes the Infrastructure Baseline   - The Artifact contains or references the content that constitutes the Infrastructure Baseline
-  - Crucible can store the Artifact +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] stores the Artifact 
-  - Crucible can retrieve the Artifact +  - Crucible retrieves the Artifact 
-  - Crucible can inspect the Artifact content and associated metadata +  - Crucible exposes the Artifact content and associated metadata for inspection 
-  - The Artifact representation remains distinguishable from an Infrastructure Deployment created from the baseline +  - The Artifact representation remains distinguishable from an Infrastructure Deployment created from the Infrastructure Baseline 
-  - The management record preserves the required Evidence, Provenance, and Traceability+  - The management record identifies the Infrastructure Baseline and its Artifact representation 
 +  - The management record preserves the required [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
  
-Verification includes:+===== Referenced By =====
  
-  * Infrastructure Baseline inspection +The following pages reference this requirement:
-  * Artifact inspection +
-  * Artifact-content inspection +
-  * Artifact-metadata inspection +
-  * Artifact-repository inspection +
-  * Artifact-catalog inspection +
-  * Artifact storage testing +
-  * Artifact retrieval testing +
-  * Artifact integrity inspection +
-  * Infrastructure Deployment comparison +
-  * Evidence inspection +
-  * Provenance inspection +
-  * Traceability inspection+
  
-The verification record identifies:+{{backlinks>.#dido:02-crusible}}
  
-  - The Infrastructure Baseline +===== Delivery Phase =====
-  - The associated Artifact +
-  - The Artifact type +
-  - The Artifact location +
-  - The Artifact content or referenced content +
-  - The associated metadata +
-  - The storage result +
-  - The retrieval result +
-  - The inspection result +
-  - 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:02-operational-requirements:or-002|OR-002 — Deployment Environments]] +<todo>Assess whether the current Crucible implementation manages each Infrastructure Baseline as an Artifact.</todo>
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-005|OR-005 — Distributed Environment Management]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start|FR-CFG-001 through FR-CFG-005]] +
-  * [[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-005a 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:06-machine-images-and-image-layers:start|6. Machine Images and Image Layers]] +
-  * [[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 content that constitutes an Infrastructure Baseline Artifact.</todo>
  
-===== Delivery Phase =====+<todo>Define the metadata required for each Infrastructure Baseline Artifact.</todo>
  
-Phase 1 and subsequent phases+<todo>Identify the repository or storage mechanism used to manage Infrastructure Baseline Artifacts.</todo>
  
-===== Implementation Status =====+<todo>Define the storage, retrieval, and inspection behaviors required for Infrastructure Baseline Artifacts.</todo>
  
-Not Assessed +<todo>Define the criteria used to distinguish an Infrastructure Baseline Artifact from an Infrastructure Deployment created from that baseline.</todo>
- +
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation manages each Infrastructure Baseline as an Artifact. +
- +
-===== Requirement Status ===== +
- +
-Draft +
- +
-This requirement derives from MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft.+
  
 ---- ----
Line 198: Line 124:
 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 Artifact-management 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 managed subject 
 +  * The [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] as the controlled representation 
 +  * Management of each Infrastructure Baseline as an Artifact
  
 The Artifact representation should identify or reference: The Artifact representation should identify or reference:
Line 205: Line 138:
   * The Artifact type   * The Artifact type
   * The associated metadata   * The associated metadata
-  * The applicable repository or storage location +  * The repository or storage location 
-  * The applicable Provenance +  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] 
-  * The applicable 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-005a.1784562350.txt.gz
  • Last modified: 2026/07/20 08:45
  • by nick_dido