UML Timing Diagram Lab
Read order payment over time
Read the order state and receipt value on a shared scale in seconds. Distinguish an instant from the duration between two events.
Scroll the diagram horizontally on narrow screens. A text list also shows the state intervals.
Order state intervals
- Idle
[0, 2) s - Awaiting payment
[2, 6) s - Paid
[6, 16) s
State at observation end Paid
- No receipt observed
[0, 6) s - Receipt observed
[6, 16) s
Observation
Receipt accepted- Order state at end of observation
- Paid
- Deadline
- 7 s
- Request to receipt
- 4 s
- Actual wait
- 4 s
Time constraint
SatisfiedMeasure receipt time from the time origin [0, 12] s
Duration constraint
SatisfiedMeasure elapsed time from request to receipt [0, 5] s
A time constraint limits the receipt’s position on the time axis. A duration constraint measures the interval between request and receipt.
This case includes the deadline in the allowed interval. After the wait limit, the order times out at the deadline and the late receipt remains visible.
Notation and semantics
This case records whole seconds. A receipt must satisfy both the absolute window and the wait limit to be accepted. The diagram shows the observation interval, so the order may still be waiting if its deadline is beyond the axis.
OMG · UML 2.5.1 §§8.4–8.5, 17.11 ↗Drag a circular marker to change its time. You can also use the arrow keys on a focused marker or enter a time below.
Scroll the diagram horizontally on narrow screens. A text list also shows the state intervals.
Order state intervals
- Idle
[0, 2) s - Awaiting payment
[2, 6) s - Paid
[6, 16) s
State at observation end Paid
- No receipt observed
[0, 6) s - Receipt observed
[6, 16) s
Check the diagram to see which constraints and inputs need attention.
Observation
Receipt accepted- Order state at end of observation
- Paid
- Deadline
- 7 s
- Request to receipt
- 4 s
- Actual wait
- 4 s
Time constraint
SatisfiedMeasure receipt time from the time origin [0, 12] s
Duration constraint
SatisfiedMeasure elapsed time from request to receipt [0, 5] s
This case records whole seconds. A receipt must satisfy both the absolute window and the wait limit to be accepted. The diagram shows the observation interval, so the order may still be waiting if its deadline is beyond the axis.
Check the diagram to see which constraints and inputs need attention.
Drag a circular marker to change its time. You can also use the arrow keys on a focused marker or enter a time below.
Scroll the diagram horizontally on narrow screens. A text list also shows the state intervals.
Order state intervals
- Idle
[0, 2) s - Awaiting payment
[2, 7) s - Timed out
[7, 16) s
State at observation end Timed out
- No receipt observed
[0, 8) s - Receipt observed
[8, 16) s
Observation
Late receipt- Order state at end of observation
- Timed out
- Deadline
- 7 s
- Request to receipt
- 6 s
- Actual wait
- 5 s
Time constraint
SatisfiedMeasure receipt time from the time origin [0, 12] s
Duration constraint
ViolatedMeasure elapsed time from request to receipt [0, 5] s
This case records whole seconds. A receipt must satisfy both the absolute window and the wait limit to be accepted. The diagram shows the observation interval, so the order may still be waiting if its deadline is beyond the axis.
Sequence diagram · message order
The checkout sequence orders messages between the customer, order service and inventory. In the timing case, instants and waiting durations share a scale in seconds.
Open the checkout sequence ↗State machine · events and guards
The order state machine uses a payment event and guards to decide whether to transition. This case defines its own receipt and timeout rule and shows how long each state lasts.
Open the order state machine ↗How do you align the units?
A device reply takes 750 ms. The timing diagram uses seconds.