dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:start

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:start [2026/08/17 14:25] – 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:start [2026/08/19 18:05] (current) nick_dido
Line 1: Line 1:
 +====== C.3.1 Test Environment Requirements ======
  
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:start|Go to C.3 Functional Requirements]]
 +
 +This section identifies the requirements governing the definition, configuration, establishment, control, emulation, reproduction, and repeatability of a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].
 +
 +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.
 +
 +===== Requirements =====
 +
 +^ Requirement ID ^ Requirement Title ^ Primary Source Basis ^
 +| 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 |
 +| 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 |
 +| 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// |
 +| 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 |
 +| 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 |
 +| 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}}
 +
 +----
 +
 +===== Notes for Editors =====
 +
 +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.
 +
 +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.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>