dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-001

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-001 [2026/07/20 07:08] – ↷ Links adapted because of a move operation nick_didodido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-001 [2026/07/30 05:44] (current) – nick_dido
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL deploy identified infrastructure resources to a target [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]].+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL deploy [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_resource|Infrastructure Resources]].
  
-===== Source Statement =====+===== Derived From =====
  
-> The system shall deploy infrastructure resources.+This requirement derives from:
  
-===== Source =====+  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-001
  
-Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-001.+The Original Requirement states:
  
-===== Assessment =====+> //The system shall deploy infrastructure resources.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-The source statement expresses a direct functional behavior but requires terminology and normative-language normalization.+FR-DEP-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** 
 +  * Links **Infrastructure Resources** 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 +
-  * **Infrastructure resources** identifies the deployment subject but does not identify the target environment +
-  * The source statement does not prescribe a resource type, provider, deployment tool, interface, or implementation method +
-  * The source statement does not independently require deployment validation, rollback, compliance assessment, or lifecycle recording +
- +
-The normalized Statement: +
- +
-  * Replaces **The system** with [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] +
-  * Retains the direct and testable verb **deploy** +
-  * Identifies the infrastructure resources as the deployment subjects +
-  * Identifies a target Infrastructure Environment +
-  * Preserves implementation independence +
-  * Retains one primary required behavior +
- +
-The normalized Statement does not prescribe which infrastructure resources apply to a particular deployment. The applicable [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]] identifies those resources.+
  
 ===== Rationale ===== ===== Rationale =====
  
-Infrastructure resources establish the computing, storage, networking, security, identity, and related capabilities required by an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]].+[[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_resource|Infrastructure Resources]] provide the compute, storage, networking, security, identity, and supporting capabilities required by infrastructure.
  
-Infrastructure resources may include:+Deploying Infrastructure Resources enables Crucible to realize infrastructure definitions through separately governed deployment workflows.
  
-  * Compute resources +This requirement establishes the deployment behavior without prescribing:
-  * Storage resources +
-  * Network resources +
-  * Identity resources +
-  * Security resources +
-  * Load-balancing resources +
-  * Monitoring resources +
-  * Logging resources +
-  * Name-resolution resources +
-  * Key-management resources +
-  * Provider-managed services+
  
-The deployment operation realizes the applicable [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]] within the target Infrastructure Environment.+  * The Infrastructure Resources included in a particular deployment 
 +  * The target environment 
 +  * The deployment platform 
 +  * The deployment tool 
 +  * The deployment sequence 
 +  * Deployment validation 
 +  * Deployment rollback 
 +  * Compliance assessment
  
-Infrastructure-resource deployment contributes to: +Separate requirements define those subjects and behaviors.
- +
-  * Repeatable environment creation +
-  * Consistent infrastructure state +
-  * Automated environment establishment +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]+
  
 ===== Applies To ===== ===== Applies To =====
Line 72: Line 49:
  
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
-  * Infrastructure resources +  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_resource|Infrastructure Resources]]
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configurations]]+
   * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]]   * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]]
-  * Compute resources 
-  * Storage resources 
-  * Network resources 
-  * Identity resources 
-  * Security resources 
-  * Monitoring resources 
-  * Logging resources 
-  * Deployment tools 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementations]] 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]] 
  
 ===== Verification ===== ===== Verification =====
  
-  - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] executes a deployment operation for identified infrastructure resources +Verification confirms that:
-  - Verification SHALL confirm that the deployment operation targets an identified [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] +
-  - Verification SHALL confirm that the identified infrastructure resources exist in the target Infrastructure Environment after successful deployment+
  
-Verification may include: +  - One or more Infrastructure Resources are selected for deployment 
- +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] executes a deployment operation for the selected Infrastructure Resources 
-  * Infrastructure-resource deployment testing +  - The completed deployment produces the selected Infrastructure Resources 
-  * Target-environment inspection +  - The resulting Infrastructure Resources can be identified as outputs of the tested deployment
-  * Infrastructure-state inspection +
-  * Provider-interface inspection +
-  * Deployment-output inspection +
-  * Deployment-log inspection +
-  * Automated [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] testing +
- +
-The verification record SHALL identify: +
- +
-  - The deployed infrastructure resources +
-  - The target Infrastructure Environment +
-  - The deployment operation +
-  - The deployment result +
-  - The observed infrastructure state +
-  - 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-001:start|MO-001]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002|MO-002]] +
-  * [[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:fr-cfg-001|FR-CFG-001]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:fr-cfg-002|FR-CFG-002]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-006|FR-DEP-006 — Deployment Rollback]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-007|FR-DEP-007 — Deployment Validation]] +
-  * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]] +
-  * [[dido:02-crusible:10-reproducibility-provenance-and-traceability:start|10. Reproducibility, Provenance, and Traceability]]+
  
 ===== Referenced By ===== ===== Referenced By =====
  
-The wiki Backlinks function provides the current list of pages that reference ''FR-DEP-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}}
- +
-Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship. +
- +
-===== ConOps Relationship ===== +
- +
-The Crucible Concept of Operations describes a Phase 1 workflow that composes controlled configuration inputs and performs [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] through an automated [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]]. +
- +
-FR-DEP-001 establishes the required behavior for deploying infrastructure resources to a target Infrastructure Environment. +
- +
-Requirements governing virtual machines, Kubernetes clusters, containerized workloads, platform services, rollback, and validation define separate deployment behavior. +
- +
-===== Delivery Phase ===== +
- +
-Phase 1+
  
 ===== Implementation Status ===== ===== Implementation Status =====
  
-Not Assessed +Implemented and Verified
- +
-Implementation status requires verification that Crucible deploys identified infrastructure resources to a target Infrastructure Environment.+
  
 ===== Requirement Status ===== ===== Requirement Status =====
  
-Draft +<todo>Review and approve FR-DEP-001 as a leaf requirement.</todo>
- +
-The source System Requirements Specification identifies Version 1.1 as a draft.+
  
 ---- ----
-===== Notes for Editors =====+===== Issues =====
  
-This requirement page should retain the stable requirement identifier ''FR-DEP-001''.+<todo>Determine whether separate requirements identify the source that selects the Infrastructure Resources for a deployment.</todo>
  
-Changes to the Statement SHALL preserve the approved intent of the source requirement.+<todo>Determine whether separate requirements identify the Deployment Target or Infrastructure Environment for the deployed Infrastructure Resources.</todo>
  
-The Source Statement should preserve the original wording from the controlling System Requirements Specification.+---- 
 +===== Notes for Editors =====
  
-The Statement should remain limited to deployment of identified infrastructure resources.+This requirement page retains the stable requirement identifier ''FR-DEP-001''.
  
-Requirements for deployment rollback, validation, compliance assessment, lifecycle recording, and resource retirement should remain in their applicable requirement pages.+This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.+The Statement preserves the approved source intent by requiring Crucible to deploy Infrastructure Resources.
  
-Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.+Do not add a target Infrastructure Environment, Deployment Target, Infrastructure Configuration, deployment-validation, rollback, compliance-assessment, lifecycle-recording, or resource-retirement obligation 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 184: Line 98:
 {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-001#Statement&noheader&nofooter&noeditbtn}} {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-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-03-deployment-orchestration/fr-dep-001.1784556501.txt.gz
  • Last modified: 2026/07/20 07:08
  • by nick_dido