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

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-003:mo-003c [2026/07/20 08:27] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003c [2026/07/30 05:23] (current) – [Delivery Phase] nick_dido
Line 1: Line 1:
-====== MO-003c — Common Infrastructure Baseline ======+====== MO-003c — Provider-Independent Infrastructure Baseline ======
  
 [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:start|Go to MO-003 — Cloud-Agnostic Deployment]] [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:start|Go to MO-003 — Cloud-Agnostic Deployment]]
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL use the same identified version of the [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] for each selected [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platform]].+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL use the same identified version of the provider-independent [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] for each selected [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platform]].
  
 ===== Derived From ===== ===== Derived From =====
Line 15: Line 15:
 The Original Requirement states: The Original Requirement states:
  
-> //The system SHALL provide cloud-agnostic deployment capabilities.//[[dido:02-crusible:99-annexes:annex-b:cr-003|[C3]]]+> //The system SHALL provide cloud-agnostic deployment capabilities.//[[dido:02-crusible:99-annexes:annex-b:cr-002|[C2]]]
  
-MO-003c preserves the portion of the Original Requirement that requires a common Infrastructure Baseline across the selected Deployment Platforms.+MO-003c preserves the portion of the Original Requirement that requires common provider-independent infrastructure requirements across the selected Deployment Platforms.
  
 The separate requirements derived from MO-003 address: The separate requirements derived from MO-003 address:
  
   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003a|MO-003a — Cross-Platform Deployment]]   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003a|MO-003a — Cross-Platform Deployment]]
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003b|MO-003b — Common Crucible Description]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003b|MO-003b — Provider-Independent Crucible Description]] 
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003d|MO-003d — Provider-Specific Dependency Limitation]]+  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003d|MO-003d — Limitation of Provider-Specific Dependencies]]
  
-===== Assessment =====+===== Rationale =====
  
-The Original Requirement does not identify the infrastructure requirements that remain common across Cloud Providers or Deployment Platforms.+A provider-independent [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] establishes consistent infrastructure requirements across multiple Deployment Platforms.
  
-The phrase **cloud-agnostic deployment capabilities** does not identify:+Using the same identified version prevents a change of Deployment Platform from implicitly changing the provider-independent infrastructure requirements.
  
-  * The common Infrastructure Baseline +Provider-specific implementations may realize the same Infrastructure Baseline through different platform mechanisms. Those mechanisms do not change the requirements established by the identified Infrastructure Baseline.
-  * The version of the Infrastructure Baseline +
-  * The Deployment Platforms to which the Infrastructure Baseline applies +
-  * The distinction between baseline requirements and platform-specific implementation details +
-  * The criteria used to determine whether the same Infrastructure Baseline was applied to each deployment +
- +
-MO-003c: +
- +
-  * Identifies the [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] as the common source of infrastructure requirements +
-  * Requires use of the same identified Infrastructure Baseline version across the selected Deployment Platforms +
-  * Prevents a change of target Deployment Platform from implicitly changing the common infrastructure requirements +
-  * Separates common Infrastructure Baseline use from cross-platform deployment, common Crucible Description use, and provider-specific dependency limitation +
- +
-===== Rationale ===== +
- +
-A common Infrastructure Baseline establishes consistent infrastructure requirements across multiple Deployment Platforms. +
- +
-The Infrastructure Baseline defines the required infrastructure characteristics independently of the provider-specific mechanisms used to realize those characteristics.+
  
 Using the same identified version supports: Using the same identified version supports:
Line 54: Line 37:
   * Consistent infrastructure requirements   * Consistent infrastructure requirements
   * Controlled comparison of deployment results   * Controlled comparison of deployment results
 +  * Change control
 +  * Detection of platform-specific changes to provider-independent baseline requirements
 +  * Reuse across supported Deployment Platforms
   * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]   * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
   * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]   * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * Change control 
-  * Cross-platform evaluation 
-  * Detection of platform-specific changes to common baseline requirements 
-  * Reuse across supported Deployment Platforms 
- 
-The requirement uses an identified version rather than the unqualified word **same**. The identifier and version establish the specific Infrastructure Baseline applied to each deployment. 
- 
-Provider-specific implementations can realize the common Infrastructure Baseline through different platform mechanisms. Those mechanisms do not change the requirements established by the identified Infrastructure Baseline. 
  
-This requirement does not require use of the same Crucible Description. MO-003b establishes that requirement.+This requirement does not require use of the same Crucible Description. MO-003b addresses that outcome.
  
 ===== Applies To ===== ===== Applies To =====
Line 74: Line 52:
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism|Cloud Agnosticism]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism|Cloud Agnosticism]]
   * [[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]]
 +  * Infrastructure Baseline identifiers
 +  * Infrastructure Baseline versions
   * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_information|Platform Independent Information]]   * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_information|Platform Independent Information]]
   * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_information|Platform Specific Information]]   * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_information|Platform Specific Information]]
Line 83: Line 63:
   * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]]   * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]]
   * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]   * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]
 +  * [[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]]
   * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]   * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] 
  
 ===== Verification ===== ===== Verification =====
Line 91: Line 71:
 Verification confirms that: Verification confirms that:
  
-  - Two or more selected Deployment Platforms are identified+  - Two or more selected [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platforms]] are identified 
 +  - The provider-independent [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] is identified
   - Each deployment uses an Infrastructure Baseline with the same identifier   - Each deployment uses an Infrastructure Baseline with the same identifier
   - Each deployment uses the same identified version of the Infrastructure Baseline   - Each deployment uses the same identified version of the Infrastructure Baseline
-  - The Infrastructure Baseline defines common infrastructure requirements+  - The Infrastructure Baseline contains provider-independent infrastructure requirements
   - Changing the selected Deployment Platform does not require modification of the identified Infrastructure Baseline version   - Changing the selected Deployment Platform does not require modification of the identified Infrastructure Baseline version
 +  - [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_information|Platform Specific Information]] remains separate from the provider-independent Infrastructure Baseline
   - Platform-specific implementation mechanisms do not alter the requirements established by the Infrastructure Baseline   - Platform-specific implementation mechanisms do not alter the requirements established by the Infrastructure Baseline
-  - The deployment records identify the Infrastructure Baseline identifier and version used for each Deployment Platform+  - Each deployment record identifies the Infrastructure Baseline identifier and version used for the selected Deployment Platform 
 +  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Infrastructure Baseline, selected Deployment Platform, Provider Implementation, platform-specific information, and deployment result
  
-Verification includes:+===== Referenced By =====
  
-  * Infrastructure Baseline inspection +The following pages reference this requirement:
-  * Infrastructure Baseline identifier comparison +
-  * Infrastructure Baseline version comparison +
-  * Artifact Representation comparison +
-  * Cryptographic digest inspection +
-  * Platform-independent information inspection +
-  * Platform-specific information inspection +
-  * Cross-platform deployment tests +
-  * Resulting Infrastructure Environment comparison +
-  * Deployment-record inspection +
-  * Provenance inspection +
-  * Traceability inspection +
-  * Evidence inspection+
  
-The verification record identifies:+{{backlinks>.#dido:02-crusible}}
  
-  - The selected Deployment Platforms +===== Delivery Phase =====
-  - The Infrastructure Baseline identifier +
-  - The Infrastructure Baseline version +
-  - The applicable Infrastructure Baseline Artifact Representation +
-  - The cryptographic digest of the applicable Artifact Representation +
-  - The common infrastructure requirements +
-  - The platform-specific implementation mechanisms used for each Deployment Platform +
-  - The deployment result for each Deployment Platform +
-  - The resulting Infrastructure Environment for each Deployment Platform +
-  - Any detected modification to the Infrastructure Baseline +
-  - The observed result +
-  - The generated 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 deployments to the selected Deployment Platforms use the same identified version of the provider-independent Infrastructure Baseline.</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-multi-cloud-management:start|FR-MC-001 through FR-MC-005]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:start|FR-DSO-001 through FR-DSO-006]] +
-  * [[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]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:11-interoperability-requirements:start|INT-001 through INT-007]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:13-key-value-proposition-requirements:kvp-006|KVP-006 — Enable Cloud Portability]]+
  
-===== Related Architecture Sections =====+===== Requirement Status =====
  
-  * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] +<todo>Review and accept MO-003c as a proposed derived requirement created from the evaluation and decomposition of MO-003 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:08-dependencies-and-air-gap-operations:start|8. Dependencies and Air Gap Operations]] +
-  * [[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 provider-independent infrastructure requirements that the Infrastructure Baseline must contain.</todo>
  
-===== Delivery Phase =====+<todo>Define the provider-specific information and implementation mechanisms that must remain separate from the Infrastructure Baseline.</todo>
  
-Phase 1 and subsequent phases+<todo>Identify the controlling source that defines the boundary between provider-independent baseline requirements and provider-specific implementation details.</todo>
  
-===== Implementation Status =====+<todo>Determine whether changing the selected Deployment Platform may require any controlled transformation of the Infrastructure Baseline without creating a new Infrastructure Baseline version.</todo>
  
-Not Assessed +<todo>Define the identifier and versioning rules used to determine that each deployment uses the same Infrastructure Baseline.</todo>
- +
-Implementation status requires verification that deployments to the selected Deployment Platforms use the same identified version of the Infrastructure Baseline. +
- +
-===== Requirement Status ===== +
- +
-Draft +
- +
-This requirement derives from MO-003 in the Crucible System Requirements Specification, Version 1.1 Draft.+
  
 ---- ----
Line 180: Line 122:
 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 SHALL preserve the common Infrastructure Baseline intent derived from MO-003.+The parent MO-003 page is a non-leaf page and retains a trailing '':start'' in its namespace. 
 + 
 +Changes to the Statement should preserve:
  
-The applicable deployment records should identify:+  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor 
 +  * The provider-independent [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] as the common source of infrastructure requirements 
 +  * Use of the same identified Infrastructure Baseline version across the selected Deployment Platforms 
 +  * Separation of provider-independent baseline requirements and provider-specific implementation details
  
-  * The Infrastructure Baseline identifier +The unresolved boundary between provider-independent and provider-specific information should remain recorded in the Issues section until a controlling source defines it.
-  * The Infrastructure Baseline version +
-  * The applicable Artifact Representation +
-  * The cryptographic digest +
-  * The selected Deployment Platform +
-  * The applicable Provider Implementation +
-  * The platform-specific implementation mechanisms used for the deployment +
-  * The deployment result +
-  * The resulting Infrastructure Environment +
-  * 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-003/mo-003c.1784561264.txt.gz
  • Last modified: 2026/07/20 08:27
  • by nick_dido