FR-DSO-006 — Automated Validation Execution

Go to C.3.8 DevSecOps Integration

Crucible SHALL execute automated Validation Operations.

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.[C1]

FR-DSO-006:

• Replaces The system with the defined system name 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 Validation Operation to its controlling definition

No other substantive normalization is required.

An automated Validation Operation evaluates an identified subject against defined Acceptance Criteria without requiring interactive execution by an operator.

Automated Validation Operations enable repeatable evaluation within Development, Security, and Operations (DevSecOps) Workflows, GitOps Workflows, and CI/CD Pipelines.

A Validation Operation can evaluate:

• An Artifact
• A Build Operation result
• A Deployment
• A Deployment Operation result
• An Infrastructure Configuration
• An Infrastructure Environment
• A Platform Service
• A Workload
• A 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 CI/CD Pipeline
• Compliance evaluation
• Security assessment
• Remediation
• Approval
• Authorization

Separate requirements, architecture specifications, validation definitions, and Workflow definitions govern those subjects and behaviors.

This requirement applies to:

• Crucible
• Automated Validation Operations
• Validation subjects
• Acceptance Criteria
• DevSecOps Workflows
• GitOps Workflows
• CI/CD Pipelines

Verification confirms that:

1. A Validation Operation, an identified validation subject, and defined Acceptance Criteria are selected for testing
2. Crucible initiates the selected Validation Operation without interactive operator execution
3. Crucible executes the selected Validation Operation
4. The Validation Operation evaluates the selected subject against the defined Acceptance Criteria
5. The Validation Operation completes with an observable result
6. The resulting validation status, observations, or failure information can be identified

The following pages reference this requirement:

Implemented and Verified

Review and approve FR-DSO-006 as a leaf requirement.

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.

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:

• 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}}