====== FR-DSO-006 — Automated Validation Execution ======
[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:start|Go to C.3.8 DevSecOps Integration]]
===== Statement =====
[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL execute automated [[dido:99_annexes:annex-b-terms-and-definitions:v:validation_operation|Validation Operations]].
===== Derived From =====
This requirement derives from:
* Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DSO-006
The Original Requirement states:
> //The system shall support automated validation execution.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
FR-DSO-006:
* 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 phrase **support automated validation execution** with the direct and observable behavior **execute automated Validation Operations**
* Links [[dido:99_annexes:annex-b-terms-and-definitions:v:validation_operation|Validation Operation]] to its controlling definition
No other substantive normalization is required.
===== Rationale =====
An automated [[dido:99_annexes:annex-b-terms-and-definitions:v:validation_operation|Validation Operation]] evaluates an identified subject against defined [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] without requiring interactive execution by an operator.
Automated Validation Operations enable repeatable evaluation within [[dido:99_annexes:annex-b-terms-and-definitions:d:devsecops|Development, Security, and Operations (DevSecOps)]] [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflows]], [[dido:99_annexes:annex-b-terms-and-definitions:g:gitops|GitOps]] Workflows, and [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]].
A Validation Operation can evaluate:
* An [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]]
* A Build Operation result
* A [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]]
* A [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operation]] result
* An Infrastructure Configuration
* An Infrastructure Environment
* A Platform Service
* A Workload
* A [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle|Transfer Bundle]]
A Validation Operation can produce:
* A successful validation result
* An unsuccessful validation result
* A recorded inability to complete the validation
* Validation observations
* Validation status
* Validation logs
* Validation metadata
This requirement establishes automated Validation Operation execution without prescribing:
* A particular validation tool
* A particular validation subject
* Particular Acceptance Criteria
* A particular validation procedure
* A particular triggering mechanism
* A particular [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]]
* Compliance evaluation
* Security assessment
* Remediation
* Approval
* Authorization
Separate requirements, architecture specifications, validation definitions, and Workflow definitions govern those subjects and behaviors.
===== Applies To =====
This requirement applies to:
* [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
* Automated [[dido:99_annexes:annex-b-terms-and-definitions:v:validation_operation|Validation Operations]]
* Validation subjects
* [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]
* [[dido:99_annexes:annex-b-terms-and-definitions:d:devsecops|DevSecOps]] Workflows
* [[dido:99_annexes:annex-b-terms-and-definitions:g:gitops|GitOps]] Workflows
* [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]]
===== Verification =====
Verification confirms that:
- A [[dido:99_annexes:annex-b-terms-and-definitions:v:validation_operation|Validation Operation]], an identified validation subject, and defined [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] are selected for testing
- [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] initiates the selected Validation Operation without interactive operator execution
- Crucible executes the selected Validation Operation
- The Validation Operation evaluates the selected subject against the defined Acceptance Criteria
- The Validation Operation completes with an observable result
- The resulting validation status, observations, or failure information can be identified
===== Referenced By =====
The following pages reference this requirement:
{{backlinks>.#dido:02-crusible}}
===== Implementation Status =====
Implemented and Verified
===== Requirement Status =====
Review and approve FR-DSO-006 as a leaf requirement.
----
===== Issues =====
Determine whether separate requirements define the required Validation Operation inputs, outputs, metadata, and status information.
Determine whether separate requirements identify the subjects and Acceptance Criteria for which Crucible must execute automated Validation Operations.
Determine whether separate requirements govern validation failure handling, remediation, approval, and result retention.
----
===== Notes for Editors =====
This requirement page retains the stable requirement identifier ''FR-DSO-006''.
This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
The Statement uses the controlling Terms and Definitions entry:
* [[dido:99_annexes:annex-b-terms-and-definitions:v:validation_operation|Validation Operation]]
The Statement addresses execution of automated Validation Operations.
FR-DSO-001 governs integration with Git-based Workflows.
FR-DSO-002 governs integration with GitOps Workflows.
FR-DSO-003 governs integration with CI/CD Pipelines.
FR-DSO-004 governs automated Build Operation execution.
FR-DSO-005 governs automated Deployment Operation execution.
Do not add particular validation tools, validation subjects, Acceptance Criteria, procedures, triggering mechanisms, compliance-evaluation behavior, remediation, approval, or authorization obligations unless the controlling requirement changes through an approved requirements process.
To reference this requirement Statement from another wiki page, insert:
{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:fr-dso-006#Statement&noheader&nofooter&noeditbtn}}
----
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.