ENV-003i — Remove or Isolate Residual State

Go to ENV-003 — Establish Controlled Starting State

Statement

Before each Test Execution, the DIDO-TE SHALL remove or isolate each residual state element not included in the required 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

Residual state includes data, processes, messages, files, caches, temporary resources, communication relationships, credentials, locks, subscriptions, transactions, and other state remaining from a prior activity or Test Execution.

Residual state may alter the behaviour of a Node, Test Object, or supporting Test Resource.

Removing or isolating residual state prevents a prior Test Execution or unrelated activity from influencing a later Test Result. This separation supports Reproducibility and Comparability.

Applies To

Verification

Verification confirms that:

The DIDO-TE identifies residual state before Test Execution.The DIDO-TE determines whether each identified residual state element belongs to the required controlled starting state.The DIDO-TE removes or isolates each residual state element not included in the required controlled starting state.Isolation prevents the residual state element from influencing the applicable Test Execution.Removal or isolation addresses residual data, processes, messages, files, caches, resources, communication relationships, credentials, locks, subscriptions, and transactions, where applicable.The resulting Test Environment contains only state permitted by the controlled descriptive information.The DIDO-TE records each detected residual state element and the action taken.The DIDO-TE maintains Traceability among each residual state element, its originating activity when known, the removal or isolation action, and the applicable Test Execution.Unidentified, unremoved, ineffectively isolated, prohibited, or untraceable residual state constitutes nonconformance with this requirement.Verification includes:

Inspection of the Test Environment following a prior Test ExecutionInspection for residual data, processes, messages, files, caches, resources, communication relationships, credentials, locks, subscriptions, and transactionsObservation of residual-state removal or isolationConfirmation that isolated residual state cannot influence the applicable Test ExecutionComparison of the resulting Test Environment state with the required controlled starting stateInspection of residual-state detection and disposition recordsInspection of Traceability records connecting each residual state element to its origin, disposition, and applicable Test ExecutionRepetition of a Test Execution following a prior Test ExecutionA negative assessment containing prohibited or ineffectively isolated residual stateConfirmation that the negative assessment produces a nonconformance result

Referenced By

Related Architecture Sections

Add links to the architecture sections governing Test Environment reset, state isolation, cleanup, Node lifecycle, Test Resource lifecycle, and Test Execution admission.

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-003i-remove-or-isolate-residual-state#Statement&noheader&nofooter&noeditbtn}}

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