Assuming a diagram is synchronized (i.e.Sirius works hard to ensure that what you see on you sequence diagram (in terms of vertical ordering of elements and horizontal ordering of lifelines) always correspond to the semantic ordering of the represented events. However placing a message above or below another one has a strong implication on the ordering of the events they represent, and thus on the structure of the underlying semantic model which is represented. This is true for the vertical placement and for the left-to-right order of lifelines. The relative graphical positions of elements on a sequence diagram have strong meaning. The most important consequence of this is that contrary to what happens on a classical diagram, The canonical case is a UML Sequence Diagram (where the notation comes from), which represents the messages exchanged between objects in a software system.

Typically, they representĮvents sent and received between some entities over Obeo UML Behavioral viewpoint (available for free at ) which is based on the Eclipse Foundation’s UML2 meta-model.Īs their name says, sequence diagrams are meant to represent ordered sequences of elements. The resulting diagram is available in the the specification of a UML sequence diagram editor. This tutorial is based on an example, i.e. It has been written for software architects who want to specify sequence diagrams on their own meta-models.

This document describes how to specify sequence diagram modelers with Sirius.

Sequence Diagrams Specifying Sequence Diagram Editors

Draw sequence diagram online free