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

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-007 [2026/07/17 09:54] – nick_didodido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-007 [2026/07/30 05:50] (current) – nick_dido
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]] by evaluating an identified deployment result against the applicable [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]].+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]].
  
-===== Source Statement =====+===== Derived From =====
  
-> The system shall support [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]].+This requirement derives from:
  
-===== Source =====+  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-007
  
-Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-007.+The Original Requirement states:
  
-===== Assessment =====+> //The system shall support [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]].//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-The source statement expresses the approved intent but does not provide a fully testable formulation.+FR-DEP-007:
  
-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 **Deployment Validation** 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 that does not identify the required behavior +
-  * **[[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]]** names an activity but does not identify the evaluated subject +
-  * The source statement does not identify the criteria used for validation +
-  * The source statement does not identify an observable validation result +
-  * The source statement does not prescribe a validation tool, test framework, provider, validation method, 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 **perform** +
-  * Uses the defined Deployment Validation concept +
-  * Identifies an identified deployment result as the evaluated subject +
-  * Identifies applicable Acceptance Criteria as the evaluation basis +
-  * Retains one primary required behavior +
-  * Preserves implementation independence +
- +
-The normalized Statement does not define the Acceptance Criteria. The applicable deployment specification, [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]], policy, or lower-level requirement defines those criteria.+
  
 ===== Rationale ===== ===== Rationale =====
  
-A completed deployment does not by itself establish that the resulting subject satisfies the conditions required for its intended use.+[[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]] determines whether a deployment result satisfies the conditions governing acceptance of that deployment.
  
-[[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]] evaluates the deployment result against identified [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]].+This requirement establishes the ability to perform Deployment Validation without prescribing:
  
-The evaluated deployment result may include:+  * The deployment subject 
 +  * The validation method 
 +  * The applicable [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] 
 +  * Compliance-assessment behavior 
 +  * Rollback behavior 
 +  * Recovery behavior 
 +  * Preservation of validation results 
 +  * Validation tools or implementation technology
  
-  * Deployed [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_resource|Infrastructure Resources]] +Separate requirements, specifications, workflows, or policies define those subjects and behaviors.
-  * A deployed [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machine]] +
-  * A deployed [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes Cluster]] +
-  * A deployed [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workload]] +
-  * A deployed Platform Service +
-  * A resulting [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] +
-  * Relationships among deployed subjects +
- +
-Acceptance Criteria may evaluate: +
- +
-  * Resource existence +
-  * Required configuration +
-  * Required relationships +
-  * Required operational state +
-  * Required network behavior +
-  * Required identity and access behavior +
-  * Required security controls +
-  * Required service availability +
-  * Required health conditions +
-  * Required compliance results +
- +
-FR-DEP-007 does not independently establish any particular Acceptance Criterion. +
- +
-Deployment Validation differs from deployment execution: +
- +
-  * Deployment execution creates or changes a deployment subject +
-  * Deployment Validation evaluates the resulting state against Acceptance Criteria +
- +
-Deployment Validation differs from compliance assessment: +
- +
-  * Deployment Validation evaluates a deployment result against deployment Acceptance Criteria +
-  * Compliance assessment evaluates a subject against identified compliance criteria +
- +
-Compliance results may form part of the applicable Deployment Validation criteria. +
- +
-Deployment Validation contributes to: +
- +
-  * Detection of incomplete deployments +
-  * Detection of incorrect deployment state +
-  * Controlled acceptance of deployment results +
-  * Rollback or recovery decisions +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:a:auditability|Auditability]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]+
  
 ===== Applies To ===== ===== Applies To =====
Line 100: Line 49:
   * [[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:d:deployment_validation|Deployment Validation]]   * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]]
-  * Deployment results +  * Deployments
-  * [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] +
-  * [[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]] +
-  * Platform Services +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]] +
-  * Deployment workflows +
-  * Validation operations +
-  * Validation results +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]]+
  
 ===== Verification ===== ===== Verification =====
  
-  - Verification SHALL confirm that the tested deployment result is identified +Verification confirms that:
-  - Verification SHALL confirm that the applicable [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] are identified +
-  - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] evaluates the identified deployment result against the applicable Acceptance Criteria +
-  - Verification SHALL confirm that Crucible determines whether the deployment result satisfies each applicable Acceptance Criterion +
-  - Verification SHALL confirm that Crucible records the Deployment Validation result+
  
-Verification may include: +  - A tested Deployment is selected for validation 
- +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]] for the tested Deployment 
-  * Infrastructure Resource validation testing +  - The result of the tested Deployment Validation can be determined
-  * Virtual Machine validation testing +
-  * Kubernetes Cluster validation testing +
-  * Containerized Workload validation testing +
-  * Platform Service validation testing +
-  * Successful-validation testing +
-  * Failed-validation testing +
-  * Acceptance Criteria inspection +
-  * Deployment-result inspection +
-  * Validation-output inspection +
-  * Validation-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 evaluated deployment result +
-  - The applicable Acceptance Criteria +
-  - The observed result for each Acceptance Criterion +
-  - The Deployment Validation operation +
-  - The Deployment Validation 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-001|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-005|MO-005]] +
-  * [[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-03-deployment-orchestration:fr-dep-001|FR-DEP-001 — Deploy Infrastructure Resources]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-002|FR-DEP-002 — Deploy Virtual Machines]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-003|FR-DEP-003 — Deploy Kubernetes Clusters]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-004|FR-DEP-004 — Deploy Containerized Workloads]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-005|FR-DEP-005 — Deploy Platform Services]] +
-  * [[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-06-compliance-management:start|C.3.6 Compliance Management]] +
-  * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]] +
-  * [[dido:02-crusible:09-compliance-and-security:start|9. Compliance and Security]] +
-  * [[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-007''. +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 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 predeployment and postdeployment activities within an automated Phase 1 [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]]. +
- +
-FR-DEP-007 establishes the behavior required to evaluate an identified deployment result against the applicable Acceptance Criteria. +
- +
-Requirements governing deployment execution, compliance assessment, rollback, recovery, logging, and Evidence retention define separate behavior. +
- +
-===== Delivery Phase =====+
  
-Phase 1+{{backlinks>.#dido:02-crusible}}
  
 ===== Implementation Status ===== ===== Implementation Status =====
  
-Not Assessed +Implemented and Verified
- +
-Implementation status requires verification that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs Deployment Validation by evaluating an identified deployment result against the applicable Acceptance Criteria.+
  
 ===== Requirement Status ===== ===== Requirement Status =====
  
-Draft +<todo>Review and approve FR-DEP-007 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-007''.+<todo>Determine whether separate requirements identify the Acceptance Criteria used for Deployment Validation.</todo>
  
-Changes to the Statement SHALL preserve the approved intent of the source requirement.+<todo>Determine whether separate requirements govern preservation of the Deployment Validation result.</todo>
  
-The Source Statement should preserve the original wording from the controlling System Requirements Specification.+---- 
 +===== Notes for Editors =====
  
-The Statement should remain limited to evaluating an identified deployment result against the applicable Acceptance Criteria.+This requirement page retains the stable requirement identifier ''FR-DEP-007''.
  
-The applicable deployment specification, Baseline, policy, or lower-level requirement should define the Acceptance Criteria.+This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-Requirements for deployment execution, compliance assessment, rollback, recovery, logging, and Evidence retention should remain in their applicable requirement pages.+The Statement preserves the approved source intent by requiring Crucible to perform Deployment Validation.
  
-Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations. +Do not add a specific deployment subject, Acceptance Criteria, validation method, compliance-assessment, rollback, recovery, logging, or validation-record obligation unless the controlling requirement changes through an approved requirements process.
- +
-Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.+
  
 To reference this requirement Statement from another wiki page, insert: To reference this requirement Statement from another wiki page, insert:
Line 223: Line 96:
 {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-007#Statement&noheader&nofooter&noeditbtn}} {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-007#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-007.1784307261.txt.gz
  • Last modified: 2026/07/17 09:54
  • by nick_dido