Author Topic: UML profile : stereotyped BPMN Data Object (Read 4152 times)

Guillaume · « **on:** January 10, 2015, 03:49:34 am »

Hi,

I would like to define a stereotype on BPMN2 data objects.
I started creating a UML profile: I created a metaclass in which I chose the Stereotypes tab, selected BPMN2.0 and DataObject.

I created a "test" stereotype with a dummy tagged value, linked via a Generalization link with the DataObject stereotype.

Unfortunately when generating the UML profile, this stereotype is not exported/seen.

Is there any way to extend BPMN2.0 stereotypes? (same actually applies to SysML, etc.)

Thanks

qwerty · « **Reply #1 on:** January 10, 2015, 07:49:32 am »

Actually this has been answered here (by the Sparxians) a couple of times.

q.

P.S. And once more below.

KP · « **Reply #2 on:** January 12, 2015, 10:01:35 am »

Your stereotype element needs to have a Generalization to an abstract «stereotype» named "BPMN2.0::DataObject" and an «extends» to a «metaclass» "Artifact".

Guillaume · « **Reply #3 on:** January 13, 2015, 12:42:10 am »

Thanks for the info

Sorry I couldn't find the info forum search.

For any other BPMN2.0, SysML or other stereotypes, is there any easy way in EA to find the extended Metaclass (e.g. find that the SysML "Block" stereotype extends the Class Metaclass) ?

qwerty · « **Reply #4 on:** January 13, 2015, 06:15:11 am »

You can look into the MDG file. The info is (I think) quite obvious once you got a working example.

q.

KP · « **Reply #5 on:** January 13, 2015, 09:30:59 am »

The other way is to remove the stereotype and see what you're left with

Guillaume · « **Reply #6 on:** June 17, 2015, 10:16:52 pm »

Hi,

I managed to get my stereotype applied on the BPMN2.0 Data Object & Artifact to work. I've generated an MDG Tech with a diagram profile & toolbox.

The remaining odd issue I have left is that the Quicklinker contains the list as defined in the Artifact metaclass. This happens when my element is displayed in any diagram other than BPMN2.0 (the Quicklinker is correct when used in a BPMN2 diagram).
Actually this issue already exists with the current BPMN2.0 Data Object i.e. if you drop one onto a UML Class diagram, the quicklinker will treat this element as an artifact, not a BPMN Data Object.

Any hint to fix this please?

As a temp solution, I've set my toolbox visible for all types of diagrams so that it can be used on a BPMN2.0 diagram.

Thanks
Guillaume

Sparx Systems Forum

News: