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

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-005 [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-005 [2026/07/30 05:55] (current) – nick_dido
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL deploy identified deployment subjects to an Edge Environment.+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform Edge Deployments.
  
-===== Source Statement =====+===== Derived From =====
  
-> The system shall support edge deployments.+This requirement derives from:
  
-===== Source =====+  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-MC-005
  
-Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-MC-005.+The Original Requirement states:
  
-===== Assessment =====+> //The system shall support edge deployments.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-The source statement identifies a target deployment context but does not state the required deployment behavior.+FR-MC-005:
  
-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** 
 +  * Capitalizes **Edge Deployments** as the named deployment 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 +
-  * **Edge deployment** does not identify the deployment subjects +
-  * **Edge** does not identify a controlled target-environment concept +
-  * The source statement does not prescribe an edge platform, device class, provider, network architecture, orchestration mechanism, or connectivity model +
- +
-The normalized Statement: +
- +
-  * Replaces **The system** with [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] +
-  * Replaces **support** with the direct behavior **deploy** +
-  * Identifies deployment subjects +
-  * Identifies an Edge Environment as the target +
-  * Preserves implementation independence +
- +
-**Edge Environment** and possibly **Edge Deployment** should receive glossary definitions. Defining Edge Environment is the higher priority because it identifies the deployment target.+
  
 ===== Rationale ===== ===== Rationale =====
  
-An Edge Environment operates computing capabilities near a source or consumer of data, an operational process, a physical location, or another point where local processing provides an architectural benefit.+An Edge Deployment places computing capabilities near a source or consumer of data, an operational process, a physical location, or another location where local processing provides an architectural benefit.
  
-Edge deployment subjects may include:+An Edge Deployment can involve:
  
   * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_resource|Infrastructure Resources]]   * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_resource|Infrastructure Resources]]
Line 49: Line 37:
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workloads]]   * [[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]]   * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]]
-  * Configuration 
-  * Security controls 
-  * Monitoring capabilities 
  
-An Edge Environment may operate with:+This requirement establishes Edge Deployment behavior without prescribing:
  
-  * Limited network connectivity +  * The deployment subjects 
-  * Intermittent connectivity +  * The target Edge Environment 
-  * Restricted bandwidth +  * An edge platform 
-  * Limited computing capacity +  * A device class 
-  * Limited storage capacity +  * A Cloud Provider 
-  * Location-specific security controls +  * A network architecture 
-  * Local operational authority +  * An orchestration mechanism 
-  * Low-latency processing requirements+  * A connectivity model 
 +  * Disconnected operation 
 +  * Air-gapped operation 
 +  * Resource constraints 
 +  * Synchronization behavior
  
-FR-MC-005 does not independently require disconnected operation. The Air-Gapped Operations requirements govern disconnected and Air-Gapped Environment behavior.+Separate requirements, architecture specifications, workflows, or policies define those subjects and behaviors.
  
 ===== Applies To ===== ===== Applies To =====
Line 71: Line 60:
  
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
-  * Edge Environments 
   * Edge Deployments   * Edge Deployments
-  * Deployment subjects 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_resource|Infrastructure Resources]] 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machines]] 
-  * [[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]] 
   * Edge deployment workflows   * Edge deployment workflows
  
 ===== Verification ===== ===== Verification =====
  
-  - Verification SHALL confirm that the tested target is identified as an Edge Environment +Verification confirms that:
-  - Verification SHALL confirm that the deployment subjects assigned to the Edge Environment are identified +
-  - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] deploys the identified subjects to the Edge Environment +
-  - Verification SHALL confirm that the resulting deployment satisfies the applicable Edge Environment [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]+
  
-Verification may include: +  - An Edge Deployment is selected for testing 
- +  - The target of the tested deployment exhibits the characteristics defined for an Edge Deployment 
-  * Edge Deployment testing +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs the tested Edge Deployment 
-  * Target-environment inspection +  - The deployed subjects can be identified in the target environment 
-  * Limited-connectivity testing +  - The observed behavior demonstrates Edge Deployment
-  * Resource-constraint testing +
-  * Deployment-state inspection +
-  * Acceptance testing +
-  * Deployment-log inspection +
- +
-The verification record SHALL identify: +
- +
-  - The Edge Environment +
-  - The deployed subjects +
-  - The applicable environment constraints +
-  - The applicable Acceptance Criteria +
-  - The deployment operation +
-  - The observed deployment result +
-  - 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-004|FR-MC-004 — Hybrid-Cloud Deployments]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:start|C.3.5 Air-Gapped Operations]] +
-  * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]] +
-  * [[dido:02-crusible:08-dependencies-and-air-gap-operations:start|8. Dependencies and Air Gap Operations]]+
  
 ===== Referenced By ===== ===== Referenced By =====
  
-The wiki Backlinks function provides the current list of pages that reference ''FR-MC-005''.+The following pages reference this requirement:
  
-Incoming Traceability should be derived dynamically from backlinks.+{{backlinks>.#dido:02-crusible}}
  
-===== ConOps Relationship =====+===== Implementation Status =====
  
-FR-MC-005 establishes deployment to an Edge Environment without prescribing the edge platform, device class, provider, or connectivity model.+Implemented and Verified
  
-===== Delivery Phase =====+===== Requirement Status =====
  
-Phase 1+<todo>Review and approve FR-MC-005 as a leaf requirement.</todo>
  
-===== Implementation Status =====+---- 
 +===== Issues =====
  
-Not Assessed+<todo>Determine whether Edge Deployment requires a controlled definition in the shared Terms and Definitions corpus.</todo>
  
-===== Requirement Status =====+<todo>Determine whether Edge Environment requires a controlled definition in the shared Terms and Definitions corpus.</todo>
  
-Draft+<todo>Determine whether separate requirements define connectivity, synchronization, resource constraints, and network isolation for Edge Deployments.</todo>
  
 ---- ----
 ===== Notes for Editors ===== ===== Notes for Editors =====
  
-This requirement page should retain the stable requirement identifier ''FR-MC-005''.+This requirement page retains the stable requirement identifier ''FR-MC-005''.
  
-The Statement should remain limited to deployment of identified deployment subjects to an Edge Environment.+This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-Edge Deployment should not be treated as synonymous with disconnected or Air-Gapped Environment deployment.+The Statement preserves the approved source intent by requiring Crucible to perform Edge Deployments.
  
-Requirements for dependency capture, disconnected operation, synchronization, resource constraints, and network isolation should remain in their applicable requirement pages.+Do not treat Edge Deployment as synonymous with deployment to a [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] or [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]]. 
 + 
 +Do not add specific deployment subjects, an Edge Environment, dependency capture, disconnected operation, synchronization, resource constraints, network isolation, platform, device, Provider, or connectivity 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 161: Line 114:
 {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-005#Statement&noheader&nofooter&noeditbtn}} {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-005#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-005.1784563113.txt.gz
  • Last modified: 2026/07/20 08:58
  • by nick_dido