Skip to main content
← UML

UML Timing Diagram Lab

UML / TIMING / 01

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.

sd Order paymentTime constraint[0, 12] sDeadline 7 sRequest2 sReceipt6 sDuration constraint[0, 5] sOrder state lifelineIdleAwaiting paymentPaidTimed outReceipt value lifelineNo receipt observedReceipt observedTime / s0246810121416

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

Satisfied

Measure receipt time from the time origin [0, 12] s

Duration constraint

Satisfied

Measure 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 ↗
Blank area: ← → chapters · Native keys inside controls01 / 06
Preparing the model