Book a Demo

Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

Interaction Overview Diagram

Interaction Overview diagrams visualize the cooperation between other Interaction diagrams to illustrate a control flow serving an encompassing purpose. As Interaction Overview diagrams are a variant of Activity diagrams, most of the diagram notation is the same, as is the process of constructing the diagram.

Decision points, Forks, Joins, Start points and End points are the same. Instead of Activity elements, however, rectangular elements of two types are used:

  • Interaction elements display an inline Interaction diagram, which can be any one of the four types (Sequence, Timing, Communication or Interaction Overview)
  • Interaction Occurrence elements are references to an existing Interaction diagram: they are visually represented by a frame, with ref in the frame's title space; the diagram name is indicated in the frame contents

To create an Interaction Occurrence, simply drag an Interaction diagram from the Browser window onto your Interaction Overview diagram. The ref frame displays, encapsulating an instance of the Interaction diagram.

You generate Interaction Overview diagram elements and connectors from the 'Activity' pages of the Diagram Toolbox.

Example Diagram

This diagram depicts a sample sale process, shown in an Interaction Overview diagram, with sub-processes abstracted within Interaction Occurrences.

The diagram appears very similar to an Activity diagram, and is conceptualized the same way; as the flow moves into an interaction, the respective interaction's process must be followed before the Interaction Overview's flow can advance.

An Interaction Overview diagram example using Sparx Systems Enterprise Architect.

Interaction Overview Diagram Element Toolbox Icons



See also

Partition element

A Partition element is used to logically organize elements.

Decision element

A Decision is an element that indicates a point of conditional progression: if a condition is true, then processing continues one way; if not, then another.

Send element

The Send element is used to depict the action of sending a signal.

Receive element

A Receive element is used to define the acceptance or receipt of a request.

Synchronize element

A Synch state is useful for indicating that concurrent paths are synchronized. They are used to split and rejoin periods of parallel processing.

Initial element

The Initial element defines the start of a flow when an Activity is invoked.

Final element

The Final element, indicates the completion of an Activity; upon reaching the Final, all execution is aborted.

Flow Final element

The Flow Final element depicts an exit from the system, as opposed to the Activity Final, which represents the completion of the Activity.

Flow Final
Region element

Enterprise Architect supports two types of Region element: Expansion Regions and Interruptible Activity Regions.

An Expansion Region surrounds a process to be imposed multiple times on the incoming data, once for every element in the input collection.

An Interruptible Activity Region surrounds a group of Activity elements, all affected by certain interrupts in such a way that all tokens passing within the region are terminated should the interruption(s) be raised.

Exception element

The Exception Handler element defines the group of operations to carry out when an exception occurs.

A Merge Node for UML Activity diagrams as used in Sparx Systems Enterprise Architect models.

A Merge Node brings together a number of alternative flow paths in Activity, Analysis and Interaction Overview diagrams.

Horizontal Fork/Join element

A Fork/Join element can be used to: 1) split a single flow into a number of concurrent flows, 2) join a number of concurrent flows or 3) both join and fork a number of incoming flows to a number of outgoing flows.

Fork/Join Fork Join
Vertical Fork/Join element

A Fork/Join element can be used to: 1) split a single flow into a number of concurrent flows, 2) join a number of concurrent flows or 3) both join and fork a number of incoming flows to a number of outgoing flows.

Interaction Overview Diagram Connector Toolbox Icons



See also

Control Flow connector

The Control Flow is a connector connecting two nodes, modeling an active transition.

Control Flow
Object Flow connector

An Object Flow connects two elements, with specific data passing through it, modeling an active transition.

Object Flow
Interrupt Flow connector

The Interrupt Flow is a connection used to define the two UML concepts of connectors for Exception Handler and Interruptible Activity Region.

Interrupt Flow

Learn more