| 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:start [2026/08/18 14:06] – nick_dido | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:start [2026/08/19 18:05] (current) – nick_dido |
|---|
| |
| The requirements address the controlled information, state, environmental conditions, resources, relationships, and behavior required to establish and evaluate Test Environments used for [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]. | The requirements address the controlled information, state, environmental conditions, resources, relationships, and behavior required to establish and evaluate Test Environments used for [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]. |
| | |
| | The requirements in this section derive from the source documents identified in Annex B. Some requirements derive directly from those sources. Others normalize or decompose source concepts into individually verifiable architectural [[dido:99_annexes:annex-b-terms-and-definitions:o:obligation|Obligations]]. |
| |
| Some requirements are organized as non-leaf requirement groups containing individually verifiable leaf requirements. Other requirements establish individual normative obligations directly. | Some requirements are organized as non-leaf requirement groups containing individually verifiable leaf requirements. Other requirements establish individual normative obligations directly. |
| |
| ===== Contents ===== | ===== Requirements ===== |
| |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-001-define-test-environment:start|ENV-001 — Define Test Environment]] | ^ Requirement ID ^ Requirement Title ^ Primary Source Basis ^ |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-002-configure-test-environment:start|ENV-002 — Configure Test Environment]] | | ENV-001 | Define Test Environment | [[dido:03-dido-te:99-annexes:annex-b-references:dte-004|[DTE4]]], //Test Environment Package//; [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2]]], Appendix A | |
| * [[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]] | | ENV-002 | Configure Test Environment | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], Figure 2 and configuration concepts; [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2]]], Appendix A | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-004-provide-deterministic-test-environment:start|ENV-004 — Provide Deterministic Test Environment]] | | ENV-003 | Establish Controlled Starting State | [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2]]], Section 1.1, //Submitted Concept and Novelty// | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-005-emulate-distributed-systems:start|ENV-005 — Emulate Distributed Systems]] | | ENV-004 | Provide Deterministic Test Environment | [[dido:03-dido-te:99-annexes:annex-b-references:dte-003|[DTE3]]], Section 2.1.1, //Deterministic States//; SOW Section 1.2 | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-006-reproduce-real-world-conditions|ENV-006 — Reproduce Real-World Conditions]] | | ENV-005 | Emulate Distributed Systems | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], Abstract and Figure 2; [[dido:03-dido-te:99-annexes:annex-b-references:dte-003|[DTE3]]], SOW Section 2.1.1, Primary Goal 1 | |
| * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-007-support-repeatable-test-environments|ENV-007 — Support Repeatable Test Environments]] | | ENV-006 | Reproduce Real-World Conditions | [[dido:03-dido-te:99-annexes:annex-b-references:dte-003|[DTE3]]], Sections 2.1.1 and 2.2.1 | |
| | | ENV-007 | Support Repeatable Test Environments | [[dido:03-dido-te:99-annexes:annex-b-references:dte-003|[DTE3]]], Section 2.1.1, //Repeatable Testing Scenarios//; [[dido:03-dido-te:99-annexes:annex-b-references:dte-004|[DTE4]]], //Test Environment Package// | |
| | |
| | ===== Contents ===== |
| |
| {{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements#1|js navbar nocookie maxjs#2 id#dido_te_test_environment_requirements_nav}} | {{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements#1|js navbar nocookie maxjs#2 id#dido_te_test_environment_requirements_nav}} |
| ===== Notes for Editors ===== | ===== Notes for Editors ===== |
| |
| The explicit links remain while the Test Environment requirement hierarchy is being created and reviewed. After all requirement pages are finalized, the explicit links may be removed because the ''indexmenu'' automatically discovers them. | The explicit links remain while the Test Environment requirement hierarchy is being created and reviewed. After all requirement pages are finalized, you may remove the explicit links because the ''indexmenu'' automatically discovers them. |
| |
| Legacy Test Environment Configuration requirements using the ''FR'' prefix shall be dispositioned against the corresponding ''ENV'' requirements before the legacy requirement pages are retired. | Disposition legacy Test Environment Configuration requirements using the ''FR'' prefix against the corresponding ''ENV'' requirements before retiring the legacy requirement pages. |
| |
| Preserve legacy requirement identifiers and traceability when a requirement is superseded. Do not reuse a retired requirement identifier for another requirement. | Preserve legacy requirement identifiers and traceability when a requirement is superseded. Do not reuse a retired requirement identifier for another requirement. |