Endpoint

An Endpoint used in defining lost and found messages in Sequence, Timing, Communication and Interaction diagrams using Sparx Systems Enterprise Architect.

Description

An Endpoint is used in Interaction diagrams (Sequence, Timing, Communication or Interaction Overview) to reflect a lost or found Message in sequence. To model this, drag an Endpoint element onto the workspace.

With Sequence diagrams, drag a Message from the appropriate Lifeline to the Endpoint. With Timing diagrams, the Message connecting the Lifeline to the Endpoint requires some timing specifications to draw the connection.

This example depicts a lost Message in a Sequence diagram.

An example of an Endpoint on a Sequence Diagram using Sparx Systems Enterprise Architect.

Toolbox icon

End Point element

Learn more

OMG UML Specification:

The OMG Unified Modeling Language specification, (v2.5.1, p.574) states:

A lost Message is a Message where the sending event occurrence is known, but there is no receiving event occurrence. We interpret this to be because the destination of the [lost]Message is outside the scope of the description.

A found Message is a Message where the receiving event occurrence is known, but there is no (known) sending event occurrence. We interpret this to be because the origin of the Message is outside the scope of the description. This may for example be noise or other activity that we do not want to describe in detail.