Differences
This shows you the differences between two versions of the page.
| 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:env-002-configure-test-environment:start [2026/08/18 12:34] – removed - external edit (Unknown date) 127.0.0.1 | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-002-configure-test-environment:start [2026/08/18 13:52] (current) – nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== ENV-002 — Configure Test Environment ====== | ||
| + | [[dido: | ||
| + | |||
| + | ENV-002 is a non-leaf requirement group governing the controlled configuration of each [[dido: | ||
| + | |||
| + | Conformance is assessed against the individual leaf requirements listed below. ENV-002 does not establish a separate conformance obligation. | ||
| + | |||
| + | ===== Contents ===== | ||
| + | |||
| + | {{indexmenu> | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | A controlled [[dido: | ||
| + | |||
| + | 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, | ||
| + | |||
| + | 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 [[dido: | ||
| + | |||
| + | The leaf requirements in this group define the individually verifiable obligations governing Test Environment Configuration and its validation. | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Traceability ===== | ||
| + | |||
| + | {{backlinks> | ||
| + | |||
| + | ===== ConOps Relationship ===== | ||
| + | |||
| + | Add links to the ConOps activities and architecture sections governing Test Environment configuration, | ||
| + | |||
| + | ===== Delivery Phase ===== | ||
| + | |||
| + | Assign the applicable delivery phase. | ||
| + | |||
| + | ===== Requirement Status ===== | ||
| + | |||
| + | Draft | ||
| + | |||
| + | ===== Notes for Editors ===== | ||
| + | |||
| + | 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 '' | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||