dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:env-003j-validate-controlled-starting-state

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:env-003j-validate-controlled-starting-state [2026/08/18 12:34] – removed - external edit (Unknown date) 127.0.0.1dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:env-003j-validate-controlled-starting-state [2026/08/18 12:34] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== ENV-003j — Validate Controlled 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 =====
 +
 +Before each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]], the [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL validate the controlled starting state against the controlled descriptive information governing the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].
 +
 +===== 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 =====
 +
 +Validation determines whether the established starting state corresponds to the required [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]], [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]], participating [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:t:test_object|Test Objects]], [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resources]], [[dido:99_annexes:annex-b-terms-and-definitions:t:test_input|Test Inputs]], communication relationships, and applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraints]].
 +
 +Validation also confirms the absence or effective isolation of residual state excluded from the required starting state.
 +
 +A validated starting state provides an inspectable basis for admitting a Test Execution and interpreting its resulting [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]].
 +
 +===== 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:n:node|Node]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_object|Test Object]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resource]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_input|Test Input]]
 +  * [[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 validates the controlled starting state before each Test Execution.
 +  * Validation uses the applicable controlled descriptive information.
 +  * Validation confirms application of the required Baseline.
 +  * Validation confirms application of the required Configuration values.
 +  * Validation confirms the required initial state of each participating Node and Test Object.
 +  * Validation confirms the availability and required state of each Test Resource and Test Input.
 +  * Validation confirms establishment of each required communication relationship.
 +  * Validation confirms satisfaction of each applicable Constraint.
 +  * Validation confirms removal or effective isolation of prohibited residual state.
 +  * Validation produces an explicit valid or invalid result.
 +  * The DIDO-TE identifies each difference between the required and actual starting states.
 +  * The DIDO-TE records each validation result and identified difference 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 validation result, identified differences, controlled descriptive information, Test Environment, and applicable Test Execution.
 +  * An incomplete, incorrect, indeterminate, unsupported, or untraceable validation result constitutes nonconformance with this requirement.
 +
 +Verification includes:
 +
 +  * Inspection of the controlled descriptive information used for validation
 +  * Observation of controlled-starting-state validation
 +  * Inspection of Baseline and Configuration validation results
 +  * Inspection of Node, Test Object, Test Resource, and Test Input validation results
 +  * Inspection of communication-relationship and Constraint validation results
 +  * Inspection of residual-state validation results
 +  * Inspection of the explicit valid or invalid result
 +  * Inspection of identified differences between the required and actual starting states
 +  * Inspection of validation Evidence and Traceability records
 +  * A negative assessment using an incomplete or incorrect starting state
 +  * Confirmation that the negative assessment produces an invalid result and identifies the applicable differences
 +
 +===== Referenced By =====
 +
 +{{backlinks>.}}
 +
 +===== Related Architecture Sections =====
 +
 +  * Add links to the architecture sections governing starting-state validation, validation criteria, difference detection, Evidence, Traceability, 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:
 +
 +<code dokuwiki>
 +{{section>dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-003-establish-controlled-starting-state:env-003j-validate-controlled-starting-state#Statement&noheader&nofooter&noeditbtn}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>