state·OMG UML 2.5.1·software, saas, billing·complexity 3/3·since v0.3.0
SaaS subscription lifecycle
UML statechart for a subscription moving through trial, active service, payment recovery, pause, cancellation, and reactivation.
For the SaaS product engineer
state-diagram·§ UML 2.5 / Harel
↘ preview
100%
UTF-8 · LF · 34 lines · 1139 chars✓ parsed·4.1 ms·12.6 KB SVG
Scenario
Subscription logic is where simple status enums drift out of sync with billing providers. This statechart makes the product contract explicit: trial conversion, incomplete setup, dunning recovery, pause, cancellation, and reactivation are separate transitions with guards and actions.
Annotation key
Activeis a composite state because payment recovery happens while the product is still notionally active.- Guard labels such as
[payment_method_valid]document provider-dependent branching. - Entry and exit actions mark entitlement provisioning and sync points.