| 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-001-define-test-environment:start [2026/08/18 12:34] – ↷ Page moved from dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-001-define-test-environment:start to dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env- nick_dido | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-001-define-test-environment:start [2026/08/18 16:09] (current) – nick_dido |
|---|
| ====== ENV-001 — Define Test Environment ====== | ====== ENV-001 — Define Test Requirements ====== |
| |
| [[dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:start|Go to C.2 Test Environment 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]]. | 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]]. |
| |
| ===== Contents ===== | ===== 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}} |
| |
| {{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-001-define-test-environment#1|js navbar nocookie maxjs#1}} | ===== Source ===== |
| | |
| ===== Derived From ===== | |
| |
| * [[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-005|[DTE5] DIDO-TE Requirements Register]], source requirement identifiers and obligations to be assigned |
| ===== Rationale ===== | ===== Rationale ===== |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] requires explicit and controlled descriptive information before the DIDO-TE deploys, operates, reproduces, or evaluates it. | 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. | 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 allows the DIDO-TE to determine precisely which information is complete, missing, inapplicable, or nonconforming. | Separating these obligations supports precise determination of which information is complete, missing, inapplicable, or nonconforming. |
| |
| ===== Applies To ===== | ===== Applies To ===== |
| * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] |
| |
| ===== Referenced By ===== | ===== Traceability ===== |
| |
| {{backlinks>.}} | {{backlinks>.}} |
| |
| ===== Related Architecture Sections ===== | ===== ConOps Relationship ===== |
| |
| * Add links to the architecture sections governing the definition and controlled description of a Test Environment. | Add links to the ConOps activities and architecture sections governing the definition and controlled description of a Test Environment. |
| |
| ===== Delivery Phase ===== | ===== Delivery Phase ===== |
| ===== Notes for Editors ===== | ===== Notes for Editors ===== |
| |
| The explicit child links remain on this non-leaf page while the leaf requirements are being created. After all child pages have been created and finalized, the explicit links may be removed because the ''indexmenu'' automatically discovers the leaf pages. | 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 have been removed. Their normative and verification content belongs in ENV-001a through ENV-001k. | The former ENV-001 Statement and Verification sections were removed because ENV-001a through ENV-001k define their normative and verification content. |
| |
| ---- | ---- |