dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start [2026/08/06 11:12] – created nick_didodido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start [2026/08/06 11:14] (current) – nick_dido
Line 1: Line 1:
-dd+====== MO-006 — Application-Independent and Infrastructure-Independent Testing ====== 
 + 
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]] 
 + 
 +===== Statement ===== 
 + 
 +[[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL support application-independent testing and infrastructure-independent testing. 
 + 
 +===== Derived From ===== 
 + 
 +MO-006 derives from the DIDO-TE mission objective requiring testing which separates: 
 + 
 +  * The [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]], evaluation method, and [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] from a particular application implementation 
 +  * The Test Definition, evaluation method, and Acceptance Criteria from a particular infrastructure implementation, provider, platform, or deployment environment 
 + 
 +MO-006 decomposes into: 
 + 
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006a|MO-006a — Application-Independent Testing]] 
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006b|MO-006b — Infrastructure-Independent Testing]] 
 + 
 +===== Rationale ===== 
 + 
 +Application-independent testing permits DIDO-TE to apply the same governed testing intent to different application implementations without embedding implementation-specific assumptions in the Test Definition, evaluation method, or Acceptance Criteria. 
 + 
 +Infrastructure-independent testing permits DIDO-TE to apply the same governed testing intent across different infrastructure implementations, providers, platforms, and deployment environments without embedding infrastructure-specific assumptions in the governing test. 
 + 
 +Together, these forms of independence support: 
 + 
 +  * Objective comparison of [[dido:99_annexes:annex-b-terms-and-definitions:c:candidate_solution|Candidate Solutions]] 
 +  * Reuse of Test Definitions 
 +  * Consistent application of Acceptance Criteria 
 +  * Separation of testing intent from implementation choices 
 +  * Identification of application-specific and infrastructure-specific effects 
 +  * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] 
 +  * Reproducible comparative evaluation 
 + 
 +Application independence and infrastructure independence do not require identical execution procedures in every Test Environment. Test adaptations preserve the governed testing intent, evaluated characteristics, Acceptance Criteria, and required Evidence. 
 + 
 +===== Applies To ===== 
 + 
 +MO-006 applies to: 
 + 
 +  * DIDO-TE 
 +  * Test Definitions 
 +  * Test Environments 
 +  * Candidate Solutions 
 +  * Evaluation methods 
 +  * Acceptance Criteria 
 +  * Test adaptations 
 +  * Test Results 
 +  * Comparative evaluations 
 + 
 +===== Verification ===== 
 + 
 +Verification confirms that: 
 + 
 +  - MO-006a defines the requirements for application-independent testing 
 +  - MO-006b defines the requirements for infrastructure-independent testing 
 +  - The child requirements preserve the distinction between application independence and infrastructure independence 
 +  - The child requirements preserve the governing Test Definition, evaluated characteristics, Acceptance Criteria, Evidence obligations, and Traceability across permitted test adaptations 
 + 
 +===== Referenced By ===== 
 + 
 +The following pages reference this requirement: 
 + 
 +{{backlinks>.#dido:03-dido-te}} 
 + 
 +===== Delivery Phase ===== 
 + 
 +<todo>Assign the delivery phase for MO-006.</todo> 
 + 
 +===== Implementation Status ===== 
 + 
 +<todo>Record the implementation status of MO-006 after reviewing the implementation plan.</todo> 
 + 
 +===== Requirement Status ===== 
 + 
 +<todo>The proposed derived requirement requires review and acceptance.</todo> 
 + 
 +===== Contents ===== 
 + 
 +{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-006#1|js navbar nocookie maxjs#1 id#dido_te_mo_006_requirements_nav}} 
 + 
 +---- 
 + 
 +===== Issues ===== 
 + 
 +<todo>Confirm the controlling source statement and citation from which MO-006 derives.</todo> 
 + 
 +<todo>Confirm whether application independence and infrastructure independence apply only to Test Definitions and Acceptance Criteria or also to test procedures, test data, metrics, and Evidence requirements.</todo> 
 + 
 +<todo>Determine the permitted adaptations for application-specific and infrastructure-specific execution without weakening comparability.</todo> 
 + 
 +<todo>Define how DIDO-TE records and approves deviations introduced by application-specific or infrastructure-specific test adaptations.</todo> 
 + 
 +---- 
 + 
 +===== Notes for Editors ===== 
 + 
 +MO-006 is a non-leaf requirement page. Its child requirements contain the separately verifiable normative obligations. 
 + 
 +The explicit child links remain on this page until MO-006a and MO-006b have been created and finalised. The links may then be removed because the indexmenu discovers the child pages automatically. 
 + 
 +---- 
 + 
 +<WRAP centeralign> 
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. 
 +</WRAP>
  • dido/03-dido-te/99-annexes/annex-c-requirements/01-mission-objectives/mo-006/start.1786039931.txt.gz
  • Last modified: 2026/08/06 11:12
  • by nick_dido