====== ENV-003l — Prevent Execution from Invalid Starting State ======

[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:start|Go to ENV-003 — Establish Controlled Starting State]]

===== Statement =====

The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL prevent [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] when validation identifies an invalid controlled starting state.

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

  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:start|ENV-003 — Establish Controlled Starting State]]
  * [[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 =====

An invalid controlled starting state indicates one or more required conditions for [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] remain unsatisfied.

Permitting execution from an invalid state introduces uncontrolled variation, undermines the resulting [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Result]], and weakens [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], [[dido:99_annexes:annex-b-terms-and-definitions:c:comparability|Comparability]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]].

Preventing Test Execution creates an enforceable admission control between starting-state validation and execution. Recording the prevention decision and validation failures provides [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] of the rejected execution attempt.

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

  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraint]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]

===== Verification =====

Verification confirms that:

  * The DIDO-TE evaluates the controlled-starting-state validation result before admitting Test Execution.
  * The DIDO-TE admits Test Execution only when validation produces a valid result.
  * The DIDO-TE prevents Test Execution when validation produces an invalid, incomplete, indeterminate, missing, or expired result.
  * Prevention stops the applicable Test Procedure and participating Nodes or Test Objects from initiating the Test Execution.
  * The DIDO-TE identifies each validation failure responsible for preventing Test Execution.
  * The DIDO-TE records the rejected execution attempt, validation result, identified failures, prevention action, time, and responsible actor or process as [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].
  * The DIDO-TE maintains [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the rejected execution attempt, invalid starting state, validation result, identified failures, prevention action, Test Environment, and Test Definition.
  * The DIDO-TE requires successful revalidation after correction of the starting state and before admission of a subsequent Test Execution.
  * Execution from an invalid, incomplete, indeterminate, unvalidated, or expired starting state constitutes nonconformance with this requirement.

Verification includes:

  * Inspection of the Test Execution admission control
  * Observation of admission following a valid starting-state result
  * A negative assessment using an invalid starting state
  * A negative assessment using an incomplete, indeterminate, missing, or expired validation result
  * Confirmation that the DIDO-TE prevents Test Execution for each negative assessment
  * Confirmation that the applicable Test Procedure and participating Nodes or Test Objects do not initiate the prevented Test Execution
  * Inspection of the recorded validation failures and prevention Evidence
  * Inspection of Traceability records connecting the rejected execution attempt to the invalid state, validation result, prevention action, Test Environment, and Test Definition
  * Correction of the starting state followed by revalidation
  * Confirmation that the DIDO-TE admits Test Execution only after successful revalidation

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

{{backlinks>.}}

===== Related Architecture Sections =====

  * Add links to the architecture sections governing Test Execution admission, starting-state validation, failure handling, Evidence recording, correction, and revalidation.

===== 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-003-establish-controlled-starting-state:env-003l-prevent-execution-from-invalid-starting-state#Statement&noheader&nofooter&noeditbtn}}
</code>

----

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