MO-004 — Connected and Disconnected Operations

Go to Mission Objectives

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

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 Crucible
• Support is a weak verb that does not identify the behavior Crucible performs
• Operational environments does not identify the activities Crucible performs, the inputs used, the outputs produced, or the required completion conditions
• The Original Requirement combines operation in Connected Environments and Disconnected Environments within one normative statement
• Connected Environment operation and Disconnected Environment operation can pass or fail independently
• The Original Requirement does not identify which Operational Lifecycle activities apply within each environment
• The Original Requirement does not identify how the applicable Operational Lifecycle activities are selected
• The Original Requirement does not distinguish resource availability from resource authorization
• The Original Requirement does not prohibit use of resources that are not authorized for the operational environment
• The Original Requirement does not prohibit dependence on external network resources unavailable within a Disconnected Environment
• The Original Requirement does not identify whether resources imported through an approved transfer process become available within the Disconnected Environment
• The Original Requirement does not provide independently identifiable statements for verification and traceability

The previously normalized Statement also combined:

• Execution in Connected Environments
• Execution in Disconnected Environments
• Use of only Authorized Resources
• Dependence on resources available within each environment

These obligations can pass or fail independently.

The Original Requirement therefore requires decomposition into independently identifiable normative requirements.

The decomposition preserves MO-004 as the stable parent requirement identifier. Each replacement requirement receives a lettered identifier and a separate requirement page.

The Original Requirement is replaced by the following independently identifiable normative requirements:

• MO-004a — Connected Environment Operation
• MO-004b — Disconnected Environment Operation
• MO-004c — Unauthorized Resource Prohibition
• MO-004d — External Resource Independence