DYNAMIC UMLs / SIX WAYS TO SEE A SYSTEM
Understand it.
One step at a time.
Choose a diagram to explore. Each example is a standalone HTML file with playback, an element inspector, and visible assumptions. Open it locally — everything works offline.
The three-party sign-in ↗
Messages between participants, in time order.
/ct-dynamic-uml-sequenceAn order, made explicit ↗
Ownership, cardinality and specialization.
/ct-dynamic-uml-classIs this change ready? ↗
A vertical decision path, side retry rail and nested repair flow.
/ct-dynamic-uml-flowchartThe life of an order ↗
Events, guards and an order lifecycle.
/ct-dynamic-uml-stateTwo checks, one dispatch ↗
Concurrent branches with a fork and join.
/ct-dynamic-uml-activityOne source, three agents ↗
Repository boundaries and dependencies.
/ct-dynamic-uml-componentLong sequence: 32 messages across six participants ↗
Examples for template review. The sequence, class, flowchart, state and activity examples are illustrative; the component view follows the local repository. Flowcharts are general process notation rather than a formal UML diagram type. These pages explain systems; they do not execute them.