Home » Modeling » Papyrus » Sequence Diagram, messages as ordered set
Sequence Diagram, messages as ordered set [message #1006572] |
Thu, 31 January 2013 20:24 |
|
I have noticed that when changing the sequence of messages in an sequence diagram, the changes in the diagram are not reflected in the messages order within the model. Thus I guess that, during a possible transformation, I will not get the messages in the order specified in the diagram. The same thing holds for the message occurrence specifications in the Interaction.fragment
what am I missing?
I am using
Eclipse Modeling Tools
Version: Juno Service Release 1
Build id: 20120920-0800
with
Papyrus 0.9.1.v201209290809
On a Mac Os 10.7.5
Follow me on Twitter @andreasindico
|
|
| |
Re: Sequence Diagram, messages as ordered set [message #1006848 is a reply to message #1006572] |
Sat, 02 February 2013 20:40 |
Eclipse User |
|
|
|
Andrea,
the order of the message is completely irrelevant in sequence diagrams. They
are ordered by the MessageOccurrenceSpecifications that cover the lifelines
and combine the messages; these are eventually ordered through
Interaction.fragment on purpose.
>The same thing holds for the message occurrence specifications in the
>Interaction.fragment
This confuses me; I just tried it with the last Papyrus version 0.9.1 and
the order in Interaction.fragments is updated, when I moved messages in the
diagram. Be aware that the current implementation of sequence diagrams in
Papyrus only react on moving OccurrenceSpecifications and its subclasses
(like MessageOccurrenceSpecification). If you, e.g., move CombinedFragments
or StateInvariants, the order of fragments will not correspond to the
diagram. Fortunately, the correct order is recalculated every time you touch
an OccurrenceSpecification. So, when you wildly move things in the sequence
diagram, just touch an OccurrenceSpecification before running your
transformation.
Regards,
Marc-Florian
"Andrea Sindico" schrieb im Newsbeitrag
news:keejtl$cgn$1@xxxxxxxxe.org...
I have noticed that when changing the sequence of messages in an sequence
diagram, the changes in the diagram are not reflected in the messages order
within the model. Thus I guess that, during a possible transformation, I
will not get the messages in the order specified in the diagram. The same
thing holds for the message occurrence specifications in the
Interaction.fragment
what am I missing?
I am using
Eclipse Modeling Tools
Version: Juno Service Release 1
Build id: 20120920-0800
with
Papyrus 0.9.1.v201209290809
On a Mac Os 10.7.5
--
Follow me on Twitter https://twitter.com/andreasindico
|
|
| | |
Re: Sequence Diagram, messages as ordered set [message #1008576 is a reply to message #1007956] |
Wed, 13 February 2013 07:20 |
Eclipse User |
|
|
|
Andrea,
okay, that's good to know and reassures me.
As I said, be aware that only the shifting of OccurrenceSpecifications
update the order; if you move CombinedFragments or StateInvariants, the
Interaction.fragments list won't be updated ever. In such a case, simply
touch a OccurrenceSpecification by touching and slightly moving a message
and the list order we be recalculated.
Regards,
Marc-Forian
"Andrea Sindico" schrieb im Newsbeitrag
news:kf2v2a$sbo$1@xxxxxxxxe.org...
the same example works (the message occurrences order is updated in the
interaction fragment within the model) when executed with the same
configuration (Eclipse Juno + Papyrus)on Windows. I therefore guess the
problem may be related to the Mac Os environment.
--
Follow me on Twitter https://twitter.com/andreasindico
|
|
| |
Re: Sequence Diagram, messages as ordered set [message #1019126 is a reply to message #1019071] |
Fri, 15 March 2013 04:53 |
Steve Solomon Messages: 2 Registered: March 2013 |
Junior Member |
|
|
I also tried it under Juno MDT, build 0.9.2.v201302131112.
Same issue. Fragments of type MessageOccurenceSpecification are not in diagram order in the .uml file.
Please see the attached .uml, .di, and .notation files.
Thanks,
-Steve Solomon
-
Attachment: model.di
(Size: 0.67KB, Downloaded 287 times) -
Attachment: model.notation
(Size: 24.28KB, Downloaded 276 times) -
Attachment: model.uml
(Size: 10.11KB, Downloaded 279 times) -
Attachment: .project
(Size: 0.22KB, Downloaded 323 times)
|
|
|
Goto Forum:
Current Time: Wed Sep 25 23:02:44 GMT 2024
Powered by FUDForum. Page generated in 0.03786 seconds
|