C.3.4 Multi-Cloud Management

Go to Crucible Functional Requirements

The Multi-Cloud Management requirements define how Crucible separates Platform Independent Information from Platform Specific Information, incorporates provider-specific extensions, supports deployment across cloud providers, and operates across hybrid-cloud and edge environments.

Together, these requirements establish Platform Independence and provider realization behavior that contributes to Cloud Portability, provider substitution, and consistent deployment outcomes across Provider Implementations.

Contents

Notes for Editors

The individual requirement pages should retain the stable identifiers FR-MC-001 through FR-MC-005.

Individual requirement pages are leaf nodes and should not include a trailing :start in their namespaces.

The Source Statement on each requirement page should preserve the original wording from the controlling System Requirements Specification.

Normalized Statements should use direct, testable behavior and should distinguish Platform Independent Information from Platform Specific Information and Platform Specific Parameters.

Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.

Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.

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

{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}

Replace <namespace> with the namespace of the requirement leaf page.

The section name following # SHALL match the section heading verbatim on the requirement page.

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

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.