FR-BAS-003 — Process Predeployment and Postdeployment Steps

Go to C.3.9 Baseline Composition and Workspace

Crucible SHALL process predeployment and postdeployment steps.

This requirement derives from:

• Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-BAS-003

The Original Requirement states:

The system shall process predeployment and postdeployment steps.[C1]

FR-BAS-003:

• Replaces The system with the defined system name Crucible
• Changes shall to the established uppercase normative form SHALL
• Retains the direct behavior process
• Retains both predeployment and postdeployment steps as source-defined subjects

No other substantive normalization is required.

Predeployment steps perform activities required before a Deployment Operation begins.

Postdeployment steps perform activities required after a Deployment Operation completes.

These steps allow a Workspace execution to coordinate activities that occur immediately before and after deployment without embedding those activities into the Deployment Operation itself.

Predeployment steps can include:

• Preparing deployment inputs
• Evaluating prerequisites
• Resolving Workspace content
• Generating configuration
• Preparing credentials or access information
• Evaluating deployment conditions

Postdeployment steps can include:

• Collecting deployment results
• Recording deployment status
• Performing cleanup
• Generating Evidence
• Initiating a Validation Operation
• Publishing execution results

This requirement establishes processing of predeployment and postdeployment steps without prescribing:

• Particular predeployment steps
• Particular postdeployment steps
• A required number of steps
• A step definition format
• Step ordering beyond their relationship to deployment
• A step execution engine
• A scripting language
• A particular Deployment Operation
• A particular Deployment Target
• Failure-handling behavior
• Rollback behavior
• Validation behavior

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

This requirement applies to:

• Crucible
• Predeployment steps
• Postdeployment steps
• Workspace execution
• Deployment Operations

Verification confirms that:

1. A Workspace execution containing at least one predeployment step and at least one postdeployment step is selected for testing
2. Crucible processes the selected predeployment step before the associated Deployment Operation
3. Crucible processes the associated Deployment Operation
4. Crucible processes the selected postdeployment step after the associated Deployment Operation
5. The result of each processed step can be identified
6. The observed execution order distinguishes the predeployment and postdeployment steps

The following pages reference this requirement:

Implemented and Verified

Review and approve FR-BAS-003 as a leaf requirement.

Determine whether Predeployment Step and Postdeployment Step require controlled definitions in the shared Terms and Definitions corpus.

Determine whether separate requirements define the representation, ordering, inputs, outputs, and status of deployment-related steps.

Determine whether separate requirements govern step failure handling, retry behavior, rollback, and continuation.

This requirement page retains the stable requirement identifier FR-BAS-003.

This page is a leaf requirement page and omits a trailing :start from its namespace.

The Statement addresses processing of both predeployment and postdeployment steps.

Predeployment steps execute before the associated Deployment Operation. Postdeployment steps execute after the associated Deployment Operation.

FR-BAS-001 governs consumption of Baseline Repositories from a Workspace.

FR-BAS-002 governs composition of selected Baselines.

FR-BAS-004 governs noninteractive Workspace execution.

Do not add particular deployment-related steps, execution engines, scripting languages, ordering rules, failure-handling behavior, rollback behavior, or validation 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-09-baseline-composition-and-workspace:fr-bas-003#Statement&noheader&nofooter&noeditbtn}}