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 an observable behavior performed by Crucible
• Operational environments does not identify the Crucible activities performed within each environment
• The Original Requirement combines operation in Connected Environments and Disconnected Environments within one normative statement

The Original Requirement does not identify:

• The Operational Lifecycle activities that Crucible performs within each environment
• The resources that Crucible may use within each environment
• The distinction between resource availability and resource authorization
• Whether Crucible may depend on external network resources while operating in a Disconnected Environment
• Whether resources imported through an approved transfer process become available within the Disconnected Environment

The Original Requirement therefore requires:

• Replacement of the system with the defined system name Crucible
• Replacement of support with observable Crucible behavior
• Identification of the Operational Lifecycle activities performed within Connected Environments
• Identification of the Operational Lifecycle activities performed within Disconnected Environments
• Identification of the resources authorized for use within each environment
• Separation of Connected Environment operation from Disconnected Environment operation
• Separation of resource authorization from resource availability
• Confirmation that the derived requirements collectively preserve the complete intent of MO-004

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

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

Review and approve the proposed decomposition of MO-004 into independently testable Connected Environment, Disconnected Environment, resource-authorization, and resource-availability requirements.

Determine whether MO-004a through MO-004d collectively supersede MO-004.

If MO-004a through MO-004d are accepted as the complete replacement for MO-004, mark MO-004 as superseded and preserve this page as the parent Traceability record.

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

Identify the Operational Lifecycle activities that Crucible must perform within a Connected Environment.

Identify the Operational Lifecycle activities that Crucible must perform within a Disconnected Environment.

Define how Operational Lifecycle activities are selected for each environment.

Identify the Authorized Resources that Crucible may use within each environment.

Define the relationship between resource authorization and resource availability.

Define whether Crucible may depend on external network resources while operating within a Disconnected Environment.

Define when resources imported through an approved transfer process become available for use within a Disconnected Environment.

Determine whether MO-004a through MO-004d provide complete coverage of the approved intent of MO-004.

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 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

The derived requirements should distinguish:

• Operation within a Connected Environment
• Operation within a Disconnected Environment
• Authorization to use a resource
• Availability of a resource within an environment

Availability 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 decomposition
• Approves the child requirements
• Identifies the Operational Lifecycle activities required within each environment
• Defines the relationship between resource authorization and resource availability
• Confirms that the child requirements collectively preserve the complete approved intent of MO-004
• 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.