ENV-003 — Establish Controlled Starting State

Go to C.3.1 Test Environment Requirements

ENV-003 is a non-leaf requirement group governing establishment of a controlled starting state for the applicable Test Environment before each Test Execution.

Conformance is assessed against the individual leaf requirements listed below. ENV-003 does not establish a separate conformance obligation.

• [DTE5] DIDO-TE Requirements Register, 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)

A controlled starting state establishes the conditions under which a Test Execution begins.

Applying the required Baseline, Configuration values, Test Inputs, Test Resources, and Constraints limits differences among repeated Test Executions to the variables governed by the applicable Test Definition.

Removing or isolating residual state prevents a prior Test Execution from influencing a later Test Result.

Validating and recording the controlled starting state supports Reproducibility, Comparability, and Traceability.

The leaf requirements in this group define the individually verifiable obligations governing establishment, validation, and recording of the controlled starting state.

• Test Environment
• Test Definition
• Test Execution
• Test Object
• Node
• Test Resource
• Test Input
• Baseline
• Configuration
• Constraint
• Evidence

Add links to the ConOps activities and architecture sections governing Test Environment initialization, state control, residual-state isolation, validation, Evidence, and Test Execution admission.

Assign the applicable delivery phase.

Draft

The subordinate leaf requirements ENV-003a through ENV-003l define the normative obligations and corresponding verification criteria for ENV-003.

We removed the former ENV-003 Statement and Verification sections because ENV-003 is a non-leaf requirement group and does not establish an independently verifiable conformance obligation.

The explicit child links remain while we create and review the subordinate requirement pages. After we finalize all subordinate pages, we can remove the explicit links because the indexmenu automatically discovers the leaf pages.