MO-002b — Platform Deployment Duration Reduction

Go to MO-002 — Reduced Platform Deployment Timelines

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

This requirement derives from:

• MO-002 — Reduced Platform Deployment Timelines

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:

• MO-002a — Maximum Platform Deployment Duration

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 Deployment Duration used for comparison.

Equivalent measurement conditions prevent differences in deployment scope, inputs, resources, environment, or measurement method from producing a misleading comparison.

Equivalent measurement conditions can include:

• 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 Platform Deployments

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

This requirement applies to:

• Crucible
• Platform Deployments
• Selected Platform Deployments
• Deployment Duration
• Deployment Baselines
• Equivalent measurement conditions
• Controlled Inputs
• Platform Deployment scope
• Platform Deployment starting events
• Platform Deployment completion events
• Platform Deployment measurement methods
• Failed Platform Deployments
• Incomplete Platform Deployments
• Interrupted Platform Deployments
• Repeated Platform Deployments
• Evidence
• Provenance
• Traceability

Verification confirms that:

1. The approved Deployment Baseline is uniquely identified
2. The Deployment Baseline identifies the baseline Platform Deployment
3. The Deployment Baseline records the baseline Deployment Duration
4. The selected Platform Deployment is identified
5. The baseline and selected Platform Deployments use equivalent measurement conditions
6. The baseline and selected Platform Deployments use equivalent deployment scopes
7. The baseline and selected Platform Deployments use equivalent Controlled Inputs
8. The baseline and selected Platform Deployments use equivalent starting and completion events
9. The baseline and selected Platform Deployments include equivalent measured activities
10. The baseline and selected Platform Deployments use equivalent measurement methods
11. The measured Deployment Duration is less than the Deployment Duration recorded by the approved Deployment Baseline
12. Failed, incomplete, interrupted, and repeated Platform Deployments receive equivalent treatment in the baseline and measured results
13. The verification record preserves Traceability among the approved Deployment Baseline, the selected Platform Deployment, the measured Deployment Duration, and the comparison result

The following pages reference this requirement:

Implemented and Verified

Compare the current Crucible Platform Deployment Duration with the approved Deployment Baseline under equivalent measurement conditions.

Review and accept MO-002b as a proposed derived requirement created from the evaluation and decomposition of MO-002 in the Crucible System Requirements Specification, Version 1.1 Draft.

The following unresolved issues affect this requirement:

Identify the approved Deployment Baseline and its controlling source.

Define the baseline Platform Deployment process, scope, Controlled Inputs, starting event, completion event, included activities, and Deployment Duration.

Define the measurement conditions that must remain equivalent between the baseline and selected Platform Deployments.

Define the required amount of Platform Deployment Duration reduction.

Define how failed, incomplete, interrupted, and repeated Platform Deployments affect the baseline and measured results.

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.

The parent MO-002 page is a non-leaf page and retains a trailing :start in its namespace.

Changes to the Statement should preserve:

• Crucible as the responsible actor
• The selected Platform Deployment as the measured activity
• The approved Deployment Baseline as the comparison point
• Equivalent measurement conditions for the baseline and selected Platform Deployments
• A measured Deployment Duration below the baseline Deployment Duration as the required outcome

The approved Deployment Baseline should identify:

• The Deployment Baseline identifier and 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 Platform Deployments

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:

{{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.