Basically, anything which would make it possible on a normal diagram to have meaningful semantic elements not visible on the diagram is forbidden. In order to guarantee the strong guarantee described above, some of the features present on normal diagrams are not supported, or even completely disabled on sequence diagrams. Most of the specific features and restrictions of sequence diagrams compared to other diagrams derive from this strong guarantee that at all time, the graphical (vertical) order of the elements you see on the diagram match exactly the semantic order of the events which exist in the underlying model. Keeping the example above, moving executionĮ1 will trigger changes in the semantic model to move the corresponding event of This is very different from what happens in other diagrams, where most graphical repositioning of elements are only cosmetic. Moving elements on a sequence diagram may trigger changes in the underlying semantic model to reflect the new event order implied by the positions you changed. Symmetrically, and perhaps more importantly,.you are inĪutomatic Refresh mode or your manually refreshed it since the last semantic changes), Sirius will always organize the elements on the diagram in a way which is compatible with the semantic ordering of the events: if you see an executionĮ2, you can be sure the events corresponding to Assuming your 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 Sirius preferences page) to ensure the diagram is always kept in synch with the underlying semantic model.Īs their name says, sequence diagrams are meant to represent ordered sequences of elements. Since Sirius 3.1.0, the snap features are automatically disabled in Sequence diagram editors and the user can not reactivate them. Snap to shapes for new diagrams check boxes. Sirius > Sirius Diagram > Rulers and Grid, un-check the You can also disable it for all future diagrams in the preferences: Properties view when the diagram itself is selected. For an existing diagram, this is available in the This means that to use sequence diagrams you IMPORTANT WARNING: To work correctly, Sirius sequence diagrams must have a tight control on where the graphical elements are placed on the diagram and on their synchronization with the underlying semantic model.
The general diagrams user manual for more information. Unless otherwise stated here, all the features of normal Sirius diagrams apply also to sequence diagrams, so you can refer to This document only describes the specificities of sequence diagrams. They also support some additional features or change the classical behavior of some features. These diagrams behave mostly like normal Sirius diagrams, but in order to ensure the consistency of the models they represent, they have some restrictions. Here is an example which illustrates most of the graphical constructions which can appear on these diagrams: Sirius supports a special kind of diagrams which reuse the notations and conventions of UML Sequence Diagrams, but can be applied to other domains than just UML. Sequence diagrams share most of the functionalities of normal diagrams, but they have some specificities and restrictions. This document explains how to use sequence diagrams editors/modelers. Sequence Diagrams Sequence Diagrams Editors
0 kommentar(er)
