dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:mo-002b

This is an old revision of the document!


MO-002b — Platform Deployment Duration Reduction

Crucible SHALL complete the selected Platform Deployment in less time than the approved Deployment Baseline under equivalent measurement conditions.

This requirement derives from:

The Original Requirement states:

Crucible SHALL reduce platform deployment timelines from months to days or hours through automation.[C2]

MO-002b preserves the portion of the Original Requirement that requires a reduction in Platform Deployment duration.

The separate requirement derived from MO-002 addresses:

The Original Requirement uses reduce without identifying:

  • The approved Deployment Baseline
  • The baseline Platform Deployment process
  • The baseline Deployment Duration
  • The Platform Deployment selected for comparison
  • The activities included in each measurement
  • The starting event
  • The completion event
  • The Controlled Inputs
  • The operational context
  • The measurement method
  • The degree of required reduction
  • The treatment of failed, incomplete, interrupted, or repeated deployments

The phrase from months to days or hours does not establish a controlled comparison because it does not identify a specific baseline duration or a specific measured duration.

MO-002b:

  • Identifies the approved Deployment Baseline as the comparison point
  • Identifies the selected Platform Deployment as the measured activity
  • Requires the selected Platform Deployment to complete in less time than the approved Deployment Baseline
  • Requires equivalent measurement conditions for the baseline and measured Platform Deployments
  • Separates relative duration reduction from the maximum-duration obligation established by MO-002a
  • Removes through automation because the phrase prescribes an implementation approach rather than the required outcome

A claim that Crucible reduces Platform Deployment duration requires an approved and measurable comparison point.

The approved Deployment Baseline records the Platform Deployment process and duration used for comparison. The baseline and measured Platform Deployments require equivalent measurement conditions so that differences in scope, inputs, resources, environment, or measurement method do not produce a misleading duration comparison.

Equivalent measurement conditions include equivalent:

  • Platform Deployment scope
  • Controlled Inputs
  • Starting event
  • Completion event
  • Included activities
  • Operational context
  • Computing resources
  • Network conditions
  • Measurement method
  • Measurement precision
  • Treatment of failed, incomplete, interrupted, and repeated deployments

The measured Platform Deployment satisfies this requirement when its Deployment Duration is less than the duration recorded by the approved Deployment Baseline under the applicable equivalent measurement conditions.

This requirement establishes a relative improvement over an approved Deployment Baseline. It does not establish the maximum permitted Deployment Duration. MO-002a establishes the absolute duration limit.

Verification confirms that:

  1. The approved Deployment Baseline is uniquely identified
  2. The approved Deployment Baseline records the baseline Platform Deployment process
  3. The approved Deployment Baseline records the baseline Deployment Duration
  4. The baseline and measured Platform Deployments use equivalent measurement conditions
  5. The baseline and measured Platform Deployments use equivalent Platform Deployment scopes
  6. The baseline and measured Platform Deployments use equivalent Controlled Inputs
  7. The baseline and measured Platform Deployments use equivalent starting and completion events
  8. The baseline and measured Platform Deployments include equivalent activities
  9. The baseline and measured Platform Deployments use equivalent measurement methods
  10. The measured Deployment Duration is less than the Deployment Duration recorded by the approved Deployment Baseline
  11. Failed, incomplete, interrupted, and repeated deployments receive equivalent treatment in the baseline and measured results

Verification includes:

  • Deployment Baseline inspection
  • Baseline Platform Deployment process inspection
  • Baseline duration inspection
  • Platform Deployment scope comparison
  • Controlled Input comparison
  • Starting-event comparison
  • Completion-event comparison
  • Included-activity comparison
  • Operational-context comparison
  • Computing-resource comparison
  • Network-condition comparison
  • Measurement-method comparison
  • Measurement-precision comparison
  • Starting-time capture
  • Completion-time capture
  • Elapsed-time calculation
  • Duration comparison
  • Deployment-result inspection
  • Repeated Platform Deployment tests
  • Evidence inspection
  • Provenance inspection
  • Traceability inspection

The verification record identifies:

  1. The approved Deployment Baseline
  2. The Deployment Baseline identifier and revision
  3. The baseline Platform Deployment process
  4. The baseline Platform Deployment scope
  5. The baseline Controlled Inputs
  6. The baseline operational context
  7. The baseline starting event
  8. The baseline completion event
  9. The baseline activities included in the measurement
  10. The baseline measurement method
  11. The baseline Deployment Duration
  12. The measured Platform Deployment
  13. The measured Platform Deployment scope
  14. The measured Controlled Inputs
  15. The measured operational context
  16. The measured starting event
  17. The measured completion event
  18. The measured activities included in the measurement
  19. The measured measurement method
  20. The measured Deployment Duration
  21. The difference between the baseline and measured Deployment Durations
  22. The treatment of any failed, incomplete, interrupted, or repeated deployment
  23. The observed result
  24. The generated Evidence

Phase 1 and subsequent phases

Not Assessed

Implementation status requires comparison of the current Crucible Platform Deployment duration against the approved Deployment Baseline under equivalent measurement conditions.

Draft

This requirement derives from MO-002 in the Crucible System Requirements Specification, Version 1.1 Draft.


This requirement page should retain the stable requirement identifier MO-002b.

This page is a leaf requirement page and omits a trailing :start from its namespace.

Changes to the Statement SHALL preserve the Platform Deployment duration-reduction intent derived from MO-002.

The approved Deployment Baseline should identify:

  • The Deployment Baseline identifier
  • The Deployment Baseline revision
  • The baseline Platform Deployment process
  • The baseline Platform Deployment scope
  • The baseline Controlled Inputs
  • The baseline operational context
  • The baseline starting event
  • The baseline completion event
  • The activities included in the baseline measurement
  • The baseline measurement method
  • The baseline measurement precision
  • The baseline Deployment Duration
  • The treatment of failed, incomplete, interrupted, and repeated deployments
  • The supporting Evidence

Material changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:mo-002b#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.


© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

  • dido/02-crusible/99-annexes/annex-c-requirements/01-mission-objectives/mo-002/mo-002b.1784560592.txt.gz
  • Last modified: 2026/07/20 08:16
  • by nick_dido