MO-007 — Connected, Disconnected, and Air-Gapped Operation

Go to Mission Objectives

Original Requirement

DIDO-TE SHALL support testing operations in Connected Environments, Disconnected Environments, and Air-Gapped Environments.

Assessment of Original Requirement

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.

The following Specification Discipline and Authoring findings apply:

Support is a weak verb that does not identify an observable DIDO-TE behaviorTesting operations does not identify the operations DIDO-TE performs within each environment typeThe requirement combines operation in Connected Environments, Disconnected Environments, and Air-Gapped EnvironmentsThe requirement does not identify the distinct connectivity, isolation, transfer, execution, and Evidence obligations associated with each environment typeA single verification result could obscure failure to operate in one or more required environment typesThe Original Requirement identifies:

The decomposition treats operation in each environment type as a separate obligation so that DIDO-TE behavior can be specified and verified independently.

The three environment types impose different constraints upon:

Access to external networks and servicesIntroduction of testing artifacts and dependenciesTransfer of Transfer BundlesConfiguration and execution of testsCollection and removal of Test ResultsCollection and preservation of logs and EvidenceIntegrity, provenance, and TraceabilityApplication of security and authorization controlsThe Original Requirement does not identify which testing operations apply to all three environment types or which environment-specific operations require separate treatment.

The Original Requirement therefore requires:

Replacement of support with observable DIDO-TE behaviorsIdentification of the testing operations required within each environment typeSeparation of the three independently testable environment obligationsIdentification of the transfer controls applicable to Disconnected and Air-Gapped EnvironmentsIdentification of the connectivity and external-service dependencies permitted within each environment typeConfirmation that the derived requirements collectively preserve the complete intent of MO-007The decomposition preserves MO-007 as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.

Proposed Statements

The Original Requirement is decomposed into the following proposed replacement requirements:

Requirement Status

Issues

The following unresolved issues affect the decomposition of MO-007:

Notes for Editors

This page should retain the stable parent requirement identifier MO-007.

This page is a non-leaf requirement page and retains a trailing :start in its namespace.

The child requirements are leaf requirement pages and omit a trailing :start from their namespaces.

This page preserves:

The Original RequirementThe assessment of the Original RequirementThe reason for decompositionTraceability to the proposed replacement requirementsThe unresolved cross-cutting issues affecting the decompositionThe supersession decisionThe proposed child requirements are:

MO-007a — Connected Environment OperationMO-007b — Disconnected Environment OperationMO-007c — Air-Gapped Environment OperationThe Original Requirement should not be marked as superseded until the requirement owner:

Approves the three child requirementsConfirms that the child requirements collectively preserve the complete approved intent of MO-007Confirms that each required testing operation has been allocated to one or more child requirementsConfirms that no additional child requirements are requiredAfter 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:

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

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.