| 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:start [2026/08/18 12:34] – ↷ Page moved from dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-003-establish-controlled-starting-state:start to dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requi nick_dido | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:start [2026/08/18 13:57] (current) – nick_dido |
|---|
| ====== ENV-003 — Establish Controlled Starting State ====== | ====== ENV-003 — Establish Controlled Starting State ====== |
| |
| [[dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:start|Go to C.2 Test Environment Requirements]] | [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:start|Go to C.3.1 Test Environment Requirements]] |
| |
| ===== Statement ===== | ENV-003 is a non-leaf requirement group governing establishment of a controlled starting state for the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] before each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]. |
| |
| 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 establish a controlled starting state for the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]. | Conformance is assessed against the individual leaf requirements listed below. ENV-003 does not establish a separate conformance obligation. |
| |
| The controlled starting state SHALL: | ===== Contents ===== |
| |
| * Apply the required [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] | {{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state#1|js navbar nocookie maxjs#1 id#dido_te_env_003_requirements_nav}} |
| * Apply the required [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] values | |
| * Initialise each participating [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] | |
| * Initialise each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_object|Test Object]] | |
| * Provision each required [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resource]] | |
| * Load each required [[dido:99_annexes:annex-b-terms-and-definitions:t:test_input|Test Input]] | |
| * Establish each required communication relationship | |
| * Apply each applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraint]] | |
| * Remove or isolate residual state from prior Test Executions | |
| * Validate the resulting starting state against the controlled descriptive information governing the Test Environment | |
| * Record the validated starting state as [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | |
| |
| The DIDO-TE SHALL NOT begin the Test Execution when the starting state fails validation. | ===== Source ===== |
| | |
| ===== Derived Requirements ===== | |
| | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-003-establish-controlled-starting-state:env-003a-apply-required-baseline|ENV-003a — Apply Required Baseline]] | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-003-establish-controlled-starting-state:env-003b-apply-required-configuration-values|ENV-003b — Apply Required Configuration Values]] | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-003-establish-controlled-starting-state:env-003c-initialise-participating-nodes|ENV-003c — Initialise Participating Nodes]] | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-003-establish-controlled-starting-state:env-003d-initialise-test-objects|ENV-003d — Initialise Test Objects]] | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-003-establish-controlled-starting-state:env-003e-provision-required-test-resources|ENV-003e — Provision Required Test Resources]] | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-003-establish-controlled-starting-state:env-003f-load-required-test-inputs|ENV-003f — Load Required Test Inputs]] | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-003-establish-controlled-starting-state:env-003g-establish-required-communication-relationships|ENV-003g — Establish Required Communication Relationships]] | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-003-establish-controlled-starting-state:env-003h-apply-applicable-constraints|ENV-003h — Apply Applicable Constraints]] | |
| * [[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|ENV-003i — Remove or Isolate Residual State]] | |
| * [[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|ENV-003j — Validate Controlled Starting State]] | |
| * [[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|ENV-003k — Record Controlled Starting State]] | |
| * [[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|ENV-003l — Prevent Execution from Invalid Starting State]] | |
| | |
| ===== Derived From ===== | |
| |
| * [[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-005|[DTE5] DIDO-TE Requirements Register]], source requirement identifier and obligation to be assigned |
| |
| Validating and recording the controlled starting state supports [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], [[dido:99_annexes:annex-b-terms-and-definitions:c:comparability|Comparability]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]. | Validating and recording the controlled starting state supports [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], [[dido:99_annexes:annex-b-terms-and-definitions:c:comparability|Comparability]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]. |
| | |
| | The leaf requirements in this group define the individually verifiable obligations governing establishment, validation, and recording of the controlled starting state. |
| |
| ===== Applies To ===== | ===== Applies To ===== |
| * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] |
| |
| ===== Verification ===== | ===== Traceability ===== |
| | |
| Verification confirms that: | |
| | |
| * The DIDO-TE establishes a controlled starting state before each Test Execution. | |
| * The starting state contains the required Baseline and Configuration values. | |
| * The starting state contains the required Nodes, Test Objects, Test Resources, and Test Inputs. | |
| * The starting state contains the required communication relationships. | |
| * The starting state satisfies each applicable Constraint. | |
| * The DIDO-TE removes or isolates residual state from prior Test Executions. | |
| * The DIDO-TE validates the resulting starting state against the controlled descriptive information governing the Test Environment. | |
| * The DIDO-TE records the validated starting state as Evidence. | |
| * The DIDO-TE maintains [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the starting-state Evidence, applicable Baseline, Configuration, Test Definition, Test Environment, and Test Execution. | |
| * The DIDO-TE prevents Test Execution when the starting state fails validation. | |
| * The DIDO-TE records each starting-state validation failure as Evidence. | |
| * A missing, incomplete, invalid, residual, or untraceable starting state constitutes nonconformance with this requirement. | |
| | |
| Verification includes: | |
| | |
| * Inspection of the controlled descriptive information governing the Test Environment | |
| * Inspection of the applicable Baseline and Configuration records | |
| * Inspection of Node and Test Object initialisation records | |
| * Inspection of Test Resource provisioning records | |
| * Inspection of Test Input loading records | |
| * Inspection of the established communication relationships | |
| * Inspection of applicable Constraint enforcement records | |
| * Inspection of starting-state validation Evidence | |
| * Inspection of Traceability records | |
| * Repetition of a Test Execution from the same controlled starting state | |
| * A negative assessment using a starting state that differs from the required state | |
| * A residual-state assessment following a prior Test Execution | |
| * Confirmation that the DIDO-TE prevents Test Execution when starting-state validation fails | |
| * Inspection of Evidence recording the validation failure | |
| | |
| ===== Referenced By ===== | |
| |
| {{backlinks>.}} | {{backlinks>.}} |
| |
| ===== Related Architecture Sections ===== | ===== ConOps Relationship ===== |
| |
| * Add links to the architecture sections governing Test Environment initialisation, state control, residual-state isolation, validation, Evidence, and Test Execution admission. | Add links to the ConOps activities and architecture sections governing Test Environment initialization, state control, residual-state isolation, validation, Evidence, and Test Execution admission. |
| |
| ===== Delivery Phase ===== | ===== Delivery Phase ===== |
| Draft | Draft |
| |
| ===== Statement Reference ===== | ===== Notes for Editors ===== |
| | |
| | The subordinate leaf requirements ENV-003a through ENV-003l define the normative obligations and corresponding verification criteria for ENV-003. |
| |
| Use the following syntax to reference this requirement’s Statement section from another DokuWiki page: | 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. |
| |
| <code dokuwiki> | 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. |
| {{section>dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-003-establish-controlled-starting-state:start#Statement&noheader&nofooter&noeditbtn}} | |
| </code> | |
| |
| ---- | ---- |