====== ENV-002i — Enforce Deployment Constraints ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-002-configure-test-environment:start|Go to ENV-002 — Configure Test Environment]]

===== Statement =====

The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL enforce each deployment [[dido:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraint]] applicable to a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] before and during [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]].

===== Derived From =====

  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5] DIDO-TE Requirements Register]], source requirement identifier and obligation to be assigned
  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-006|[DTE6] Structured Information Processing Reference Architecture (SIP-RA)]]
  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-007|[DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)]]

===== Rationale =====

Deployment [[dido:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraints]] define the permitted placement, allocation, installation, distribution, topology, dependency, and operational conditions governing the elements of a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].

Enforcing these Constraints ensures each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_object|Test Object]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resource]] occupies or uses an applicable [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Target]] under the specified conditions.

Maintaining the required deployment state supports controlled execution, [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], and assessment of whether a deployment difference influenced a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Result]].

===== Applies To =====

  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraint]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Target]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_object|Test Object]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resource]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]

===== 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 [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|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 Environment
  * Inspection of the placement and allocation of Test Objects, Nodes, and Test Resources
  * Inspection of each applicable Deployment Target
  * Inspection of installation, topology, dependency, version, Baseline, and Configuration information
  * Comparison of the instantiated deployment with the controlled Test Environment information
  * Testing for the absence of prohibited deployments
  * Inspection of the resulting Test Environment Configuration and Traceability records
  * A negative assessment using an unsatisfied deployment Constraint before Test Execution
  * Confirmation that the DIDO-TE prevents Test Execution when the Constraint remains unsatisfied
  * A negative assessment introducing a deployment Constraint violation during Test Execution
  * Confirmation that the DIDO-TE identifies and records the violation and its relationship to the affected Test Execution and Test Results

===== Referenced By =====

{{backlinks>.}}

===== 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:

<code dokuwiki>
{{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}}
</code>

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>