dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004a

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004a [2026/07/20 08:35] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004a [2026/07/30 05:23] (current) – [Delivery Phase] nick_dido
Line 1: Line 1:
-====== MO-004a — Connected Environment Operation ======+====== MO-004a — Connected Environment Operations ======
  
 [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:start|Go to MO-004 — Connected and Disconnected Operations]] [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:start|Go to MO-004 — Connected and Disconnected Operations]]
Line 21: Line 21:
 The separate requirements derived from MO-004 address: The separate requirements derived from MO-004 address:
  
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004b|MO-004b — Disconnected Environment Operation]] +  * [[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 — Unauthorized Resource Prohibition]] +  * [[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 — External Resource Independence]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-004:mo-004d|MO-004d — Disconnected Resource Availability]]
- +
-===== Assessment ===== +
- +
-The Original Requirement uses **support** without identifying the behavior [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs. +
- +
-The phrase **connected operational environments** does not identify: +
- +
-  * The Operational Lifecycle activities performed +
-  * The method used to select those activities +
-  * The inputs required by each activity +
-  * The outputs produced by each activity +
-  * The resources available to each activity +
-  * The completion conditions applicable to each activity +
-  * The Evidence required to demonstrate successful execution +
- +
-MO-004a: +
- +
-  * Replaces **support** with the direct action **execute** +
-  * Identifies Crucible as the responsible actor +
-  * Identifies the selected Operational Lifecycle activity as the required behavior +
-  * Identifies a Connected Environment as the applicable operational context +
-  * Separates Connected Environment operation from Disconnected Environment operation +
-  * Separates execution behavior from resource authorization and external-resource constraints+
  
 ===== Rationale ===== ===== Rationale =====
  
-A [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] provides access to authorized network services, repositories, registries, data sources, and other resources required by selected Operational Lifecycle activities.+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.
  
 Operational Lifecycle activities can include: Operational Lifecycle activities can include:
Line 68: Line 45:
   * Operational maintenance   * Operational maintenance
  
-The selected activities define the scope of the required execution. Selection prevents the requirement from implying that every Operational Lifecycle activity applies to every Connected Environment or every deployment scenario.+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.
  
-Execution in a Connected Environment supports:+Execution in a Connected Environment supports access to network services, repositories, registries, data sources, and other resources available within the environment.
  
-  * Retrieval of authorized dependencies +This requirement does not establish the requirements for execution in a Disconnected Environment. MO-004b addresses that outcome.
-  * Access to approved repositories and registries +
-  * Integration with authorized external services +
-  * Use of CI/CD Pipelines +
-  * Collection of Evidence +
-  * Preservation of Provenance +
-  * Maintenance of Traceability +
-  * Coordination across distributed resources+
  
-This requirement does not establish the requirements for execution in a Disconnected Environment. MO-004b establishes those requirements. +This requirement does not establish which resources Crucible is authorized to use. MO-004c addresses Authorized Resource use.
- +
-This requirement does not permit access to unauthorized resources. MO-004c establishes the applicable prohibition.+
  
 ===== Applies To ===== ===== Applies To =====
Line 92: Line 60:
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]]   * [[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]]   * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]]
-  * Operational Lifecycle activities+  * 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: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:authorized_resource|Authorized Resources]]
Line 113: Line 81:
 Verification confirms that: Verification confirms that:
  
-  - The Connected Environment is identified +  - The [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] is identified 
-  - The selected Operational Lifecycle activity is identified +  - Each selected [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activity is identified 
-  - The inputs required by the selected activity are identified +  - The inputs required by each selected activity are identified 
-  - The authorized resources used by the selected activity are identified +  - The resources used by each selected activity are identified 
-  - Crucible executes the selected activity within the Connected Environment +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] executes each selected activity within the Connected Environment 
-  - The selected activity reaches its defined completion condition +  - Each selected activity reaches its defined completion condition 
-  - The selected activity produces its required outputs +  - Each selected activity produces its required outputs 
-  - The execution record preserves the required Evidence, Provenance, and Traceability +  - 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
-Verification includes: +
- +
-  * Connected Environment inspection +
-  * Operational Lifecycle activity inspection +
-  * Controlled Input inspection +
-  * Authorized Resource inspection +
-  * Repository-access tests +
-  * Registry-access tests +
-  * Authorized network-service tests +
-  * CI/CD Pipeline tests +
-  * Operational Lifecycle execution tests +
-  * Completion-condition inspection +
-  * Output inspection +
-  * Evidence inspection +
-  * Provenance inspection +
-  * Traceability inspection +
- +
-The verification record identifies: +
- +
-  - The Connected Environment +
-  - The selected Operational Lifecycle activity +
-  - The applicable activity identifier and revision +
-  - The selected Controlled Inputs +
-  - The Authorized Resources used during execution +
-  - The applicable starting condition +
-  - The applicable completion condition +
-  - The execution result +
-  - The outputs produced +
-  - Each identified failure or exception +
-  - The observed result +
-  - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] +
- +
-===== Requirements Realized By ===== +
- +
-This requirement is realized by: +
- +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001|OR-001 — Operational Roles]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-002|OR-002 — Deployment Environments]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-004|OR-004 — Concurrent Environment Management]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-005|OR-005 — Distributed Environment Management]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start|FR-CFG-001 through FR-CFG-005]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:start|FR-IMG-001 through FR-IMG-006]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:start|FR-DEP-001 through FR-DEP-007]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:start|FR-COMP-001 through FR-COMP-010]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:start|FR-DSO-001 through FR-DSO-006]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:start|FR-BAS-001 through FR-BAS-004]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-10-dependency-capture-and-offline-transfer:start|FR-DEPC-001 through FR-DEPC-005]] +
- +
-===== Related Architecture Sections ===== +
- +
-  * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] +
-  * [[dido:02-crusible:06-machine-images-and-image-layers:start|6. Machine Images and Image Layers]] +
-  * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]] +
-  * [[dido:02-crusible:08-dependencies-and-air-gap-operations:start|8. Dependencies and Air Gap Operations]] +
-  * [[dido:02-crusible:09-compliance-and-security:start|9. Compliance and Security]] +
-  * [[dido:02-crusible:10-reproducibility-provenance-and-traceability:start|10. Reproducibility, Provenance, and Traceability]]+
  
 ===== Referenced By ===== ===== Referenced By =====
Line 187: Line 99:
 ===== Delivery Phase ===== ===== Delivery Phase =====
  
-Phase 1 and subsequent phases+Implemented and Verified
  
 ===== Implementation Status ===== ===== Implementation Status =====
  
-Not Assessed +<todo>Assess whether the current Crucible implementation executes each selected Operational Lifecycle activity in a Connected Environment.</todo>
- +
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation executes the selected Operational Lifecycle activity in a Connected Environment.+
  
 ===== Requirement Status ===== ===== Requirement Status =====
  
-Draft+<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> 
 + 
 +---- 
 +===== Issues ===== 
 + 
 +The following unresolved issues affect this requirement:
  
-This requirement derives from MO-004 in the Crucible System Requirements Specification, Version 1.1 Draft.+<todo>Identify the Operational Lifecycle activities that Crucible must execute within a Connected Environment.</todo> 
 + 
 +<todo>Identify the controlling source that selects the Operational Lifecycle activities for a Connected Environment.</todo> 
 + 
 +<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>
  
 ---- ----
Line 208: Line 129:
 This page is a leaf requirement page and omits a trailing '':start'' from its namespace. This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-Changes to the Statement SHALL preserve the Connected Environment operation intent derived from MO-004.+The parent MO-004 page is a non-leaf page and retains a trailing '':start'' in its namespace. 
 + 
 +Changes to the Statement should preserve:
  
-The selected Operational Lifecycle activity should identify:+  * [[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
  
-  * The activity identifier +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 activity revision +
-  * The applicable Connected Environment +
-  * The required Controlled Inputs +
-  * The Authorized Resources available to the activity +
-  * The starting condition +
-  * The completion condition +
-  * The required outputs +
-  * The applicable failure criteria +
-  * The required Evidence+
  
-Material changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.+Material changes should receive review and should update the verification criteria, source records, and Issues section.
  
 To reference this requirement Statement from another wiki page, insert: To reference this requirement Statement from another wiki page, insert:
  • dido/02-crusible/99-annexes/annex-c-requirements/01-mission-objectives/mo-004/mo-004a.1784561747.txt.gz
  • Last modified: 2026/07/20 08:35
  • by nick_dido