Eclipse Community Forums: Papyrus » Activity Diagrams in Papyrus

Home » Modeling » Papyrus » Activity Diagrams in Papyrus - Advanced Features(Object node, swimlane, and parameter set notations in Activity Diagrams)

Show: Today's Messages :: Show Polls :: Message Navigator

Activity Diagrams in Papyrus - Advanced Features [message #1751773]

Fri, 13 January 2017 16:57

Sadaf Mustafiz

Messages: 4
Registered: January 2017

Junior Member

Hi,

From what I understand based on the activity diagram tutorial posted, it is not possible to create object nodes in Papyrus activity diagrams (ADs) and only pins can be attached to actions/activities to denote objects. I need to use some of the AD notations (as specified in the OMG UML superstructure) and would like to know if the current version of AD in papyrus supports the following.

- specifying multicast and multireceive by placing an object node on the edge of partitions (swimlanes) (as shown in Fig. 15.18 in formal/15-03-01): Is there any other way to depict this in Papyrus?

- object flows into decision nodes: I can't seem to find a way to add a decision input flow to a decision node (to show that the decision is based on some input objects).

- multi-dimensional swimlane notation: Is there a way to add both vertical and horizontal partitions in an activity diagram (as shown in Fig. 15.66c in formal/15-03-01)?

- parameter sets notation: Is there a way to add input pins as parameter sets to depict possible alternate sets of inputs that can trigger an activity (like in Fig. 16.23 in formal/15-03-01)

If one or more of these features are not as yet supported by Papyrus, is there any plan to add them in the near future?

Appreciate your time and help.

Report message to a moderator

Re: Activity Diagrams in Papyrus - Advanced Features [message #1752192 is a reply to message #1751773]

Thu, 19 January 2017 15:40

Arnaud Cuccuru

Messages: 34
Registered: April 2010

Member

Hi,
Thanks for your feedbacks. A few comments :

- specifying multicast and multireceive by placing an object node on the edge of partitions (swimlanes) (as shown in Fig. 15.18 in formal/15-03-01): Is there any other way to depict this in Papyrus?

This notation is not supported

- multi-dimensional swimlane notation: Is there a way to add both vertical and horizontal partitions in an activity diagram (as shown in Fig. 15.66c in formal/15-03-01)?

This notation is not supported

- parameter sets notation: Is there a way to add input pins as parameter sets to depict possible alternate sets of inputs that can trigger an activity (like in Fig. 16.23 in formal/15-03-01)

I am not familiar with ParameterSets, but the diagram in Fig. 16.23 depicts an InvocationAction, with multiple argument pins. As you probably know, argument pins are implicitly mapped to paremeters of the invoked behavior or operation. In the behavior or operation definition, these parameters can be grouped into ParameterSets. However, Papyrus does not provide any notation to represent at the pin level the grouping specified at the parameter level.

We don't have plans in the near future to fix these limitations (at least, by the Oxygen release). We have ongoing development activities to improve ergonomy of activity diagrams (we plan to make annoucements soon about this), but our focus at the moment is on executable activity modeling, as defined in OMG specifications fUML and PSCS (so for example, Activity partitions are out of the scope of this work).

Regarding the last limitation you have found :

- object flows into decision nodes: I can't seem to find a way to add a decision input flow to a decision node (to show that the decision is based on some input objects).

Indeed, the « UML tab » of the property view is rather empty when selecting a DecisionNode. This is certainly something that we should fix for the Oxygen release. Meanwhile, you can go to the « advanced tab » of the property view, where you have the possibility to select the decision input flow.

Cheers,
Arnaud

Report message to a moderator

Re: Activity Diagrams in Papyrus - Advanced Features [message #1752294 is a reply to message #1752192]

Fri, 20 January 2017 16:57

Sadaf Mustafiz

Messages: 4
Registered: January 2017

Junior Member

Hi Arnaud,

Thanks a lot for your response and for the clarifications.

You mentioned: "In the behavior or operation definition, these parameters can be grouped into ParameterSets. " Could you elaborate a bit more of this please. Does this mean that the parameter sets can be define in the ActivityParameterNode itself and in the calling activity (created as a Call Behaviour Action).

Is there any documentation/tutorial available on executable activity modelling support in Papyrus?

Thank you!

Report message to a moderator

Previous Topic:	Moving Properties and Operations to a different class
Next Topic:	Does Papyrus support OSLC

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Oct 09 03:15:26 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter