dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle [2026/07/11 11:14] – ↷ Links adapted because of a move operation nick_didodido:99_annexes:annex-b-terms-and-definitions:l:lifecycle [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 7: Line 7:
 A lifecycle describes how a thing progresses through states over time. A lifecycle identifies the states a thing enters, the events that cause state changes, the transitions between states, and the conditions that govern those transitions. A lifecycle describes how a thing progresses through states over time. A lifecycle identifies the states a thing enters, the events that cause state changes, the transitions between states, and the conditions that govern those transitions.
  
-A lifecycle applies to business objects, data objects, reports, trades, obligations, requirements, policies, messages, implementation artefacts, and other governed things whose status changes over time.+A lifecycle applies to business objects, data objects, reports, trades, obligations, requirements, policies, messages, implementation artifacts, and other governed things whose status changes over time.
  
 A lifecycle differs from a status value. A status value identifies one state at one point in time. A lifecycle defines the state progression, valid transitions, prohibited transitions, and rules that govern movement from one state to another. A lifecycle differs from a status value. A status value identifies one state at one point in time. A lifecycle defines the state progression, valid transitions, prohibited transitions, and rules that govern movement from one state to another.
Line 19: Line 19:
 ===== Source ===== ===== Source =====
  
-DIDO Solutions usage, informed by state-machine modelling, business process modelling, software architecture, and lifecycle governance practice.+DIDO Solutions usage, informed by state-machine modeling, business process modeling, software architecture, and lifecycle governance practice.
  
 ===== Note ===== ===== Note =====
Line 27: Line 27:
 ===== Example ===== ===== Example =====
  
-An FX trade lifecycle includes states such as ''Proposed'', ''Rejected'', ''Confirmed'', ''Settled'', and ''Cancelled''. The lifecycle defines valid transitions such as ''Proposed'' to ''Confirmed'' and ''Confirmed'' to ''Settled''. The lifecycle prohibits invalid transitions such as ''Proposed'' directly to ''Settled'' when confirmation is required before settlement.+An FX trade lifecycle includes states such as ''Proposed'', ''Rejected'', ''Confirmed'', ''Settled'', and ''Canceled''. The lifecycle defines valid transitions such as ''Proposed'' to ''Confirmed'' and ''Confirmed'' to ''Settled''. The lifecycle prohibits invalid transitions such as ''Proposed'' directly to ''Settled'' when confirmation is required before settlement.
  
 ---- ----
  • dido/99_annexes/annex-b-terms-and-definitions/l/lifecycle.1783793698.txt.gz
  • Last modified: 2026/07/11 11:14
  • by nick_dido