| Next revision | Previous revision |
| dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:mo-002a [2026/07/20 08:06] – created nick_dido | dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:mo-002a [2026/07/30 05:21] (current) – [Delivery Phase] nick_dido |
|---|
| ===== Statement ===== | ===== Statement ===== |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL complete the selected [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] within the maximum [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] specified by the applicable [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]. | [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL complete the selected [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] within the maximum [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] established by the [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]. |
| |
| ===== Derived From ===== | ===== Derived From ===== |
| > //Crucible SHALL reduce platform deployment timelines from months to days or hours through automation.//[[dido:02-crusible:99-annexes:annex-b:cr-002|[C2]]] | > //Crucible SHALL reduce platform deployment timelines from months to days or hours through automation.//[[dido:02-crusible:99-annexes:annex-b:cr-002|[C2]]] |
| |
| MO-002a preserves the portion of the Original Requirement that establishes a target duration for completing a Platform Deployment. | MO-002a preserves the portion of the Original Requirement that establishes a maximum duration for completing a Platform Deployment. |
| |
| The separate requirement derived from MO-002 addresses: | The separate requirement derived from MO-002 addresses: |
| |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:mo-002b|MO-002b — Platform Deployment Duration Reduction]] | * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:mo-002b|MO-002b — Platform Deployment Timeline Reduction]] |
| | |
| ===== Assessment ===== | |
| | |
| The Original Requirement uses **from months to days or hours** without identifying: | |
| | |
| * The maximum permitted Deployment Duration | |
| * The applicable Platform Deployment | |
| * The starting event | |
| * The completion event | |
| * The activities included in the measured duration | |
| * The applicable operational context | |
| * The measurement method | |
| * The treatment of failed, incomplete, interrupted, or repeated deployments | |
| * The Acceptance Criteria used to determine whether the measured duration is acceptable | |
| | |
| The terms **days or hours** provide alternative and unbounded target ranges rather than a measurable performance threshold. | |
| | |
| MO-002a: | |
| | |
| * Replaces **days or hours** with a maximum Deployment Duration | |
| * Identifies [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor | |
| * Identifies the selected [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] as the measured activity | |
| * Requires the applicable [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] to specify the maximum permitted Deployment Duration | |
| * Separates the maximum-duration obligation from comparison against an approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]] | |
| * Removes **through automation** because the phrase prescribes an implementation approach rather than the required outcome | |
| |
| ===== Rationale ===== | ===== Rationale ===== |
| Organizations require predictable Platform Deployment timelines to support development, integration, testing, evaluation, release, recovery, and operational planning. | Organizations require predictable Platform Deployment timelines to support development, integration, testing, evaluation, release, recovery, and operational planning. |
| |
| A qualitative or unbounded target such as **days or hours** does not establish an objectively verifiable performance obligation. A maximum Deployment Duration provides a measurable limit based on defined measurement boundaries. | The phrase **days or hours** does not establish an objectively verifiable performance obligation. A maximum [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] provides a measurable limit based on defined measurement boundaries. |
| |
| The applicable Acceptance Criteria establish: | The [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] establish: |
| |
| * The selected Platform Deployment | * The selected [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] |
| * The operational context | * The activities included in the measurement |
| * The activities included in the measured deployment | |
| * The starting event | * The starting event |
| * The completion event | * The completion event |
| * The maximum permitted Deployment Duration | * The maximum permitted Deployment Duration |
| * The measurement method | * The measurement conditions |
| * The required measurement precision | |
| * The treatment of failed, incomplete, interrupted, or repeated deployments | * The treatment of failed, incomplete, interrupted, or repeated deployments |
| |
| Different Acceptance Criteria can apply to different: | Separating the maximum duration requirement from the relative duration-reduction requirement permits Crucible to satisfy one requirement while independently passing or failing the other. |
| | |
| * Platform types | |
| * Deployment scopes | |
| * Infrastructure sizes | |
| * Computing resources | |
| * Network conditions | |
| * Connected Environments | |
| * Disconnected Environments | |
| * Air-Gapped Environments | |
| * Initial deployments | |
| * Repeated deployments | |
| * Recovery deployments | |
| |
| This requirement establishes an absolute maximum Deployment Duration. It does not require the measured duration to improve upon an approved Deployment Baseline. MO-002b establishes the relative duration-reduction requirement. | This requirement does not require the measured Deployment Duration to improve upon an approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]]. MO-002b addresses that outcome. |
| |
| ===== Applies To ===== | ===== Applies To ===== |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] | * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployments]] | * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployments]] |
| | * Selected Platform Deployments |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] | * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] | * [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]] | * Platform Deployment activities included in the measurement |
| * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] | * Platform Deployment starting events |
| * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] construction | * Platform Deployment completion events |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] | * Failed Platform Deployments |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:provisioning|Provisioning]] | * Incomplete Platform Deployments |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_assessment|Compliance Assessment]] | * Interrupted Platform Deployments |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]] | * Repeated Platform Deployments |
| * [[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:d:disconnected_environment|Disconnected Environments]] | * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]] | * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | * [[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:p:provenance|Provenance]] |
| Verification confirms that: | Verification confirms that: |
| |
| - The applicable Acceptance Criteria identify the selected Platform Deployment | - The selected [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] is identified |
| - The applicable Acceptance Criteria identify the Platform Deployment activities included in the measurement | - The [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] identify the Platform Deployment activities included in the measurement |
| - The applicable Acceptance Criteria identify a defined starting event | - The Acceptance Criteria identify the starting event |
| - The applicable Acceptance Criteria identify a defined completion event | - The Acceptance Criteria identify the completion event |
| - The applicable Acceptance Criteria specify the maximum permitted Deployment Duration | - The Acceptance Criteria establish the maximum permitted [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] |
| - The measured Deployment Duration begins when the defined starting event occurs | - Measurement begins when the defined starting event occurs |
| - The measured Deployment Duration ends when the defined completion event occurs | - Measurement ends when the defined completion event occurs |
| - The selected Platform Deployment reaches the state required by the defined completion event | - The selected Platform Deployment reaches the state required by the completion event |
| - The measured Deployment Duration does not exceed the maximum permitted Deployment Duration | - The measured Deployment Duration does not exceed the maximum Deployment Duration established by the Acceptance Criteria |
| - Failed, incomplete, interrupted, and repeated deployments receive the treatment specified by the applicable Acceptance Criteria | - Failed, incomplete, interrupted, and repeated Platform Deployments receive the treatment established by the Acceptance Criteria |
| | - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Acceptance Criteria, the selected Platform Deployment, the measured Deployment Duration, and the verification result |
| |
| Verification includes: | ===== Referenced By ===== |
| |
| * Acceptance Criteria inspection | The following pages reference this requirement: |
| * Platform Deployment scope inspection | |
| * Controlled Input inspection | |
| * Deployment-event inspection | |
| * Starting-time capture | |
| * Completion-time capture | |
| * Elapsed-time calculation | |
| * Platform state inspection | |
| * Deployment-result inspection | |
| * Repeated Platform Deployment tests | |
| * Connected Environment tests | |
| * Disconnected Environment tests | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]] tests | |
| * End-to-end [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] tests | |
| |
| The verification record identifies: | {{backlinks>.#dido:02-crusible}} |
| |
| - The applicable Acceptance Criteria | ===== Delivery Phase ===== |
| - The selected Platform Deployment | |
| - The operational context | |
| - The Platform Deployment activities included in the measurement | |
| - The selected Controlled Inputs | |
| - The defined starting event | |
| - The defined completion event | |
| - The recorded starting time | |
| - The recorded completion time | |
| - The measured Deployment Duration | |
| - The maximum permitted Deployment Duration | |
| - The treatment of any failed, incomplete, interrupted, or repeated deployment | |
| - The observed result | |
| - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | |
| |
| ===== Requirements Realized By ===== | Implemented and Verified |
| |
| This requirement is realized by: | ===== Implementation Status ===== |
| |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001|OR-001 — Operational Roles]] | <todo>Measure the current Crucible implementation against the maximum Platform Deployment Duration established by the Acceptance Criteria.</todo> |
| * [[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:08-performance-requirements:start|PERF-001 through PERF-005]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:13-key-value-proposition-requirements:kvp-001|KVP-001 — Reduce Environment Deployment Timelines]] | |
| |
| ===== Related Architecture Sections ===== | ===== Requirement Status ===== |
| |
| * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] | <todo>Review and accept MO-002a as a proposed derived requirement created from the evaluation and decomposition of MO-002 in the Crucible System Requirements Specification, Version 1.1 Draft.</todo> |
| * [[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 ===== | ---- |
| | ===== Issues ===== |
| |
| The following pages reference this requirement: | The following unresolved issues affect this requirement: |
| |
| {{backlinks>.#dido:02-crusible}} | <todo>Identify the Platform Deployment activities included in the Deployment Duration measurement.</todo> |
| |
| ===== Delivery Phase ===== | <todo>Define the starting event and completion event used to calculate Platform Deployment Duration.</todo> |
| |
| Phase 1 and subsequent phases | <todo>Define the maximum permitted Platform Deployment Duration and identify the controlling Acceptance Criteria.</todo> |
| |
| ===== Implementation Status ===== | <todo>Define the measurement conditions, precision, exclusions, and tolerances used to evaluate Platform Deployment Duration.</todo> |
| |
| Not Assessed | <todo>Define how failed, incomplete, interrupted, and repeated Platform Deployments affect the measured Deployment Duration.</todo> |
| | |
| Implementation status requires measurement of the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation against the maximum Deployment Duration specified by the applicable Acceptance Criteria. | |
| | |
| ===== Requirement Status ===== | |
| | |
| Draft | |
| | |
| This requirement derives from MO-002 in the Crucible System Requirements Specification, Version 1.1 Draft. | |
| |
| ---- | ---- |
| 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 maximum Platform Deployment duration intent derived from MO-002. | The parent MO-002 page is a non-leaf page and retains a trailing '':start'' in its namespace. |
| | |
| | Changes to the Statement should preserve: |
| | |
| | * [[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:p:platform_deployment|Platform Deployment]] as the measured activity |
| | * The maximum [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] as the performance constraint |
| | * The [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] as the source of the duration constraint |
| |
| The applicable Acceptance Criteria should identify: | The Acceptance Criteria should identify: |
| |
| * The selected Platform Deployment | * The selected Platform Deployment |
| * The operational context | |
| * The activities included in the measurement | * The activities included in the measurement |
| * The starting event | * The starting event |
| * The completion event | * The completion event |
| * The maximum permitted Deployment Duration | * The maximum permitted Deployment Duration |
| * The measurement method | * The measurement conditions |
| * The required measurement precision | * The required measurement precision |
| * The treatment of failed, incomplete, interrupted, and repeated deployments | * Any permitted exclusions or tolerances |
| * The required Evidence | * The treatment of failed, incomplete, interrupted, and repeated Platform Deployments |
| |
| 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: |