dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006a

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006a [2026/07/20 09:00] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006a [2026/07/30 05:28] (current) – [Delivery Phase] nick_dido
Line 1: Line 1:
-====== MO-006a — Operational Lifecycle Assignment ======+====== MO-006a — Operational Lifecycle Association ======
  
 [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start|Go to MO-006 — Infrastructure Lifecycle Management]] [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start|Go to MO-006 — Infrastructure Lifecycle Management]]
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL associate each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] with an identified [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]].+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL associate each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] with an identified revision of an [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]].
  
 ===== Derived From ===== ===== Derived From =====
Line 17: Line 17:
 > //The system SHALL support infrastructure lifecycle management from initial deployment through retirement.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] > //The system SHALL support infrastructure lifecycle management from initial deployment through retirement.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-MO-006a preserves the lifecycle-management intent of the Original Requirement by requiring each Infrastructure Environment to have an identified Operational Lifecycle.+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: The separate requirements derived from MO-006 address:
  
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006b|MO-006b — Operational Lifecycle Initiation]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006b|MO-006b — Infrastructure Lifecycle Initiation]] 
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006c|MO-006c — Current Lifecycle State Determination]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006c|MO-006c — Infrastructure Lifecycle State Recording]] 
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006d|MO-006d — Lifecycle Transition Execution]]+  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006d|MO-006d — Infrastructure Lifecycle Transition Execution]]
   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006e|MO-006e — Infrastructure Environment Retirement]]   * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006e|MO-006e — Infrastructure Environment Retirement]]
- 
-===== Assessment ===== 
- 
-The Original Requirement refers to infrastructure lifecycle management but does not require an explicit relationship between an Infrastructure Environment and the Operational Lifecycle governing that environment. 
- 
-Without an identified Operational Lifecycle, an evaluator cannot reliably determine: 
- 
-  * Which lifecycle applies to the Infrastructure Environment 
-  * Which lifecycle states apply 
-  * Which lifecycle transitions apply 
-  * Which lifecycle revision governs the environment 
-  * Which transition conditions apply 
-  * Which Retirement conditions apply 
-  * Whether the lifecycle differs from the lifecycle assigned to another Infrastructure Environment 
- 
-The phrase **infrastructure lifecycle management** does not identify: 
- 
-  * The Infrastructure Environment governed by the lifecycle 
-  * The Operational Lifecycle assigned to the environment 
-  * The identifier of the assigned lifecycle 
-  * The revision of the assigned lifecycle 
-  * The scope of the lifecycle assignment 
-  * The Evidence required to demonstrate the assignment 
- 
-MO-006a: 
- 
-  * Identifies [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor 
-  * Identifies each Infrastructure Environment as the subject of the assignment 
-  * Identifies an Operational Lifecycle as the assigned lifecycle 
-  * Requires the Operational Lifecycle to be identified 
-  * Separates lifecycle assignment from lifecycle initiation, state determination, transition execution, and Retirement 
  
 ===== Rationale ===== ===== Rationale =====
  
-An identified Operational Lifecycle defines the lifecycle framework applicable to an Infrastructure Environment.+An identified revision of an [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] defines the lifecycle framework governing an Infrastructure Environment.
  
-The lifecycle assignment provides the basis for determining:+The Operational Lifecycle revision provides the basis for determining:
  
-  * The lifecycle states applicable to the Infrastructure Environment+  * The lifecycle states that apply to the Infrastructure Environment
   * The permitted transitions between lifecycle states   * The permitted transitions between lifecycle states
-  * The conditions applicable to each transition+  * The conditions governing each transition
   * The activities allocated to Crucible   * The activities allocated to Crucible
   * The activities allocated to external actors or systems   * The activities allocated to external actors or systems
-  * The initial lifecycle stage +  * The initial lifecycle state 
-  * The terminal lifecycle stage +  * The terminal lifecycle state 
-  * The applicable approval and control points +  * The approval and control points 
-  * The Evidence associated with lifecycle activities+  * The records required for lifecycle activities
  
-Different Infrastructure Environments can require different Operational Lifecycles because of differences in:+Different Infrastructure Environments may require different Operational Lifecycle revisions because of differences in:
  
   * Mission purpose   * Mission purpose
Line 86: Line 55:
   * Retirement and disposition requirements   * Retirement and disposition requirements
  
-Identifying the Operational Lifecycle supports:+Identifying the Operational Lifecycle revision supports:
  
   * Consistent lifecycle execution   * Consistent lifecycle execution
Line 95: Line 64:
   * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]   * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
   * Maintenance of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]   * Maintenance of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * Generation of auditable [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] 
  
-This requirement establishes the association between an Infrastructure Environment and an Operational Lifecycle.+This requirement establishes the association between an Infrastructure Environment and an Operational Lifecycle revision.
  
-This requirement does not initiate the assigned Operational Lifecycle. MO-006b establishes lifecycle initiation.+This requirement does not initiate the associated Operational Lifecycle. MO-006b addresses lifecycle initiation.
  
-This requirement does not determine the current lifecycle state. MO-006c establishes current lifecycle state determination.+This requirement does not record the current lifecycle state. MO-006c addresses lifecycle-state recording.
  
-This requirement does not execute lifecycle transitions. MO-006d establishes lifecycle transition execution.+This requirement does not execute lifecycle transitions. MO-006d addresses transition execution.
  
-This requirement does not transition the Infrastructure Environment to Retirement. MO-006e establishes Infrastructure Environment Retirement.+This requirement does not retire the Infrastructure Environment. MO-006e addresses Retirement.
  
 ===== Applies To ===== ===== Applies To =====
Line 116: Line 84:
   * Operational Lifecycle identifiers   * Operational Lifecycle identifiers
   * Operational Lifecycle revisions   * Operational Lifecycle revisions
-  * Lifecycle-assignment records+  * Lifecycle-association records
   * Lifecycle states   * Lifecycle states
   * Lifecycle transitions   * Lifecycle transitions
Line 135: Line 103:
 Verification confirms that: Verification confirms that:
  
-  - The Infrastructure Environment is identified +  - Each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] is identified 
-  - An Operational Lifecycle is associated with the Infrastructure Environment+  - An [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] is associated with each Infrastructure Environment
   - The associated Operational Lifecycle has an identifier   - The associated Operational Lifecycle has an identifier
-  - The associated Operational Lifecycle revision is identifiable +  - The associated Operational Lifecycle revision is identified 
-  - The lifecycle assignment applies to the identified Infrastructure Environment +  - The lifecycle association applies to the identified Infrastructure Environment 
-  - The lifecycle assignment distinguishes the applicable Operational Lifecycle from other available lifecycles +  - The lifecycle association distinguishes the governing Operational Lifecycle revision from other available revisions 
-  - The assignment record preserves the required Evidence, Provenance, and Traceability+  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Infrastructure Environment, Operational Lifecycle identifier, Operational Lifecycle revision, association authority, and association record
  
-Verification includes:+===== Referenced By =====
  
-  * Infrastructure Environment inspection +The following pages reference this requirement:
-  * Operational Lifecycle inspection +
-  * Operational Lifecycle identifier inspection +
-  * Operational Lifecycle revision inspection +
-  * Lifecycle-assignment record inspection +
-  * Cross-environment lifecycle-assignment comparison +
-  * Lifecycle applicability inspection +
-  * Evidence inspection +
-  * Provenance inspection +
-  * Traceability inspection+
  
-The verification record identifies:+{{backlinks>.#dido:02-crusible}}
  
-  - The Infrastructure Environment +===== Delivery Phase =====
-  - The assigned Operational Lifecycle +
-  - The Operational Lifecycle identifier +
-  - The Operational Lifecycle revision +
-  - The lifecycle-assignment record +
-  - The effective assignment condition +
-  - The authority or process responsible for the assignment +
-  - Each conflicting or missing lifecycle assignment +
-  - Each identified failure or exception +
-  - 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>Assess whether the current Crucible implementation associates each Infrastructure Environment with an identified Operational Lifecycle revision.</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-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-03-deployment-orchestration:start|FR-DEP-001 through FR-DEP-007]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-metadata-catalog-and-provenance:start|FR-MC-001 through FR-MC-005]] +
-  * [[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]]+
  
-===== Related Architecture Sections =====+===== Requirement Status =====
  
-  * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] +<todo>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.</todo>
-  * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]] +
-  * [[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 Operational Lifecycles that may govern an Infrastructure Environment.</todo>
  
-===== Delivery Phase =====+<todo>Define the identifier and revision scheme used for Operational Lifecycles.</todo>
  
-Phase 1 and subsequent phases+<todo>Identify the authority or process responsible for associating an Operational Lifecycle revision with an Infrastructure Environment.</todo>
  
-===== Implementation Status =====+<todo>Define when the Operational Lifecycle association becomes effective.</todo>
  
-Not Assessed+<todo>Define the behavior required when more than one Operational Lifecycle revision appears to govern the same Infrastructure Environment.</todo>
  
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation associates each Infrastructure Environment with an identified Operational Lifecycle. +<todo>Define the behavior required when an associated Operational Lifecycle revision is superseded or withdrawn.</todo>
- +
-===== Requirement Status ===== +
- +
-Draft +
- +
-This requirement derives from MO-006 in the Crucible System Requirements Specification, Version 1.1 Draft.+
  
 ---- ----
Line 217: Line 153:
 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 should preserve the association between each Infrastructure Environment and an identified Operational Lifecycle.+The parent MO-006 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 
 +  * Each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] as the lifecycle subject 
 +  * An identified [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] revision as the governing lifecycle model 
 +  * The association between the Infrastructure Environment and the Operational Lifecycle revision
  
-The lifecycle-assignment record should identify:+The lifecycle-association record should identify:
  
   * The Infrastructure Environment identifier   * The Infrastructure Environment identifier
   * The Operational Lifecycle identifier   * The Operational Lifecycle identifier
   * The Operational Lifecycle revision   * The Operational Lifecycle revision
-  * The effective assignment condition +  * The effective association condition 
-  * The assignment date and time +  * The association date and time 
-  * The authority or process responsible for the assignment +  * The authority or process responsible for the association 
-  * The applicable operational environment +  * The operational environment 
-  * The applicable Deployment Platform +  * The Deployment Platform 
-  * The applicable security and compliance constraints +  * The security and compliance constraints 
-  * The associated Provenance +  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] 
-  * The associated Traceability +  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * The supporting Evidence+
  
-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:
  • dido/02-crusible/99-annexes/annex-c-requirements/01-mission-objectives/mo-006/mo-006a.1784563231.txt.gz
  • Last modified: 2026/07/20 09:00
  • by nick_dido