MO-003c — Provider-Independent Infrastructure Baseline

Go to MO-003 — Cloud-Agnostic Deployment

Crucible SHALL use the same identified version of the provider-independent Infrastructure Baseline for each selected Deployment Platform.

This requirement derives from:

• MO-003 — Cloud-Agnostic Deployment

The Original Requirement states:

The system SHALL provide cloud-agnostic deployment capabilities.[C2]

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:

• MO-003a — Cross-Platform Deployment
• MO-003b — Provider-Independent Crucible Description
• MO-003d — Limitation of Provider-Specific Dependencies

A provider-independent Infrastructure Baseline establishes consistent infrastructure requirements across multiple Deployment Platforms.

Using the same identified version prevents a change of Deployment Platform from implicitly changing the provider-independent infrastructure requirements.

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.

Using the same identified version supports:

• Consistent infrastructure requirements
• Controlled comparison of deployment results
• Change control
• Detection of platform-specific changes to provider-independent baseline requirements
• Reuse across supported Deployment Platforms
• Provenance
• Traceability

This requirement does not require use of the same Crucible Description. MO-003b addresses that outcome.

This requirement applies to:

• Crucible
• Cloud Agnosticism
• Infrastructure Baselines
• Infrastructure Baseline identifiers
• Infrastructure Baseline versions
• Platform Independent Information
• Platform Specific Information
• Deployment Platforms
• Provider Contracts
• Provider Implementations
• Platform Specific Parameters
• Infrastructure Deployments
• Infrastructure Environments
• Artifacts
• Evidence
• Provenance
• Traceability

Verification confirms that:

1. Two or more selected Deployment Platforms are identified
2. The provider-independent Infrastructure Baseline is identified
3. Each deployment uses an Infrastructure Baseline with the same identifier
4. Each deployment uses the same identified version of the Infrastructure Baseline
5. The Infrastructure Baseline contains provider-independent infrastructure requirements
6. Changing the selected Deployment Platform does not require modification of the identified Infrastructure Baseline version
7. Platform Specific Information remains separate from the provider-independent Infrastructure Baseline
8. Platform-specific implementation mechanisms do not alter the requirements established by the Infrastructure Baseline
9. Each deployment record identifies the Infrastructure Baseline identifier and version used for the selected Deployment Platform
10. The verification record preserves Traceability among the Infrastructure Baseline, selected Deployment Platform, Provider Implementation, platform-specific information, and deployment result

The following pages reference this requirement:

Implemented and Verified

Assess whether deployments to the selected Deployment Platforms use the same identified version of the provider-independent Infrastructure Baseline.

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.

The following unresolved issues affect this requirement:

Define the provider-independent infrastructure requirements that the Infrastructure Baseline must contain.

Define the provider-specific information and implementation mechanisms that must remain separate from the Infrastructure Baseline.

Identify the controlling source that defines the boundary between provider-independent baseline requirements and provider-specific implementation details.

Determine whether changing the selected Deployment Platform may require any controlled transformation of the Infrastructure Baseline without creating a new Infrastructure Baseline version.

Define the identifier and versioning rules used to determine that each deployment uses the same Infrastructure Baseline.

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

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

The parent MO-003 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 provider-independent 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 unresolved boundary between provider-independent and provider-specific information should remain recorded in the Issues section until a controlling source defines it.

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-003:mo-003c#Statement&noheader&nofooter&noeditbtn}}

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