| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:start [2026/07/15 12:52] – nick_dido | dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:start [2026/07/22 09:57] (current) – nick_dido |
|---|
| ====== MO-002 ====== | ====== MO-002 — Reduced Platform Deployment Timelines ====== |
| |
| [[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:start|Go to Mission Objectives]] |
| |
| ===== Statement ===== | ===== Original Requirement ===== |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL achieve a [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] duration that is less than the approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]] and within the applicable acceptance criteria. | > //Crucible SHALL reduce platform deployment timelines from months to days or hours through automation.//[[dido:02-crusible:99-annexes:annex-b:cr-002|[C2]]] |
| |
| ===== Source Statement ===== | ===== Assessment of Original Requirement ===== |
| |
| > Crucible SHALL reduce platform deployment timelines from months to days or hours through automation. | The Original Requirement preserves the approved mission objective but does not express independently testable normative statements. |
| | |
| ===== Source ===== | |
| | |
| Crucible System Requirements Specification, Version 1.1 Draft, Mission Objectives, MO-002. | |
| | |
| ===== Assessment ===== | |
| | |
| The source statement expresses the approved mission objective but does not provide the information required for deterministic verification. | |
| |
| The following Specification Discipline and Authoring findings apply: | The following Specification Discipline and Authoring findings apply: |
| |
| * **Platform deployment timelines** does not identify the beginning and end of the measured activity | * **Reduce** requires comparison with an identified and approved baseline |
| * **From months** does not define the approved baseline duration, baseline process, environment, scope, or measurement method | * **Platform deployment timelines** does not identify the measured [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] activity |
| * **To days or hours** provides alternative and unbounded target ranges rather than a single applicable acceptance criterion | * **From months** does not identify a specific baseline duration |
| * **Through automation** prescribes an implementation approach rather than the required outcome | * **To days or hours** does not establish a single measurable duration threshold |
| * The source statement does not identify which [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] activities contribute to the measured duration | * **Through automation** prescribes an implementation approach rather than stating the required outcome |
| * The source statement does not identify whether image construction, compliance assessment, dependency capture, infrastructure deployment, provisioning, and post deployment validation occur within the measured duration | |
| |
| The normalized Statement expresses the required outcome as a measurable reduction relative to an approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]] and applicable acceptance criteria. | The Original Requirement combines: |
| |
| ===== Rationale ===== | * A maximum permitted [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] |
| | * A reduction relative to a deployment-duration baseline |
| | * Automation as an implementation approach |
| |
| Organizations often require weeks or months to construct, configure, secure, validate, and deploy a platform environment through manual or partially automated processes. | The maximum permitted duration and the reduction relative to a baseline can be evaluated independently. |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] reduces [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] duration by coordinating: | The Original Requirement does not identify: |
| |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Descriptions]] | * The Platform Deployment activity being measured |
| * Reusable [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] | * The start condition |
| * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] | * The completion condition |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layers]] | * The deployment-duration baseline |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] | * The target Deployment Duration |
| * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] construction | * The required amount of reduction |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] | * The measurement conditions |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:provisioning|Provisioning]] | * The treatment of failed, interrupted, incomplete, or repeated deployments |
| * Compliance assessment | |
| * Deployment validation | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] execution | |
| |
| Controlled execution replaces repeated manual activity and supports comparison against an approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]]. | The Original Requirement therefore requires: |
| |
| ===== Applies To ===== | * Identification of the measured Platform Deployment activity |
| | * Identification of the start and completion conditions |
| | * Establishment of a measurable target Deployment Duration |
| | * Establishment of an approved deployment-duration baseline |
| | * Establishment of the required reduction relative to that baseline |
| | * Separation of the absolute duration objective from the relative reduction objective |
| | * Determination of whether automation represents a required implementation constraint or only explanatory source language |
| | * Confirmation that the derived requirements collectively preserve the complete intent of MO-002 |
| |
| This requirement applies to: | The decomposition preserves ''MO-002'' as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page. |
| |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] | ===== Proposed Statements ===== |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Descriptions]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layers]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] construction | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:provisioning|Provisioning]] | |
| * Compliance assessment | |
| * Deployment validation | |
| * [[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: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:o:operational_lifecycle|Operational Lifecycle]] | |
| |
| ===== Verification ===== | The Original Requirement is decomposed into the following proposed replacement requirements: |
| |
| - Verification SHALL confirm that the approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]] identifies the baseline process, environment scope, starting event, ending event, and measured duration | {{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002#1|js navbar nocookie maxjs#1 id#crucible_mo_002_requirements_nav}} |
| - Verification SHALL confirm that the applicable acceptance criteria identify the maximum permitted [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] duration | |
| - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs the applicable [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] activities from controlled inputs | |
| - Verification SHALL confirm that the measured [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] duration is less than the approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]] | |
| - Verification SHALL confirm that the measured [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] duration satisfies the applicable acceptance criteria | |
| - Verification SHALL confirm that repeated tests use equivalent environment scope, controlled inputs, measurement boundaries, and acceptance criteria | |
| - Verification SHALL confirm that failed or incomplete deployments are excluded from successful deployment duration results and recorded separately | |
| |
| Verification may include: | ===== Requirement Status ===== |
| |
| * Baseline process timing | <todo>Review and approve the proposed decomposition of MO-002 into an absolute Platform Deployment Duration requirement and a relative Platform Deployment timeline-reduction requirement.</todo> |
| * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] timing | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] build timing | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] timing | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:provisioning|Provisioning]] timing | |
| * Compliance assessment timing | |
| * Deployment validation timing | |
| * End-to-end [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] timing | |
| * Connected environment demonstrations | |
| * Disconnected environment demonstrations | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]] demonstrations | |
| * Repeated deployment comparisons | |
| |
| The verification record SHALL identify: | <todo>Determine whether automation is a required implementation constraint, an architectural decision, or explanatory source language that should not appear in the derived requirements.</todo> |
| |
| - The approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]] | <todo>Determine whether MO-002a and MO-002b collectively supersede MO-002.</todo> |
| - The baseline measurement method | |
| - The baseline environment scope | |
| - The baseline starting event | |
| - The baseline ending event | |
| - The baseline duration | |
| - The applicable acceptance criteria | |
| - The controlled inputs | |
| - The measured [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] activities | |
| - The measured starting event | |
| - The measured ending event | |
| - The measured duration | |
| - The difference between the baseline duration and measured duration | |
| - The verification result | |
| - The supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | |
| |
| ===== Traceability ===== | <todo>If MO-002a and MO-002b are accepted as the complete replacement for MO-002, mark MO-002 as superseded and preserve this page as the parent Traceability record.</todo> |
| |
| This requirement supports: | ---- |
| | ===== Issues ===== |
| |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start|FR-CFG-001 through FR-CFG-005]] | The following unresolved issues affect the decomposition of MO-002: |
| * [[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:start|KVP-001 — Reduce environment deployment timelines]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:13-key-value-proposition-requirements:kvp-002:start|KVP-002 — Reduce infrastructure engineering effort]] | |
| |
| KVP identifies a Key Value Proposition requirement. | <todo>Identify the Platform Deployment activity measured by MO-002.</todo> |
| |
| This requirement also relates to: | <todo>Define the start condition and completion condition used to calculate Platform Deployment Duration.</todo> |
| |
| * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] | <todo>Define the maximum permitted Platform Deployment Duration represented by days or hours.</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:09-compliance-and-security:start|9. Compliance and Security]] | |
| * [[dido:02-crusible:10-reproducibility-provenance-and-traceability:start|10. Reproducibility, Provenance, and Traceability]] | |
| |
| ===== ConOps Relationship ===== | <todo>Identify the approved deployment-duration baseline represented by months.</todo> |
| |
| The Crucible Concept of Operations describes Phase 1 as a command-line utility invoked through [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] steps. | <todo>Define the required reduction relative to the approved deployment-duration baseline.</todo> |
| |
| The Phase 1 workflow: | <todo>Define how failed, interrupted, incomplete, or repeated Platform Deployments affect duration measurement.</todo> |
| |
| * Composes [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layers]] and [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] | <todo>Determine whether MO-002a and MO-002b provide complete coverage of the approved intent of MO-002.</todo> |
| * Builds and hardens [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] | |
| * Captures dependencies and [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_finding|Compliance Findings]] | |
| * Performs [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] | |
| * Performs [[dido:99_annexes:annex-b-terms-and-definitions:p:provisioning|Provisioning]] | |
| * Executes deployment validation | |
| * Produces supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | |
| |
| The coordinated workflow reduces manual handoffs and repeated engineering activity. The measured reduction depends on an approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]] and acceptance criteria for the applicable environment. | ---- |
| | ===== Notes for Editors ===== |
| |
| ===== Delivery Phase ===== | This page should retain the stable parent requirement identifier ''MO-002''. |
| |
| Phase 1 and subsequent phases | This page is a non-leaf requirement page and retains a trailing '':start'' in its namespace. |
| |
| ===== Implementation Status ===== | The child requirements are leaf requirement pages and omit a trailing '':start'' from their namespaces. |
| |
| Not Assessed | 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-002 namespace. |
| |
| Implementation status requires measurement against an approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]] and applicable acceptance criteria. | This page preserves: |
| |
| ===== Requirement Status ===== | * The Original Requirement |
| | * 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 |
| |
| Draft | The derived requirements should separate: |
| |
| The source System Requirements Specification identifies Version 1.1 as a draft. | * The maximum permitted Platform Deployment Duration |
| | * The required reduction relative to an approved deployment-duration baseline |
| |
| ---- | The phrase **through automation** should not be converted into a normative implementation constraint unless the requirement owner confirms that automation forms part of the approved requirement intent. |
| ===== Notes for Editors ===== | |
| |
| This requirement page should retain the stable requirement identifier `MO-002`. | The Original Requirement should not be marked as superseded until the requirement owner: |
| |
| Changes to the Statement SHALL preserve the approved intent of the source requirement. | * Approves the proposed decomposition |
| | * Approves the child requirements |
| | * Confirms the treatment of **through automation** |
| | * Confirms that the child requirements collectively preserve the complete approved intent of MO-002 |
| | * Confirms that no additional child requirements are required |
| |
| Material changes should receive review and should update the related Traceability, verification criteria, acceptance criteria, and source records. | After supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment. |
| |
| The Source Statement should preserve the original wording from the controlling System Requirements Specification. | Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records. |
| |
| ---- | ---- |