| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004a [2026/07/22 12:12] – nick_dido | dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004a [2026/07/30 05:23] (current) – [Delivery Phase] nick_dido |
|---|
| ====== MO-004 — Connected and Disconnected Operations ====== | ====== MO-004a — Connected Environment Operations ====== |
| |
| [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]] | [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:start|Go to MO-004 — Connected and Disconnected Operations]] |
| |
| ===== Original Requirement ===== | ===== Statement ===== |
| | |
| | [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL execute each selected [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activity in a [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]]. |
| | |
| | ===== Derived From ===== |
| | |
| | This requirement derives from: |
| | |
| | * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:start|MO-004 — Connected and Disconnected Operations]] |
| | |
| | The Original Requirement states: |
| |
| > //The system SHALL support both connected and disconnected operational environments.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] | > //The system SHALL support both connected and disconnected operational environments.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] |
| |
| ===== Assessment of Original Requirement ===== | MO-004a preserves the portion of the Original Requirement that requires [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] to operate within a [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]]. |
| |
| The Original Requirement preserves the approved mission objective but does not express independently testable normative statements. | The separate requirements derived from MO-004 address: |
| |
| The following Specification Discipline and Authoring findings apply: | * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004b|MO-004b — Disconnected Environment Operations]] |
| | * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004c|MO-004c — Authorized Resource Use]] |
| | * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004d|MO-004d — Disconnected Resource Availability]] |
| |
| * **The system** does not use the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] | ===== Rationale ===== |
| * **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 [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]] and [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]] within one normative statement | |
| |
| The Original Requirement does not identify: | A [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] provides network connectivity to resources required by selected Operational Lifecycle activities. |
| |
| * The [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activities that Crucible performs within each environment | Operational Lifecycle activities can include: |
| * 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: | * Artifact acquisition |
| | * Dependency resolution |
| | * Baseline composition |
| | * Machine Image construction |
| | * Infrastructure Deployment |
| | * Provisioning |
| | * Configuration |
| | * Compliance Assessment |
| | * Security assessment |
| | * Deployment Validation |
| | * Evidence generation |
| | * Artifact promotion |
| | * Operational maintenance |
| |
| * Replacement of **the system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] | The selected activities define the required scope of execution. Selection prevents this requirement from implying that every Operational Lifecycle activity applies to every Connected Environment or operational context. |
| * 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. | Execution in a Connected Environment supports access to network services, repositories, registries, data sources, and other resources available within the environment. |
| |
| ===== Proposed Statements ===== | This requirement does not establish the requirements for execution in a Disconnected Environment. MO-004b addresses that outcome. |
| |
| The Original Requirement is decomposed into the following proposed replacement requirements: | This requirement does not establish which resources Crucible is authorized to use. MO-004c addresses Authorized Resource use. |
| |
| {{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004#1|js navbar nocookie maxjs#1 id#crucible_mo_004_requirements_nav}} | ===== Applies To ===== |
| |
| ===== Requirement Status ===== | This requirement applies to: |
| |
| <todo>Review and approve the proposed decomposition of MO-004 into independently testable Connected Environment, Disconnected Environment, resource-authorization, and resource-availability requirements.</todo> | * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] |
| | * Selected Operational Lifecycle activities |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:a:authorized_resource|Authorized Resources]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] |
| | * Artifact repositories |
| | * Package repositories |
| | * Image registries |
| | * Authorized network services |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:p:provisioning|Provisioning]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_assessment|Compliance Assessments]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] |
| |
| <todo>Determine whether MO-004a through MO-004d collectively supersede MO-004.</todo> | ===== Verification ===== |
| |
| <todo>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.</todo> | Verification confirms that: |
| |
| ---- | - The [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] is identified |
| ===== Issues ===== | - Each selected [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activity is identified |
| | - The inputs required by each selected activity are identified |
| | - The resources used by each selected activity are identified |
| | - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] executes each selected activity within the Connected Environment |
| | - Each selected activity reaches its defined completion condition |
| | - Each selected activity produces its required outputs |
| | - Each failure or exception is identified |
| | - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Connected Environment, selected activity, Controlled Inputs, resources used, execution result, and outputs produced |
| |
| The following unresolved issues affect the decomposition of MO-004: | ===== Referenced By ===== |
| |
| <todo>Identify the Operational Lifecycle activities that Crucible must perform within a Connected Environment.</todo> | The following pages reference this requirement: |
| |
| <todo>Identify the Operational Lifecycle activities that Crucible must perform within a Disconnected Environment.</todo> | {{backlinks>.#dido:02-crusible}} |
| |
| <todo>Define how Operational Lifecycle activities are selected for each environment.</todo> | ===== Delivery Phase ===== |
| |
| <todo>Identify the Authorized Resources that Crucible may use within each environment.</todo> | Implemented and Verified |
| |
| <todo>Define the relationship between resource authorization and resource availability.</todo> | ===== Implementation Status ===== |
| |
| <todo>Define whether Crucible may depend on external network resources while operating within a Disconnected Environment.</todo> | <todo>Assess whether the current Crucible implementation executes each selected Operational Lifecycle activity in a Connected Environment.</todo> |
| |
| <todo>Define when resources imported through an approved transfer process become available for use within a Disconnected Environment.</todo> | ===== Requirement Status ===== |
| |
| <todo>Determine whether MO-004a through MO-004d provide complete coverage of the approved intent of MO-004.</todo> | <todo>Review and accept MO-004a as a proposed derived requirement created from the evaluation and decomposition of MO-004 in the Crucible System Requirements Specification, Version 1.1 Draft.</todo> |
| |
| ---- | ---- |
| ===== Notes for Editors ===== | ===== Issues ===== |
| |
| This page should retain the stable parent requirement identifier ''MO-004''. | The following unresolved issues affect this requirement: |
| |
| This page is a non-leaf requirement page and retains a trailing '':start'' in its namespace. | <todo>Identify the Operational Lifecycle activities that Crucible must execute within a Connected Environment.</todo> |
| |
| The child requirements are leaf requirement pages and omit a trailing '':start'' from their namespaces. | <todo>Identify the controlling source that selects the Operational Lifecycle activities for a Connected Environment.</todo> |
| |
| 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. | <todo>Define the starting condition, completion condition, required inputs, required outputs, and failure criteria for each selected Operational Lifecycle activity.</todo> |
| | |
| | <todo>Identify the resources available within each Connected Environment and distinguish available resources from Authorized Resources.</todo> |
| | |
| | ---- |
| | ===== Notes for Editors ===== |
| |
| This page preserves: | This requirement page should retain the stable requirement identifier ''MO-004a''. |
| |
| * The Original Requirement | This page is a leaf requirement page and omits a trailing '':start'' from its namespace. |
| * The assessment of the Original Requirement | |
| * The reason for decomposition | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] to the proposed replacement requirements | |
| * The unresolved cross-cutting issues affecting the decomposition | |
| * The supersession decision | |
| |
| The derived requirements should distinguish: | The parent MO-004 page is a non-leaf page and retains a trailing '':start'' in its namespace. |
| |
| * Operation within a Connected Environment | Changes to the Statement should preserve: |
| * 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. | * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor |
| | * The selected [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activity as the required behavior |
| | * The [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] as the operational context |
| | * Execution of each selected activity as the required outcome |
| |
| Authorization to use a resource does not establish that the resource is available within a particular environment. | The unresolved activity-selection source should remain recorded in the Issues section until a controlling source identifies the activities required within a Connected Environment. |
| |
| The Original Requirement should not be marked as superseded until the requirement owner: | Material changes should receive review and should update the verification criteria, source records, and Issues section. |
| |
| * Approves the proposed decomposition | To reference this requirement Statement from another wiki page, insert: |
| * 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. | <code dokuwiki> |
| | {{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004a#Statement&noheader&nofooter&noeditbtn}} |
| | </code> |
| |
| Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records. | Do not rename this page after an external citation unless a redirect or move plan is in place. |
| |
| ---- | ---- |