MO-006a — Operational Lifecycle Association

Go to MO-006 — Infrastructure Lifecycle Management

Crucible SHALL associate each Infrastructure Environment with an identified revision of an Operational Lifecycle.

This requirement derives from:

• MO-006 — Infrastructure Lifecycle Management

The Original Requirement states:

The system SHALL support infrastructure lifecycle management from initial deployment through retirement.[C1]

MO-006a preserves the lifecycle-management intent of the Original Requirement by requiring each Infrastructure Environment to have an identified Operational Lifecycle revision.

The separate requirements derived from MO-006 address:

• MO-006b — Infrastructure Lifecycle Initiation
• MO-006c — Infrastructure Lifecycle State Recording
• MO-006d — Infrastructure Lifecycle Transition Execution
• MO-006e — Infrastructure Environment Retirement

An identified revision of an Operational Lifecycle defines the lifecycle framework governing an Infrastructure Environment.

The Operational Lifecycle revision provides the basis for determining:

• The lifecycle states that apply to the Infrastructure Environment
• The permitted transitions between lifecycle states
• The conditions governing each transition
• The activities allocated to Crucible
• The activities allocated to external actors or systems
• The initial lifecycle state
• The terminal lifecycle state
• The approval and control points
• The records required for lifecycle activities

Different Infrastructure Environments may require different Operational Lifecycle revisions because of differences in:

• Mission purpose
• Operational environment
• Security classification
• Compliance obligations
• Deployment Platform
• Infrastructure Baseline
• Organizational policy
• Operational authority
• Maintenance model
• Retirement and disposition requirements

Identifying the Operational Lifecycle revision supports:

• Consistent lifecycle execution
• Determination of the current lifecycle state
• Controlled lifecycle transitions
• Lifecycle-specific verification
• Reproducibility of lifecycle actions
• Preservation of Provenance
• Maintenance of Traceability

This requirement establishes the association between an Infrastructure Environment and an Operational Lifecycle revision.

This requirement does not initiate the associated Operational Lifecycle. MO-006b addresses lifecycle initiation.

This requirement does not record the current lifecycle state. MO-006c addresses lifecycle-state recording.

This requirement does not execute lifecycle transitions. MO-006d addresses transition execution.

This requirement does not retire the Infrastructure Environment. MO-006e addresses Retirement.

This requirement applies to:

• Crucible
• Infrastructure Environments
• Operational Lifecycles
• Operational Lifecycle identifiers
• Operational Lifecycle revisions
• Lifecycle-association records
• Lifecycle states
• Lifecycle transitions
• Transition conditions
• Operational environments
• Deployment Platforms
• Infrastructure Baselines
• Security profiles
• Compliance profiles
• Organizational policies
• Operational authorities
• Evidence
• Provenance
• Traceability

Verification confirms that:

1. Each Infrastructure Environment is identified
2. An Operational Lifecycle is associated with each Infrastructure Environment
3. The associated Operational Lifecycle has an identifier
4. The associated Operational Lifecycle revision is identified
5. The lifecycle association applies to the identified Infrastructure Environment
6. The lifecycle association distinguishes the governing Operational Lifecycle revision from other available revisions
7. The verification record preserves Traceability among the Infrastructure Environment, Operational Lifecycle identifier, Operational Lifecycle revision, association authority, and association record

The following pages reference this requirement:

Implemented and Verified.

Assess whether the current Crucible implementation associates each Infrastructure Environment with an identified Operational Lifecycle revision.

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

The following unresolved issues affect this requirement:

Identify the Operational Lifecycles that may govern an Infrastructure Environment.

Define the identifier and revision scheme used for Operational Lifecycles.

Identify the authority or process responsible for associating an Operational Lifecycle revision with an Infrastructure Environment.

Define when the Operational Lifecycle association becomes effective.

Define the behavior required when more than one Operational Lifecycle revision appears to govern the same Infrastructure Environment.

Define the behavior required when an associated Operational Lifecycle revision is superseded or withdrawn.

This requirement page should retain the stable requirement identifier MO-006a.

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

The parent MO-006 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
• Each Infrastructure Environment as the lifecycle subject
• An identified Operational Lifecycle revision as the governing lifecycle model
• The association between the Infrastructure Environment and the Operational Lifecycle revision

The lifecycle-association record should identify:

• The Infrastructure Environment identifier
• The Operational Lifecycle identifier
• The Operational Lifecycle revision
• The effective association condition
• The association date and time
• The authority or process responsible for the association
• The operational environment
• The Deployment Platform
• The security and compliance constraints
• The associated Provenance
• The associated Traceability

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-006:mo-006a#Statement&noheader&nofooter&noeditbtn}}

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