Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Operational Lifecycle ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An Operational Lifecycle is a specialization of [[public: | ||
| + | |||
| + | The Operational Lifecycle identifies the [[public: | ||
| + | |||
| + | Examples of operational subjects include: | ||
| + | |||
| + | * An [[public: | ||
| + | * An [[public: | ||
| + | * An [[public: | ||
| + | * A [[public: | ||
| + | * A deployed service | ||
| + | * A software component | ||
| + | * A controlled [[public: | ||
| + | |||
| + | Examples of Operational Lifecycle States include states associated with: | ||
| + | |||
| + | * Definition | ||
| + | * Creation | ||
| + | * Configuration | ||
| + | * Validation | ||
| + | * Approval | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * Activation | ||
| + | * Operation | ||
| + | * Maintenance | ||
| + | * Modification | ||
| + | * Recovery | ||
| + | * Replacement | ||
| + | * Retirement | ||
| + | * Decommissioning | ||
| + | * Archiving | ||
| + | |||
| + | Events cause or request transitions between Operational Lifecycle States. Applicable controls and transition conditions determine whether a transition occurs. | ||
| + | |||
| + | An Operational Lifecycle differs from a workflow: | ||
| + | |||
| + | * An Operational Lifecycle describes the Operational Lifecycle States, events, transitions, | ||
| + | * A workflow coordinates activities performed to achieve a bounded result | ||
| + | |||
| + | An Operational Lifecycle contains or references the workflows used to perform its lifecycle activities. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | The beginning and end of an Operational Lifecycle depend on the operational subject and its governing lifecycle definition. | ||
| + | |||
| + | For an Infrastructure Environment, | ||
| + | |||
| + | For an Artifact, the Operational Lifecycle begins with the state identified by its governing lifecycle definition and continues through the states and transitions defined for that Artifact. | ||
| + | |||
| + | An Operational Lifecycle does not require every operational subject to pass through the same Operational Lifecycle States or transitions. | ||
| + | |||
| + | The applicable architecture, | ||
| + | |||
| + | * Permitted [[public: | ||
| + | * Applicable events | ||
| + | * Permitted transitions | ||
| + | * Transition conditions | ||
| + | * Responsible actors | ||
| + | * Required records | ||
| + | |||
| + | The term does not prescribe a particular process model, workflow engine, deployment method, platform, or implementation technology. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | The Operational Lifecycle of an Infrastructure Environment progresses from definition through provisioning, | ||
| + | |||
| + | A deployment event initiates a transition from a prepared [[public: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||