Case study 2 · Transition table

Transition table of the MQLS lifecycle

The transition table condenses the MQLS lifecycle into a readable overview — derived from the semantic model.

NoteThis projection is a real, unaltered AI output. It was generated by GPT-5.6 Sol based on the semantic model and demonstrates that the method produces working, inspectable results — not only a concept, but a verifiable artefact.

Case study 2 – Transition table of the MQLS lifecycle

The transition table compresses the lifecycle of the Material Quality Lot Submission described in the semantic model into a readable business overview. For each transition it shows the triggering business action, allowed source state, authorisation, business requirements and guards, target state and published domain event.

It forms a compact bridge between the business state model, a process view and later technical projection. The table is based on the transition projection of the resolved enterprise model.

Transition table

Create

Source state: Undefined
Authorisation: Quality Supplier
Requirements / guards: Supplier ownership and user context available; part context available
Target state: Created
Domain event: MQLS Created

Publish

Source state: Created
Authorisation: Quality Supplier
Requirements / guards: No further requirements or guards
Target state: Created
Domain event: MQLS Published

Forward

Source state: Created
Authorisation: Quality Supplier
Requirements / guards: MQLS is consistent; required data correctly filled
Target state: Forwarded
Domain event: MQLS Forwarded

Delete

Source state: Created
Authorisation: Quality Supplier
Requirements / guards: No further requirements or guards
Target state: Deleted
Domain event: MQLS Deleted

Publish

Source state: Forwarded
Authorisation: Assigned Quality Manager with Quality Customer or Quality Admin
Requirements / guards: No further requirements or guards
Target state: Forwarded
Domain event: MQLS Published

Reject

Source state: Forwarded
Authorisation: Quality Customer and assigned Quality Manager
Requirements / guards: No further requirements or guards
Target state: Rejected
Domain event: MQLS Rejected

Authorize Shipment

Source state: Forwarded
Authorisation: Quality Customer and assigned Quality Manager
Requirements / guards: MQLS has consistent and correct data
Target state: Authorized for Shipment
Domain event: MQLS Authorized for Shipment

Return

Source state: Forwarded
Authorisation: Quality Customer and assigned Quality Manager
Requirements / guards: No further requirements or guards
Target state: In revision
Domain event: MQLS Returned

Publish

Source state: Authorized for Shipment
Authorisation: Assigned Quality Manager with Quality Customer or Quality Admin
Requirements / guards: No further requirements or guards
Target state: Authorized for Shipment
Domain event: MQLS Published

Reject

Source state: Authorized for Shipment
Authorisation: Quality Customer and assigned Quality Manager
Requirements / guards: No further requirements or guards
Target state: Rejected
Domain event: MQLS Rejected

Accept Finally

Source state: Authorized for Shipment
Authorisation: Quality Customer and assigned Quality Manager
Requirements / guards: Positively decided approval request present; guard requires positive second-approver decision where applicable; MQLS data consistent and correct
Target state: Finally Accepted
Domain event: MQLS Accepted Finally

Publish

Source state: Returned / In revision
Authorisation: Quality Supplier
Requirements / guards: No further requirements or guards
Target state: Returned
Domain event: MQLS Published

Forward

Source state: Returned
Authorisation: Quality Supplier
Requirements / guards: MQLS is consistent; required data correctly filled
Target state: Forwarded
Domain event: MQLS Forwarded

Delete

Source state: Returned
Authorisation: Quality Supplier
Requirements / guards: No further requirements or guards
Target state: Deleted
Domain event: MQLS Deleted

The table is a projection of the same semantic foundation used for Event Storming, decision logic and AI dialogue — not a separate source of truth.

← Case studies overview