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

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-005e [2026/07/20 08:52] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005e [2026/07/30 05:27] (current) – [Delivery Phase] nick_dido
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-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-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 describes infrastructure as reusable but does not identify the behavior that demonstrates reuse. +
- +
-The phrase **reusable asset** does not identify: +
- +
-  * The managed subject that is reused +
-  * The revision that is reused +
-  * The approval condition applicable to that revision +
-  * The operation that constitutes reuse +
-  * The minimum number of Infrastructure Deployments needed to demonstrate reuse +
-  * Whether reuse applies to the same revision or different revisions +
-  * The relationship between reuse and modification of approved baseline content +
-  * The Evidence required to demonstrate reuse +
- +
-MO-005e: +
- +
-  * Identifies [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor +
-  * Identifies an approved Infrastructure Baseline revision as the reused subject +
-  * Defines reuse as application of the same revision to multiple Infrastructure Deployments +
-  * Establishes two Infrastructure Deployments as the minimum verification threshold +
-  * Separates reuse from selection, Version Control, immutability, and deployment traceability+
  
 ===== Rationale ===== ===== Rationale =====
  
 Reuse occurs when [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] applies the same approved Infrastructure Baseline revision to more than one Infrastructure Deployment. Reuse occurs when [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] applies the same approved Infrastructure Baseline revision to more than one Infrastructure Deployment.
 +
 +The minimum threshold of two Infrastructure Deployments distinguishes demonstrated reuse from a single application of an Infrastructure Baseline revision.
  
 Reuse supports: Reuse supports:
Line 60: Line 39:
   * Reduction of duplicated configuration effort   * Reduction of duplicated configuration effort
   * Repeatable deployment processes   * Repeatable deployment processes
-  * Comparison of Infrastructure Deployments created from the same baseline revision+  * Comparison of Infrastructure Deployments created from the same Infrastructure Baseline revision
   * Reproduction of previously deployed infrastructure   * Reproduction of previously deployed infrastructure
   * Controlled deployment across multiple operational environments   * Controlled deployment across multiple operational environments
   * Controlled deployment across multiple Deployment Platforms   * Controlled deployment across multiple Deployment Platforms
   * Preservation of approved infrastructure configurations   * Preservation of approved infrastructure configurations
-  * Maintenance of Provenance +  * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] 
-  * Maintenance of Traceability +  * Maintenance of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * Generation of auditable [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]+
  
-The minimum threshold of two Infrastructure Deployments distinguishes demonstrated reuse from a single application of an Infrastructure Baseline revision.+The Infrastructure Deployments may differ in deployment instance, location, operational environment, Deployment Platform, execution time, or intended use, provided that Crucible applies the same approved Infrastructure Baseline revision.
  
-The Infrastructure Deployments can differ in deployment instance, location, operational environment, Deployment Platform, execution time, or intended use, provided that Crucible applies the same approved Infrastructure Baseline revision.+The resulting Infrastructure Environments need not be identical when permitted deployment-specific parameters or Provider Implementations produce controlled differences.
  
-This requirement does not require the Infrastructure Deployments to produce identical platform-specific results. Applicable Deployment Platform parameters and Provider Implementations can produce permitted differences while preserving the selected Infrastructure Baseline revision.+This requirement does not permit modification of the approved Infrastructure Baseline revision during reuse. MO-005f addresses preservation of approved revisions.
  
-This requirement does not prohibit modification of approved baseline content. MO-005f establishes approved baseline immutability. +This requirement does not define the deployment record that identifies the applied Infrastructure Baseline revision. MO-005g addresses that Traceability.
- +
-This requirement does not require each Infrastructure Deployment to record the applied baseline identifiers. MO-005g establishes deployment traceability.+
  
 ===== Applies To ===== ===== Applies To =====
Line 94: Line 70:
   * Deployment Platforms   * Deployment Platforms
   * Operational environments   * Operational environments
-  * Deployment parameters+  * Deployment-specific parameters
   * Provider Implementations   * Provider Implementations
-  * Artifact catalog records 
-  * Artifact repositories 
   * [[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 106: Line 80:
 Verification confirms that: Verification confirms that:
  
-  - The approved Infrastructure Baseline revision is identified +  - The approved [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] revision is identified 
-  - Two or more Infrastructure Deployments are identified +  - Two or more [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] are identified 
-  - Crucible applies the same approved Infrastructure Baseline revision to each identified Infrastructure Deployment +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] applies the same approved Infrastructure Baseline revision to each identified Infrastructure Deployment 
-  - The applied Artifact identifier is the same for each identified Infrastructure Deployment +  - The Infrastructure Baseline Artifact identifier is the same for each identified Infrastructure Deployment 
-  - The applied revision identifier is the same for each identified Infrastructure Deployment +  - The Infrastructure Baseline revision identifier is the same for each identified Infrastructure Deployment 
-  - Each application completes with an identified result +  - The approved Infrastructure Baseline content remains unchanged across the identified Infrastructure Deployments 
-  - The generated Evidence demonstrates reuse of the same approved revision+  - Each Infrastructure Deployment completes with an identified result 
 +  - Each permitted difference among the Infrastructure Deployments is attributable to identified deployment-specific parameters or Provider Implementations 
 +  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the approved Infrastructure Baseline revision, each Infrastructure Deployment, the deployment-specific parameters, the Provider Implementation, and the deployment result
  
-Verification includes:+===== Referenced By =====
  
-  * Infrastructure Baseline inspection +The following pages reference this requirement:
-  * Approval-record inspection +
-  * Artifact identifier inspection +
-  * Revision identifier inspection +
-  * Infrastructure Deployment inspection +
-  * Baseline application testing +
-  * Multiple-deployment testing +
-  * Deployment-record comparison +
-  * Applied-content comparison +
-  * Evidence inspection +
-  * Provenance inspection +
-  * Traceability inspection+
  
-The verification record identifies:+{{backlinks>.#dido:02-crusible}}
  
-  - The approved Infrastructure Baseline +===== Delivery Phase =====
-  - The stable Artifact identifier +
-  - The approved revision identifier +
-  - The approval status +
-  - Each Infrastructure Deployment used to demonstrate reuse +
-  - The application result for each Infrastructure Deployment +
-  - The Artifact identifier applied to each Infrastructure Deployment +
-  - The revision identifier applied to each Infrastructure Deployment +
-  - Each identified difference attributable to deployment-specific parameters +
-  - 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 applies the same approved Infrastructure Baseline revision to two or more Infrastructure Deployments.</todo>
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-004|OR-004 — Concurrent Environment Management]] +
-  * [[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-005e 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>Confirm that two Infrastructure Deployments provide the minimum sufficient demonstration of Infrastructure Baseline reuse.</todo>
  
-===== Delivery Phase =====+<todo>Define the criteria used to determine that two Infrastructure Deployments apply the same Infrastructure Baseline revision.</todo>
  
-Phase 1 and subsequent phases+<todo>Define the deployment-specific parameters that may differ without changing the reused Infrastructure Baseline revision.</todo>
  
-===== Implementation Status =====+<todo>Define the permitted differences among Infrastructure Environments produced from the same approved Infrastructure Baseline revision.</todo>
  
-Not Assessed +<todo>Define whether reuse across different Deployment Platforms or operational environments requires additional equivalence criteria.</todo>
- +
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation applies the same approved Infrastructure Baseline revision to two or more Infrastructure Deployments. +
- +
-===== Requirement Status ===== +
- +
-Draft +
- +
-This requirement derives from MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft.+
  
 ---- ----
Line 191: Line 130:
 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 reuse 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 
 +  * An approved [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] revision as the reused subject 
 +  * Application of the same revision to two or more Infrastructure Deployments 
 +  * Two Infrastructure Deployments as the minimum demonstrated reuse threshold
  
 The reuse record should identify: The reuse record should identify:
Line 202: Line 148:
   * The operational environment   * The operational environment
   * The Deployment Platform   * The Deployment Platform
-  * The applicable deployment-specific parameters+  * The deployment-specific parameters 
 +  * The Provider Implementation
   * The application result   * The application result
-  * 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-005e.1784562738.txt.gz
  • Last modified: 2026/07/20 08:52
  • by nick_dido