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

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-004 [2026/07/20 08:58] – ↷ Links adapted because of a move operation nick_didodido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-004 [2026/07/30 05:54] (current) – nick_dido
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] across an identified combination of cloud and non-cloud [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]].+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployments]].
  
-===== Source Statement =====+===== Derived From =====
  
-> The system shall support [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployments]].+This requirement derives from:
  
-===== Source =====+  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-MC-004
  
-Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-MC-004.+The Original Requirement states:
  
-===== Assessment =====+> //The system shall support [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployments]].//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-The source statement identifies a deployment topology but does not state the required deployment behavior.+FR-MC-004:
  
-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 the observable behavior **perform** 
 +  * Links **Hybrid-Cloud Deployments** to the controlling definition
  
-  * **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 +
-  * **[[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployment]]** requires a controlled definition +
-  * The source statement does not identify the participating Infrastructure Environments +
-  * The source statement does not prescribe public-cloud, private-cloud, on-premises, provider, network, or orchestration technology +
- +
-The normalized Statement: +
- +
-  * Replaces **The system** with [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] +
-  * Replaces **support** with **perform** +
-  * Identifies Infrastructure Deployment as the required activity +
-  * Identifies a combination of cloud and non-cloud Infrastructure Environments +
-  * Preserves implementation independence+
  
 ===== Rationale ===== ===== Rationale =====
  
-A [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployment]] distributes related deployment subjects across cloud and non-cloud Infrastructure Environments.+A [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployment]] combines deployment subjects across cloud and non-cloud environments.
  
-A [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployment]] may combine:+A Hybrid-Cloud Deployment can include:
  
   * A public-cloud environment and an on-premises environment   * A public-cloud environment and an on-premises environment
Line 47: Line 37:
   * Cloud computing resources and edge computing resources   * Cloud computing resources and edge computing resources
  
-The participating environments may differ in:+The participating environments can differ in administrative authority, network accessibility, security controls, resource models, Provider interfaces, operational constraints, and compliance obligations.
  
-  * Administrative authority +This requirement establishes Hybrid-Cloud Deployment behavior without prescribing:
-  * Network accessibility +
-  * Security controls +
-  * Resource models +
-  * Provider interfaces +
-  * Operational constraints +
-  * Compliance obligations+
  
-The deployment must identify the subjects assigned to each environment and the relationships that cross environment boundaries.+  * The participating environments 
 +  * The deployment subjects assigned to each environment 
 +  * Cross-environment connectivity 
 +  * Identity federation 
 +  * Security-boundary behavior 
 +  * Synchronization 
 +  * Workload placement 
 +  * A particular Cloud Provider 
 +  * A particular network or orchestration technology 
 + 
 +Separate requirements, architecture specifications, workflows, or policies define those subjects and behaviors.
  
 ===== Applies To ===== ===== Applies To =====
Line 64: Line 58:
  
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
-  * [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployments]]  * Cloud Infrastructure Environments +  * [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployments]] 
-  * Non-cloud Infrastructure Environments +  * Cloud environments 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_resource|Infrastructure Resources]] +  * Non-cloud environments 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machines]] +  * Hybrid deployment workflows
-  * [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes Clusters]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workloads]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]] +
-  * Cross-environment relationships+
  
 ===== Verification ===== ===== Verification =====
  
-  - Verification SHALL confirm that the tested deployment identifies at least one cloud Infrastructure Environment +Verification confirms that:
-  - Verification SHALL confirm that the tested deployment identifies at least one non-cloud Infrastructure Environment +
-  - Verification SHALL confirm that the tested deployment identifies the deployment subjects assigned to each Infrastructure Environment +
-  - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] deploys the identified subjects to their assigned Infrastructure Environments +
-  - Verification SHALL confirm that the resulting deployment satisfies the applicable cross-environment [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]+
  
-Verification may include: +  - A Hybrid-Cloud Deployment is selected for testing 
- +  - The tested deployment includes at least one cloud environment 
-  * Hybrid-Cloud Deployment testing +  - The tested deployment includes at least one non-cloud environment 
-  * Environment-topology inspection +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs the tested [[dido:99_annexes:annex-b-terms-and-definitions:h:hybrid-cloud_deployment|Hybrid-Cloud Deployment]] 
-  * Cross-environment connectivity testing +  - Deployment subjects are realized in the participating environments 
-  * Identity-boundary testing +  - The observed behavior demonstrates deployment across cloud and non-cloud environments
-  * Deployment-state inspection +
-  * Acceptance testing +
- +
-The verification record SHALL identify: +
- +
-  - The participating Infrastructure Environments +
-  - The cloud environment +
-  - The non-cloud environment +
-  - The assigned deployment subjects +
-  - The cross-environment relationships +
-  - The observed deployment results +
-  - 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:start|MO-003]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start|MO-006]] +
- +
-This requirement relates to: +
- +
-  * [[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-001|FR-MC-001 — Cloud Provider Abstraction]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-005|FR-MC-005 — Edge Deployments]] +
-  * [[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-004''.+The following pages reference this requirement:
  
-Incoming Traceability should be derived dynamically from backlinks.+{{backlinks>.#dido:02-crusible}}
  
-===== ConOps Relationship =====+===== Implementation Status =====
  
-FR-MC-004 establishes deployment across cloud and non-cloud Infrastructure Environments while preserving a coordinated deployment description and traceability relationship.+Implemented and Verified
  
-===== Delivery Phase =====+===== Requirement Status =====
  
-Phase 1+<todo>Review and approve FR-MC-004 as a leaf requirement.</todo>
  
-===== Implementation Status =====+---- 
 +===== Issues =====
  
-Not Assessed+<todo>Confirm that Hybrid-Cloud Deployment has a controlled definition in the shared Terms and Definitions corpus.</todo>
  
-===== Requirement Status ===== +<todo>Determine whether separate requirements define cross-environment connectivity, security, identity federation, synchronization, and workload placement.</todo>
- +
-Draft+
  
 ---- ----
 ===== Notes for Editors ===== ===== Notes for Editors =====
  
-This requirement page should retain the stable requirement identifier ''FR-MC-004''.+This requirement page retains the stable requirement identifier ''FR-MC-004''.
  
-The Statement should remain limited to Infrastructure Deployment across an identified combination of cloud and non-cloud Infrastructure Environments.+This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-Requirements for connectivity, security, identity federation, synchronization, and workload placement should remain separate.+The Statement preserves the approved source intent by requiring Crucible to perform Hybrid-Cloud Deployments. 
 + 
 +Do not add specific cloud and non-cloud Infrastructure Environments, workload placement, connectivity, security, identity federation, synchronization, Provider, network, or orchestration 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 150: Line 111:
 {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-004#Statement&noheader&nofooter&noeditbtn}} {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-004#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-004.1784563113.txt.gz
  • Last modified: 2026/07/20 08:58
  • by nick_dido