Differences

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

--- dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007:start [2026/08/06 11:48] – ↷ Page moved and renamed from dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007 to dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007:start nick_dido
+++ dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007:start [2026/08/06 12:12] (current) – nick_dido
@@ Line 3: / Line 3: @@
 [[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]]
-===== Statement =====
+===== Original Requirement =====
-[[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL support testing operations in [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]], [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]], and [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]].
+> //[[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL support testing operations in [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]], [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]], and [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]].//
-===== Derived From =====
+===== Assessment of Original Requirement =====
-MO-007 derives from the DIDO-TE mission objective requiring testing operations across environments with different connectivity and isolation characteristics.
+The Original Requirement preserves the approved intent that DIDO-TE conduct testing operations in three types of environment, but it combines three independently testable normative obligations.
-MO-007 decomposes into:
+The following Specification Discipline and Authoring findings apply:
-  * [[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007:mo-007a|MO-007a — Connected Environment Operation]]
+  * **Support** is a weak verb that does not identify an observable DIDO-TE behavior
-  * [[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007:mo-007b|MO-007b — Disconnected Environment Operation]]
+  * **Testing operations** does not identify the operations DIDO-TE performs within each environment type
-  * [[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007:mo-007c|MO-007c — Air-Gapped Environment Operation]]
+  * The requirement combines operation in Connected Environments, Disconnected Environments, and Air-Gapped Environments
+  * The requirement does not identify the distinct connectivity, isolation, transfer, execution, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] obligations associated with each environment type
+  * A single verification result could obscure failure to operate in one or more required environment types
-===== Rationale =====
+The Original Requirement identifies:
-Organizations conduct development, evaluation, qualification, and authorization activities in environments with different connectivity and isolation characteristics.
+  * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]]
-A Connected Environment provides access to permitted external networks and services. A Disconnected Environment operates without active external network connectivity during the relevant operation. An Air-Gapped Environment maintains physical isolation from external networks.
+The decomposition treats operation in each environment type as a separate obligation so that DIDO-TE behavior can be specified and verified independently.
-Support for all three environment types enables DIDO-TE to test [[dido:99_annexes:annex-b-terms-and-definitions:c:candidate_solution|Candidate Solutions]] under conditions representative of their intended operational environments.
+The three environment types impose different constraints upon:
-The three environment types impose distinct requirements for:
   * Access to external networks and services
@@ Line 32: / Line 34: @@
   * Configuration and execution of tests
   * Collection and removal of Test Results
-  * Collection and preservation of logs and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
+  * Collection and preservation of logs and Evidence
   * Integrity, provenance, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
   * Application of security and authorization controls
-The child requirements define the obligations applicable to each environment type.
+The Original Requirement does not identify which testing operations apply to all three environment types or which environment-specific operations require separate treatment.
-===== Applies To =====
+The Original Requirement therefore requires:
-MO-007 applies to:
+  * Replacement of **support** with observable DIDO-TE behaviors
+  * Identification of the testing operations required within each environment type
+  * Separation of the three independently testable environment obligations
+  * Identification of the transfer controls applicable to Disconnected and Air-Gapped Environments
+  * Identification of the connectivity and external-service dependencies permitted within each environment type
+  * Confirmation that the derived requirements collectively preserve the complete intent of MO-007
-  * DIDO-TE
+The decomposition preserves ''MO-007'' as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.
-  * Test Environments
-  * Connected Environments
-  * Disconnected Environments
-  * Air-Gapped Environments
-  * Test Definitions
-  * Transfer Bundles
-  * Candidate Solutions
-  * Test execution
-  * Test Results
-  * Evidence
-  * Environment-specific operating procedures
-===== Verification =====
+===== Proposed Statements =====
-Verification confirms that:
+The Original Requirement is decomposed into the following proposed replacement requirements:
-  - MO-007a defines the requirements for testing operations in Connected Environments
+{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007#1|js navbar nocookie maxjs#1 id#dido_te_mo_007_requirements_nav}}
-  - MO-007b defines the requirements for testing operations in Disconnected Environments
-  - MO-007c defines the requirements for testing operations in Air-Gapped Environments
-  - The child requirements preserve the distinctions among Connected, Disconnected, and Air-Gapped Environments
-  - The child requirements address the introduction of required testing artifacts and the collection of Test Results and Evidence under the applicable connectivity and isolation conditions
-===== Referenced By =====
+===== Requirement Status =====
-The following pages reference this requirement:
+<todo>Review and approve the decomposition of MO-007 into separate Connected Environment, Disconnected Environment, and Air-Gapped Environment requirements.</todo>
-{{backlinks>.#dido:03-dido-te}}
+<todo>Determine whether MO-007a through MO-007c collectively supersede MO-007.</todo>
-===== Delivery Phase =====
+<todo>If MO-007a through MO-007c are accepted as the complete replacement for MO-007, mark MO-007 as superseded and preserve this page as the parent Traceability record.</todo>
-<todo>Assign the delivery phase for MO-007.</todo>
+----
-===== Implementation Status =====
+===== Issues =====
-<todo>Record the implementation status of MO-007 after reviewing the implementation plan.</todo>
+The following unresolved issues affect the decomposition of MO-007:
-===== Requirement Status =====
+<todo>Confirm the controlling source statement and citation for MO-007.</todo>
-<todo>The proposed derived requirement requires review and acceptance.</todo>
+<todo>Confirm the titles and scope of MO-007a, MO-007b, and MO-007c.</todo>
-===== Contents =====
+<todo>Identify the testing operations DIDO-TE performs in each environment type.</todo>
-{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007#1|js navbar nocookie maxjs#1 id#dido_te_mo_007_requirements_nav}}
+<todo>Determine which testing operations apply uniformly across Connected, Disconnected, and Air-Gapped Environments.</todo>
+<todo>Determine whether transfer operations require separate derived requirements beneath MO-007b and MO-007c.</todo>
+<todo>Determine whether MO-007a through MO-007c provide complete coverage of the approved intent of MO-007.</todo>
 ----
-===== Issues =====
+===== Notes for Editors =====
-<todo>Confirm the controlling source statement and citation from which MO-007 derives.</todo>
+This page should retain the stable parent requirement identifier ''MO-007''.
-<todo>Confirm the titles and scope of MO-007a, MO-007b, and MO-007c.</todo>
+This page is a non-leaf requirement page and retains a trailing '':start'' in its namespace.
-<todo>Determine whether transfer operations require separate derived requirements beneath MO-007b and MO-007c.</todo>
+The child requirements are leaf requirement pages and omit a trailing '':start'' from their namespaces.
-----
+This page preserves:
-===== Notes for Editors =====
+  * The Original Requirement
+  * The assessment of the Original Requirement
+  * The reason for decomposition
+  * Traceability to the proposed replacement requirements
+  * The unresolved cross-cutting issues affecting the decomposition
+  * The supersession decision
-MO-007 is a non-leaf requirement page. Its child requirements contain the separately verifiable normative obligations for each environment type.
+The proposed child requirements are:
-The explicit child links remain in the Derived From section to document the normative decomposition. The Contents section dynamically lists the child pages.
+  * ''MO-007a — Connected Environment Operation''
+  * ''MO-007b — Disconnected Environment Operation''
+  * ''MO-007c — Air-Gapped Environment Operation''
-The MO-007 namespace retains the trailing `:start`:
+The Original Requirement should not be marked as superseded until the requirement owner:
+  * Approves the three child requirements
+  * Confirms that the child requirements collectively preserve the complete approved intent of MO-007
+  * Confirms that each required testing operation has been allocated to one or more child requirements
+  * Confirms that no additional child requirements are required
+After supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment.
+Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records.
+The non-leaf page namespace is:
 <code>
 dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-007:start
 </code>
-The child requirement namespaces omit `:start`.
 ----