What is a UML interaction overview diagram?
A UML interaction overview diagram connects interaction uses or inline interactions with activity-style control flow. It explains how larger conversations fit into a scenario.
The question this diagram answers: How do several interactions fit into a larger control flow?
Explore all 14 UML diagram types. Interaction diagrams are a specialized subset of UML behavior diagrams.
When to use a interaction overview diagram
Use an interaction overview to explain orchestration across scenarios without drawing every message on one canvas. It uses activity-style control flow to connect interaction uses or inline interactions.
Main elements and notation
Interaction use
A ref frame identifies an interaction being reused or referred to, such as Checkout or Fulfillment.
Initial and final nodes
These delimit the overview flow.
Decisions and merges
Guarded alternatives select an interaction path or bring alternative paths together.
Forks and joins
These express concurrent paths and synchronization where that is intended.
Control flow
Directed connections establish flow between the interactions and control nodes.
A real example in UXXU

Actual UXXU Desktop screenshot of an illustrative commerce project. Open the full-size example.
The example links checkout to fulfillment or payment recovery. Treat each referenced interaction as a larger conversation whose internal messages can be explained separately. Read the guard at the decision before selecting the next interaction.
Draw it in UXXU
Open an editable project, add a Code (UML) diagram, and choose Interaction overview as its UML diagram type.
- Add initial and final nodes to establish the scenario boundary.
- Add interaction references and name the conversations they represent.
- Connect them through the required decisions, merges or parallel-flow nodes.
- Write clear guards and supporting notes that explain where the detailed interactions are documented.
Select an element or connector to edit its properties. Use editable text for advanced notation where appropriate. Move and resize elements to keep labels readable; save your workspace and reopen the diagram to review the result. Editing availability depends on your plan or desktop licence.
Common mistakes and review checks
An editable interaction reference label in UXXU is not an automatic cross-diagram model reference. Keep names consistent and review the overview together with the detailed sequence diagrams.
Before sharing, check that names are consistent, connector directions are intentional, and labels do not cover the notation they describe. Ask another reader to answer the question at the top of this guide using only the diagram.
Choose the next view
UXXU focuses on visual authoring. These guides do not imply executable UML models, automatic semantic validation, or shared UML model-element references across diagrams. PlantUML import/export compatibility is separate from visual notation coverage. Check the download page for published desktop releases.
For normative UML definitions, consult the OMG UML 2.5.1 specification.