MO-004 — Connected and Disconnected Operations

Go to Mission Objectives

Original Requirement

The system SHALL support both connected and disconnected operational environments.[C1]

Assessment of Original Requirement

The Original Requirement preserves the approved mission objective but does not express independently testable normative statements.

The following Specification Discipline and Authoring findings apply:

The system does not use the defined system name CrucibleSupport is a weak verb that does not identify an observable behavior performed by CrucibleOperational environments does not identify the Crucible activities performed within each environmentThe Original Requirement combines operation in Connected Environments and Disconnected Environments within one normative statementThe Original Requirement does not identify:

The Operational Lifecycle activities that Crucible performs within each environmentThe resources that Crucible may use within each environmentThe distinction between resource availability and resource authorizationWhether Crucible may depend on external network resources while operating in a Disconnected EnvironmentWhether resources imported through an approved transfer process become available within the Disconnected EnvironmentThe Original Requirement therefore requires:

Replacement of the system with the defined system name CrucibleReplacement of support with observable Crucible behaviorIdentification of the Operational Lifecycle activities performed within Connected EnvironmentsIdentification of the Operational Lifecycle activities performed within Disconnected EnvironmentsIdentification of the resources authorized for use within each environmentSeparation of Connected Environment operation from Disconnected Environment operationSeparation of resource authorization from resource availabilityConfirmation that the derived requirements collectively preserve the complete intent of MO-004The decomposition preserves MO-004 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-004:

Notes for Editors

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

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.

The explicit child-page links should remain while the proposed decomposition is being developed. After the child pages have been created and finalized, the explicit links may be removed because the indexmenu displays the child requirement pages contained within the MO-004 namespace.

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 derived requirements should distinguish:

Operation within a Connected EnvironmentOperation within a Disconnected EnvironmentAuthorization to use a resourceAvailability of a resource within an environmentAvailability of a resource does not establish authorization to use that resource.

Authorization to use a resource does not establish that the resource is available within a particular environment.

The Original Requirement should not be marked as superseded until the requirement owner:

Approves the proposed decompositionApproves the child requirementsIdentifies the Operational Lifecycle activities required within each environmentDefines the relationship between resource authorization and resource availabilityConfirms that the child requirements collectively preserve the complete approved intent of MO-004Confirms 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.

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