====== ENV-001 — Define Test 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]]

ENV-001 is a non-leaf requirement group governing the controlled information used to define each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].

Conformance is assessed against the individual leaf requirements listed below. ENV-001 does not establish a separate conformance obligation.

===== Contents =====
 
{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-001-define-test-environment#1|js navbar nocookie maxjs#1}}

===== Source =====

  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5] DIDO-TE Requirements Register]], source requirement identifiers and obligations 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 =====

A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] requires explicit and controlled descriptive information before a conforming realization deploys, operates, reproduces, or evaluates it.

The leaf requirements in this group establish the information required to describe the purpose, composition, relationships, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]], [[dido:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraints]], versions, and [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] associated with a Test Environment.

Separating these obligations supports precise determination of which information is complete, missing, inapplicable, or nonconforming.

===== 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_object|Test Object]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resource]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Target]]
  * [[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:c:constraint|Constraint]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]

===== Traceability =====

{{backlinks>.}}

===== ConOps Relationship =====

Add links to the ConOps activities and architecture sections governing the definition and controlled description of a Test Environment.

===== Delivery Phase =====

Assign the applicable delivery phase.

===== Requirement Status =====

Draft

===== Notes for Editors =====

The explicit child links remain on this non-leaf page while you create the leaf requirements. After all child pages are created and finalized, you may remove the explicit links because the ''indexmenu'' automatically discovers the leaf pages.

The former ENV-001 Statement and Verification sections were removed because ENV-001a through ENV-001k define their normative and verification content.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>