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

This is an old revision of the document!


ENV-001 — Define Test Environment

Go to C.3.1 Test Environment Requirements

ENV-001 is a non-leaf requirement group governing the controlled information used to define each Test Environment.

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

A 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, Configuration, Constraints, versions, and Baseline associated with a Test Environment.

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

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

Assign the applicable delivery phase.

Draft

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.


© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

  • dido/03-dido-te/99-annexes/annex-c-requirements/03-functional-requirements/03-01-test-environment-requirements/env-001-define-test-environment/start.1787086296.txt.gz
  • Last modified: 2026/08/18 13:51
  • by nick_dido