dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-001

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:03-functional-requirements:03-04-multi-cloud-management:fr-mc-001 [2026/07/17 10:22] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-001 [2026/07/30 05:51] (current) – nick_dido
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL separate [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_provider]] independent deployment information from cloud-provider-specific parameters.+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL provide Cloud Provider Abstraction.
  
-===== Source Statement =====+===== Derived From =====
  
-> The system shall support [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_provider]] abstraction.+This requirement derives from:
  
-===== Source =====+  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-MC-001
  
-Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-MC-001.+The Original Requirement states:
  
-===== Assessment =====+> //The system shall support cloud provider abstraction.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-The source statement expresses the approved architectural intent but does not provide a fully testable behavior.+FR-MC-001:
  
-The following Specification Discipline and Authoring findings apply:+  * 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
  
-  * **The system** does not use the defined system name +No other substantive normalization is required.
-  * **shall** does not follow the established uppercase normative convention +
-  * **Support** is a weak verb +
-  * **Cloud provider abstraction** names an architectural approach without identifying the required separation +
-  * The source statement does not identify which information remains provider independent +
-  * The source statement does not identify which information may vary by provider +
-  * The source statement does not prescribe a provider, cloud service model, programming language, interface, or implementation technology +
- +
-The normalized Statement: +
- +
-  * Replaces **The system** with [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] +
-  * Replaces **support** with the direct behavior **separate** +
-  * Identifies cloud-provider-independent deployment information +
-  * Identifies cloud-provider-specific parameters +
-  * Preserves implementation independence +
-  * Retains one primary required behavior +
- +
-The normalized Statement does not require every deployment capability to remain identical across providers. Provider-specific extensions may address capabilities that do not have a common provider-independent representation.+
  
 ===== Rationale ===== ===== Rationale =====
  
-Cloud providers expose different:+Cloud providers expose different resource types, service identifiers, configuration parameters, identity models, network models, storage models, regions, interfaces, and operational constraints.
  
-  * Resource types +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]].
-  * Service names +
-  * Configuration parameters +
-  * Identity models +
-  * Network models +
-  * Storage models +
-  * Regions and location identifiers +
-  * Management interfaces +
-  * Operational constraints+
  
-Cloud Provider Abstraction separates common deployment intent from the details required by a particular provider.+This separation reduces provider coupling and supports reuse of deployment information across Provider Implementations.
  
-Cloud-provider-independent deployment information may identify: +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.
- +
-  * Required computing capacity +
-  * Required storage capability +
-  * Required network relationships +
-  * Required security characteristics +
-  * Required identity relationships +
-  * Required [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]] +
-  * Required [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] +
- +
-Cloud-provider-specific parameters may identify: +
- +
-  * Provider resource types +
-  * Provider service identifiers +
-  * Provider regions +
-  * Provider account or project identifiers +
-  * Provider network identifiers +
-  * Provider storage classes +
-  * Provider machine types +
-  * Provider-specific security configuration +
- +
-This separation contributes to: +
- +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_portability|Cloud Portability]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independence|Platform Independence]] +
-  * Provider substitution +
-  * Reusable deployment intent +
-  * Reduced provider coupling +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]+
  
 ===== Applies To ===== ===== Applies To =====
Line 92: Line 41:
  
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
-  * Cloud-provider-independent deployment information+  * Cloud Provider Abstraction 
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_provider|Cloud Providers]] 
 +  * Cloud deployment information
   * Cloud-provider-specific parameters   * Cloud-provider-specific parameters
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Descriptions]] 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configurations]] 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] 
   * [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementations]]   * [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementations]]
-  * Cloud deployment workflows 
-  * Cloud providers 
  
 ===== Verification ===== ===== Verification =====
  
-  - Verification SHALL confirm that a tested deployment identifies cloud-provider-independent deployment information +Verification confirms that:
-  - Verification SHALL confirm that the tested deployment identifies cloud-provider-specific parameters separately from the cloud-provider-independent deployment information +
-  - Verification SHALL confirm that changing a cloud-provider-specific parameter does not require modification of unrelated cloud-provider-independent deployment information +
-  - Verification SHALL confirm that cloud-provider-independent components do not contain unidentified provider-specific deployment behavior+
  
-Verification may include: +  - 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]] 
-  * Deployment-description inspection +  - A provider-specific parameter can change without requiring modification of unrelated provider-independent deployment information 
-  * Configuration-boundary inspection +  - The observed behavior demonstrates Cloud Provider Abstraction
-  * Provider-parameter inspection +
-  * Provider-substitution testing +
-  * Static dependency analysis +
-  * Provider implementation testing +
-  * Cross-provider deployment testing +
- +
-The verification record SHALL identify: +
- +
-  - The tested deployment information +
-  - The cloud-provider-independent information +
-  - The cloud-provider-specific parameters +
-  - The tested cloud providers +
-  - The observed separation +
-  - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] +
- +
-===== Outgoing Traceability ===== +
- +
-This requirement realizes: +
- +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003|MO-003]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006|MO-006]] +
- +
-This requirement relates to: +
- +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start|C.3.1 Configuration Management]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:start|C.3.3 Deployment Orchestration]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-002|FR-MC-002 — Provider-Specific Extensions]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-003|FR-MC-003 — Deployment Portability Across Cloud Providers]] +
-  * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]]+
  
 ===== Referenced By ===== ===== Referenced By =====
  
-The wiki Backlinks function provides the current list of pages that reference ''FR-MC-001''.+The following pages reference this requirement:
  
-Incoming [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] should be derived dynamically from backlinks rather than maintained as a duplicate manual list.+{{backlinks>.#dido:02-crusible}}
  
-===== ConOps Relationship =====+===== Implementation Status =====
  
-The Crucible Concept of Operations describes common deployment intent combined with platform-specific information before deployment.+Implemented and Verified
  
-FR-MC-001 establishes the separation between cloud-provider-independent deployment information and cloud-provider-specific parameters.+===== Requirement Status =====
  
-===== Delivery Phase =====+<todo>Review and approve FR-MC-001 as a leaf requirement.</todo>
  
-Phase 1+---- 
 +===== Issues =====
  
-===== Implementation Status ===== +<todo>Determine whether Cloud Provider Abstraction requires a controlled definition in the shared Terms and Definitions corpus.</todo>
- +
-Not Assessed +
- +
-===== Requirement Status =====+
  
-Draft+<todo>Determine whether separate requirements define the boundary between provider-independent deployment information and provider-specific parameters.</todo>
  
 ---- ----
 ===== Notes for Editors ===== ===== Notes for Editors =====
  
-This requirement page should retain the stable requirement identifier ''FR-MC-001''.+This requirement page retains the stable requirement identifier ''FR-MC-001''.
  
-Changes to the Statement SHALL preserve the approved intent of the source requirement.+This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-The Statement should remain limited to separation of cloud-provider-independent deployment information from cloud-provider-specific parameters.+The Statement preserves the approved source intent by requiring Crucible to provide Cloud Provider Abstraction.
  
-Requirements for provider extensions, cross-provider deployment, Hybrid-Cloud Deployment, and Edge Deployment should remain in their applicable requirement pages.+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: To reference this requirement Statement from another wiki page, insert:
Line 182: Line 93:
 {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-001#Statement&noheader&nofooter&noeditbtn}} {{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> </code>
- 
-Do not rename this page after an external citation unless a redirect or move plan is in place. 
  
 ---- ----
  • dido/02-crusible/99-annexes/annex-c-requirements/03-functional-requirements/03-04-multi-cloud-management/fr-mc-001.1784308975.txt.gz
  • Last modified: 2026/07/17 10:22
  • by nick_dido