ENV-003l — Prevent Execution from Invalid Starting State

Go to ENV-003 — Establish Controlled Starting State

Statement

The DIDO-TE SHALL prevent Test Execution when validation identifies an invalid controlled starting state.

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

An invalid controlled starting state indicates one or more required conditions for Test Execution remain unsatisfied.

Permitting execution from an invalid state introduces uncontrolled variation, undermines the resulting Test Result, and weakens Reproducibility, Comparability, and Traceability.

Preventing Test Execution creates an enforceable admission control between starting-state validation and execution. Recording the prevention decision and validation failures provides Evidence of the rejected execution attempt.

Applies To

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 Evidence.The DIDO-TE maintains 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 controlObservation of admission following a valid starting-state resultA negative assessment using an invalid starting stateA negative assessment using an incomplete, indeterminate, missing, or expired validation resultConfirmation that the DIDO-TE prevents Test Execution for each negative assessmentConfirmation that the applicable Test Procedure and participating Nodes or Test Objects do not initiate the prevented Test ExecutionInspection of the recorded validation failures and prevention EvidenceInspection of Traceability records connecting the rejected execution attempt to the invalid state, validation result, prevention action, Test Environment, and Test DefinitionCorrection of the starting state followed by revalidationConfirmation that the DIDO-TE admits Test Execution only after successful revalidation

Referenced By

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:

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

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