ENV-003k — Record Controlled Starting State

Go to ENV-003 — Establish Controlled Starting State

Before each Test Execution, the DIDO-TE SHALL record the validated controlled starting state as Evidence.

• ENV-003 — Establish Controlled Starting State
• [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)

Recording the validated controlled starting state preserves the conditions under which a Test Execution began.

The record identifies the applied Baseline, Configuration values, participating Nodes, Test Objects, provisioned Test Resources, loaded Test Inputs, communication relationships, applicable Constraints, residual-state dispositions, and validation result.

This Evidence supports interpretation of the resulting Test Results, investigation of differences, Reproducibility, Comparability, and Traceability.

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

Verification confirms that:

• The DIDO-TE records the validated controlled starting state before each Test Execution.
• The record identifies the applicable Test Environment, Test Definition, and Test Execution.
• The record identifies the applied Baseline and Configuration values.
• The record identifies the participating Nodes and Test Objects and their initial states.
• The record identifies the provisioned Test Resources and loaded Test Inputs.
• The record identifies the established communication relationships.
• The record identifies the applicable Constraints and their evaluation results.
• The record identifies detected residual state and its removal or isolation disposition.
• The record contains the starting-state validation result and each identified difference.
• The record contains the time of validation and the identity of the validating process or responsible actor.
• The record protects the integrity of the recorded Evidence.
• The DIDO-TE maintains Traceability among the starting-state Evidence, its constituent records, the controlled descriptive information, Test Environment, Test Definition, and Test Execution.
• Missing, incomplete, inconsistent, altered, unsupported, or untraceable starting-state Evidence constitutes nonconformance with this requirement.

Verification includes:

• Inspection of the recorded controlled starting state
• Inspection of Baseline and Configuration records
• Inspection of Node and Test Object initial-state records
• Inspection of Test Resource and Test Input records
• Inspection of communication-relationship and Constraint records
• Inspection of residual-state disposition records
• Inspection of the validation result and identified differences
• Inspection of validation time and actor or process identity
• Integrity verification of the recorded Evidence
• Inspection of Traceability records connecting the Evidence to the controlled descriptive information, Test Environment, Test Definition, and Test Execution
• A negative assessment using missing, incomplete, altered, or untraceable starting-state Evidence
• Confirmation that the negative assessment produces a nonconformance result

• Add links to the architecture sections governing starting-state Evidence, Evidence integrity, Evidence retention, Traceability, and Test Result interpretation.

Assign the applicable delivery phase.

Draft

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-003k-record-controlled-starting-state#Statement&noheader&nofooter&noeditbtn}}