States describe ongoing situations
Paid is a state, Pay is an event, and Record payment is a transition effect. Keep these roles distinct.
BEHAVIOR MODELING / 01
Select a state or transition to separate a situation, an occurrence and an effect.
Arrows show transition IDs and events. Full guards and effects appear in the inspector and list. All rounded rectangles are ordinary states.
Select a state or transition to inspect it. On small screens, scroll the diagram horizontally or use the list below.
The guide uses preset conditions. Compare the failed out-of-stock and post-shipment cancellation attempts with successful transitions.
Arrows show transition IDs and events. Full guards and effects appear in the inspector and list. All rounded rectangles are ordinary states.
Select a state or transition to inspect it. On small screens, scroll the diagram horizontally or use the list below.
Triggering from an earlier record replaces its future. Changing the model restarts the experiment. Failed attempts are recorded too.
Arrows show transition IDs and events. Full guards and effects appear in the inspector and list. All rounded rectangles are ordinary states.
Run the check after editing.
Arrows show transition IDs and events. Full guards and effects appear in the inspector and list. All rounded rectangles are ordinary states.
Select a state or transition to inspect it. On small screens, scroll the diagram horizontally or use the list below.
Triggering from an earlier record replaces its future. Changing the model restarts the experiment. Failed attempts are recorded too.
Paid is a state, Pay is an event, and Record payment is a transition effect. Keep these roles distinct.
Every business transition here has an explicit event. Guards read current conditions without side effects; true represents no restriction. UML supports other trigger mechanisms that this lab does not implement.
This lab uses external transitions: exit source → transition effect → enter target. An external self-transition also exits and re-enters; it differs from an internal transition.
The same Submit review event branches on approved and !approved. UML permits nondeterministic choice among equally prioritized conflicting transitions. This lab adds a unique-choice restriction and pauses otherwise.
Button events are handled one at a time. No deferred events, orthogonal regions or nested states are modelled. An occurrence with no enabled transition is consumed. Later stock availability does not replay an earlier Ship event.
Completed, Cancelled and Refunded are ordinary states without outgoing edges; they can still receive and ignore events. A UML FinalState uses a bullseye and completes its region. This running model has none. The solid dot is an initial pseudostate.
A book moves from Available to On loan on Borrow. The transition records the loan.
borrow [memberValid] / registerLoan