ENV-002i — Enforce Deployment Constraints

Go to ENV-002 — Configure Test Environment

Statement

The DIDO-TE SHALL enforce each deployment Constraint applicable to a Test Environment before and during Test Execution.

Derived From

, source requirement identifier and obligation to be assigned[DTE6] Structured Information Processing Reference Architecture (SIP-RA)[DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)

Rationale

Deployment Constraints define the permitted placement, allocation, installation, distribution, topology, dependency, and operational conditions governing the elements of a Test Environment.

Enforcing these Constraints ensures each Test Object, Node, and Test Resource occupies or uses an applicable Deployment Target under the specified conditions.

Maintaining the required deployment state supports controlled execution, Reproducibility, and assessment of whether a deployment difference influenced a Test Result.

Applies To

Verification

Verification confirms that:

The DIDO-TE identifies every deployment Constraint applicable to the Test Environment.The DIDO-TE enforces each applicable deployment Constraint before and during Test Execution.Each Test Object, Node, and Test Resource occupies or uses an applicable Deployment Target.Each deployed element satisfies its specified placement, allocation, installation, topology, dependency, version, Baseline, and Configuration conditions.The instantiated Test Environment excludes deployments prohibited by its controlled information.The DIDO-TE records the resulting deployment state as part of the Test Environment Configuration.The DIDO-TE maintains Traceability among each deployment Constraint, the affected element, its Deployment Target, and the applicable Test Execution.The DIDO-TE prevents Test Execution when a required deployment Constraint remains unsatisfied before execution.The DIDO-TE identifies a deployment Constraint violation occurring during Test Execution and records its relationship to the affected Test Execution and Test Results.A missing, unenforced, violated, prohibited, or untraceable deployment condition constitutes nonconformance with this requirement.Verification includes:

Inspection of the deployment Constraints applicable to the Test EnvironmentInspection of the placement and allocation of Test Objects, Nodes, and Test ResourcesInspection of each applicable Deployment TargetInspection of installation, topology, dependency, version, Baseline, and Configuration informationComparison of the instantiated deployment with the controlled Test Environment informationTesting for the absence of prohibited deploymentsInspection of the resulting Test Environment Configuration and Traceability recordsA negative assessment using an unsatisfied deployment Constraint before Test ExecutionConfirmation that the DIDO-TE prevents Test Execution when the Constraint remains unsatisfiedA negative assessment introducing a deployment Constraint violation during Test ExecutionConfirmation that the DIDO-TE identifies and records the violation and its relationship to the affected Test Execution and Test Results

Referenced By

Related Architecture Sections

Add links to the architecture sections governing deployment Constraints, Deployment Targets, topology, allocation, Baseline control, and deployment validation.

Delivery Phase

Assign the applicable delivery phase.

Requirement Status

Draft

Statement Reference

Use the following syntax to reference this requirement’s Statement section from another DokuWiki page:

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-002-configure-test-environment:env-002i-enforce-deployment-constraints#Statement&noheader&nofooter&noeditbtn}}

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.