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

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006c [2026/07/21 09:57] – ↷ Links adapted because of a move operation nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006c [2026/07/30 05:28] (current) – [Delivery Phase] nick_dido
Line 1: Line 1:
-====== MO-006c — Current Lifecycle State Determination ======+====== MO-006c — Infrastructure Lifecycle State Recording ======
  
 [[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 determine the current [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] state of each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]].+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL record the current [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] state of each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]].
  
 ===== 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-006c preserves the lifecycle-management intent of the Original Requirement by requiring Crucible to determine the current Operational Lifecycle state of each Infrastructure Environment.+MO-006c preserves the lifecycle-management intent of the Original Requirement by requiring Crucible to record the current Operational Lifecycle state of each Infrastructure Environment.
  
 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-006a|MO-006a — Operational Lifecycle Assignment]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006a|MO-006a — Operational Lifecycle Association]] 
-  * [[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-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 Crucible to determine the current lifecycle state of an Infrastructure Environment. 
- 
-Without current lifecycle-state determination, an evaluator cannot reliably determine: 
- 
-  * The current position of the Infrastructure Environment within its assigned Operational Lifecycle 
-  * Whether the Infrastructure Environment completed its preceding transition 
-  * Which lifecycle transitions are available 
-  * Which transition conditions apply 
-  * Whether the Infrastructure Environment remains in an intermediate or failed state 
-  * Whether the Infrastructure Environment has entered Retirement 
-  * Whether the reported state agrees with observable environment conditions 
- 
-The phrase **lifecycle management** does not identify: 
- 
-  * The lifecycle state being determined 
-  * The Infrastructure Environment associated with the state 
-  * The assigned Operational Lifecycle governing the state 
-  * The criteria used to determine the state 
-  * The time at which the determination applies 
-  * The treatment of indeterminate or conflicting state information 
-  * The Evidence required to support the determination 
- 
-MO-006c: 
- 
-  * 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 determination 
-  * Identifies the current Operational Lifecycle state as the required result 
-  * Separates state determination from lifecycle assignment, lifecycle initiation, transition execution, and Retirement 
  
 ===== Rationale ===== ===== Rationale =====
  
-The current Operational Lifecycle state identifies the position of an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] within its assigned [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]].+The current Operational Lifecycle state identifies the position of an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] within its associated [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] revision.
  
-Lifecycle states can include:+The associated Operational Lifecycle revision defines the permitted states. Those states can include:
  
   * Initial Deployment   * Initial Deployment
Line 76: Line 45:
   * Retirement   * Retirement
  
-The assigned Operational Lifecycle defines the applicable states. An Infrastructure Environment does not necessarily use every state listed above.+An Infrastructure Environment does not necessarily use every state listed above.
  
-Current lifecycle-state determination supports:+Recording the current lifecycle state supports:
  
   * Selection of permitted lifecycle transitions   * Selection of permitted lifecycle transitions
Line 90: Line 59:
   * 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]] 
  
-The state determination can use:+The recorded lifecycle state can be based on:
  
-  * The assigned Operational Lifecycle+  * The associated Operational Lifecycle revision
   * The preceding lifecycle state   * The preceding lifecycle state
   * The most recent completed transition   * The most recent completed transition
-  * Transition completion results +  * The transition result 
-  * Infrastructure Environment observations +  * Observable Infrastructure Environment conditions 
-  * Deployment and configuration records+  * Infrastructure Deployment records 
 +  * Configuration records
   * Validation results   * Validation results
-  * Compliance and security results+  * Compliance results 
 +  * Security results
   * Failure and exception records   * Failure and exception records
  
-A failed or incomplete transition does not imply successful entry into its intended target state. The applicable Operational Lifecycle defines the state associated with transition failure or incomplete execution.+A failed or incomplete transition does not establish successful entry into its intended target state.
  
-This requirement determines the current state. It does not require Crucible to execute a lifecycle transition. MO-006d establishes lifecycle transition execution.+This requirement records the current lifecycle state. It does not execute a lifecycle transition. MO-006d addresses lifecycle transition execution.
  
-This requirement does not assign or initiate the Operational Lifecycle. MO-006a and MO-006b establish those requirements.+This requirement does not associate or initiate the Operational Lifecycle. MO-006a and MO-006b address those outcomes.
  
-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 119: Line 89:
   * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]]   * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]]
   * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycles]]   * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycles]]
 +  * Operational Lifecycle revisions
   * Operational Lifecycle states   * Operational Lifecycle states
   * Lifecycle-state criteria   * Lifecycle-state criteria
-  * Lifecycle-state determinations +  * Lifecycle-state records 
-  * Lifecycle assignments+  * Lifecycle associations
   * Lifecycle-initiation records   * Lifecycle-initiation records
   * Lifecycle transitions   * Lifecycle transitions
Line 142: Line 113:
 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 
-  - The assigned Operational Lifecycle is identified +  - The associated [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] identifier and revision are identified 
-  - The states defined by the assigned Operational Lifecycle are identified +  - The states defined by the associated Operational Lifecycle revision are identified 
-  - The criteria applicable to each candidate state are identified +  - The criteria for each candidate lifecycle state are identified 
-  - Crucible determines one current lifecycle state for the Infrastructure Environment +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] records one current lifecycle state for each Infrastructure Environment 
-  - The determined state belongs to the assigned Operational Lifecycle +  - The recorded lifecycle state belongs to the associated Operational Lifecycle revision 
-  - The determined state agrees with the applicable lifecycle records and observable environment conditions +  - The recorded lifecycle state agrees with the lifecycle records and observable Infrastructure Environment conditions 
-  - A failed or incomplete transition does not produce an unsupported target-state determination +  - A failed or incomplete transition does not produce an unsupported target-state record 
-  - Conflicting or insufficient state information produces an identified determination result +  - Conflicting or insufficient state information produces an identified result 
-  - The state determination preserves the required Evidence, Provenance, and Traceability+  - The lifecycle-state record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Infrastructure Environment, Operational Lifecycle revision, preceding state, transition result, observed conditions, and recorded current state
  
-Verification includes:+===== Referenced By =====
  
-  * Infrastructure Environment inspection +The following pages reference this requirement:
-  * Operational Lifecycle assignment inspection +
-  * Operational Lifecycle state inspection +
-  * Lifecycle-state criteria inspection +
-  * Lifecycle-initiation record inspection +
-  * Lifecycle-transition record inspection +
-  * Transition-result inspection +
-  * Infrastructure Deployment record inspection +
-  * Configuration-state inspection +
-  * Validation-result inspection +
-  * Compliance-result inspection +
-  * Security-result inspection +
-  * Failed-transition testing +
-  * Incomplete-transition testing +
-  * Conflicting-state-information testing +
-  * Lifecycle-state determination testing +
-  * 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 candidate lifecycle states +
-  - The criteria applicable to each candidate state +
-  - The preceding lifecycle state +
-  - The most recent lifecycle transition +
-  - The transition result +
-  - The observable environment conditions +
-  - The determined current lifecycle state +
-  - The determination date and time +
-  - Each conflicting or insufficient source of state information +
-  - 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:start|OR-001 — Operational Roles]] +<todo>Assess whether the current Crucible implementation records the current Operational Lifecycle state of each Infrastructure Environment.</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-004|OR-004 — Concurrent Environment Management]] +
-  * [[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-06-compliance-management:start|FR-COMP-001 through FR-COMP-010]]+
  
-===== Related Architecture Sections =====+===== Requirement Status =====
  
-  * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] +<todo>Review and accept MO-006c 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:09-compliance-and-security:start|9. Compliance and Security]] +
-  * [[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>Define the lifecycle states contained in each Operational Lifecycle revision.</todo>
  
-===== Delivery Phase =====+<todo>Define the criteria used to assign each lifecycle state.</todo>
  
-Phase 1 and subsequent phases+<todo>Define the source information Crucible uses to establish the current lifecycle state.</todo>
  
-===== Implementation Status =====+<todo>Define the behavior required when lifecycle records and observable Infrastructure Environment conditions conflict.</todo>
  
-Not Assessed+<todo>Define the state recorded after a failed, incomplete, interrupted, or rolled-back lifecycle transition.</todo>
  
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation determines the current Operational Lifecycle state of each Infrastructure Environment. +<todo>Define when Crucible updates the current lifecycle-state record.</todo>
- +
-===== Requirement Status ===== +
- +
-Draft +
- +
-This requirement derives from MO-006 in the Crucible System Requirements Specification, Version 1.1 Draft.+
  
 ---- ----
Line 243: Line 166:
 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 determination of the current Operational Lifecycle state for each Infrastructure Environment.+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 
 +  * The current [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] state as the recorded information 
 +  * The associated Operational Lifecycle revision as the source of permitted states
  
-The lifecycle-state determination record should identify:+The lifecycle-state record should identify:
  
   * The Infrastructure Environment identifier   * The Infrastructure Environment identifier
Line 254: Line 184:
   * The transition result   * The transition result
   * The candidate lifecycle states   * The candidate lifecycle states
-  * The applicable state criteria +  * The state criteria 
-  * The observable environment conditions +  * The observable Infrastructure Environment conditions 
-  * The determined current lifecycle state +  * The recorded current lifecycle state 
-  * The determination date and time +  * The recording date and time 
-  * The actor or process responsible for the determination +  * The actor or process responsible for the record 
-  * 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-006c.1784653070.txt.gz
  • Last modified: 2026/07/21 09:57
  • by nick_dido