FR-MC-001 — Cloud Provider Abstraction [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== FR-MC-001 — Cloud Provider Abstraction ======

[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:start|Go to Crucible Multi-Cloud Management Requirements]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL provide Cloud Provider Abstraction.

===== Derived From =====

This requirement derives from:

  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-MC-001

The Original Requirement states:

> //The system shall support cloud provider abstraction.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

FR-MC-001:

  * Replaces **The system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * Changes **shall** to the established uppercase normative form **SHALL**
  * Replaces the weak verb **support** with **provide**
  * Capitalizes **Cloud Provider Abstraction** as the named architectural capability

No other substantive normalization is required.

===== Rationale =====

Cloud providers expose different resource types, service identifiers, configuration parameters, identity models, network models, storage models, regions, interfaces, and operational constraints.

Cloud Provider Abstraction allows deployment information that expresses common intent to remain separate from parameters required by a particular [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_provider|Cloud Provider]].

This separation reduces provider coupling and supports reuse of deployment information across Provider Implementations.

This requirement does not require every deployment capability to have an identical representation across Cloud Providers. Provider-specific extensions can represent capabilities that do not have a common provider-independent representation.

===== Applies To =====

This requirement applies to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * Cloud Provider Abstraction
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_provider|Cloud Providers]]
  * Cloud deployment information
  * Cloud-provider-specific parameters
  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementations]]

===== Verification =====

Verification confirms that:

  - A tested deployment contains information that expresses deployment intent
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] separates the tested deployment intent from parameters required by a particular [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_provider|Cloud Provider]]
  - A provider-specific parameter can change without requiring modification of unrelated provider-independent deployment information
  - The observed behavior demonstrates Cloud Provider Abstraction

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:02-crusible}}

===== Implementation Status =====

Implemented and Verified

===== Requirement Status =====

<todo>Review and approve FR-MC-001 as a leaf requirement.</todo>

----
===== Issues =====

<todo>Determine whether Cloud Provider Abstraction requires a controlled definition in the shared Terms and Definitions corpus.</todo>

<todo>Determine whether separate requirements define the boundary between provider-independent deployment information and provider-specific parameters.</todo>

----
===== Notes for Editors =====

This requirement page retains the stable requirement identifier ''FR-MC-001''.

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

The Statement preserves the approved source intent by requiring Crucible to provide Cloud Provider Abstraction.

Do not add provider substitution, cross-provider deployment, identical provider capabilities, Hybrid-Cloud Deployment, Edge Deployment, or provider-specific extension obligations unless the controlling requirement changes through an approved requirements process.

To reference this requirement Statement from another wiki page, insert:

<code dokuwiki>
{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-001#Statement&noheader&nofooter&noeditbtn}}
</code>

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>