ENV-002 — Configure Test Environment

Go to C.3.1 Test Environment Requirements

ENV-002 is a non-leaf requirement group governing the controlled configuration of each Test Environment before Test Execution.

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

• [DTE5] DIDO-TE Requirements Register, source requirement identifier and obligation to be assigned
• [DTE6] Structured Information Processing Reference Architecture (SIP-RA)
• [DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)

A controlled Configuration establishes the operating state of a Test Environment before Test Execution.

Configuring the Test Environment according to its controlled descriptive information establishes consistency between the defined environment and its instantiated state.

Recording the resulting Configuration preserves the information required to reproduce the Test Environment, compare separate Test Executions, identify environmental differences, and interpret the resulting Test Results.

Validation before Test Execution prevents a Test Execution performed in an incorrectly configured Test Environment from being represented as originating from the specified Test Environment and Baseline.

The leaf requirements in this group define the individually verifiable obligations governing Test Environment Configuration and its validation.

• Test Environment
• Test Definition
• Test Object
• Node
• Test Resource
• Deployment Target
• Baseline
• Configuration
• Constraint
• Test Execution
• Evidence

Add links to the ConOps activities and architecture sections governing Test Environment configuration, provisioning, validation, and Baseline control.

Assign the applicable delivery phase.

Draft

The subordinate leaf requirements ENV-002a through ENV-002l define the normative obligations and corresponding verification criteria for ENV-002.

We removed the former ENV-002 Statement and Verification sections because ENV-002 is a non-leaf requirement group and does not establish an independently verifiable conformance obligation.

After you create and finalize all subordinate requirement pages, you may remove explicit child links because the indexmenu automatically discovers the leaf pages.