Activity Diagram discrepancy in UML and SysML

[Sonali Arora]

Hi SysML Enthusiasts,

I am working on a SysML model in Papyrus. When I draw an Activity Diagram in SysML, it has less features on the Palette on the right side than the feautures available in UML.

I have attached the screenshots of both the Palettes.

Does anyone of you has also experienced a similar issue?

Please help me out if you know how I can access all the features in SysML as well.

TIA and Cheers

Sonali

[Tom Westbury]

Hi Sonali,

A bit of a hack:

You should be able to fix this by right clicking on any model element in the browser and choose "Switch Architecture Context..." and choose UML, then switch it back to SysML when you're done

The Papyrus developers have simplified the activity palette in the SysML perspective architecture view, possibly because not many SysML users use the more advanced aspects of activity diagrams

Hope this helps,

Tom

[jozsef bedocs]

It would appear that Papyrus has organized their UML pallet around ALF.  ALF is an executable action language for Activity Diagrams in UML.  SysML uses a subset of UML elements for Activity Diagrams.  Other tools treat UML and SysML as profiles that can be added into a project, which enables the use of both.  I have not used Papyrus; so, I don't know whether that tool allows a mixed environment. The answer lies within Papyrus' implementation of profiles. 

[Sonali Arora]

Hi Tom,

Thank you for you reply. This seems to work, I just tried it. But later, when I will try to validate it and simulate it, do you think I will face a problem because of different Profiles?

Thanks,

Sonali

[Sonali Arora]

Hi Jozsef,

Thank you so much for the reply. I will look into the Implementation of Profiles in Papyrus.

Sonali

On Thursday, July 9, 2020 at 7:03:47 PM UTC+2, jozsef bedocs wrote:

[Tom Westbury]

Hi Sonali, 

It shouldn't be a problem as long as you stick to using only the stereotypes and elements in the FUML spec: https://www.omg.org/spec/FUML/1.1/PDF for any animation. FUML is a subset of UML that has been given executable semantics by the OMG (I believe that most of FUML is contained by UML4SysML). Moka is an implementation of this standard (though there may be subtle differences as I have not explored this more than a simple demo).

The SysML 1.4 profile for papyrus is provided with OCL constraints where applicable so you should be able to validate the model as correct SysML syntax using just the inbuilt OCL interpreter.

If you need a long term fix for the Architecture Context, you can produce your own architecture contexts for papyrus, there is a section on this in the papyrus manual in the eclipse help documentation (help -> help contents). This is how you can change the tool palettes in diagrams as well as creating new diagram types if needed.