Extending Archimate Element using UML Profile

[gpatenaude]

Is it possible to extend a certain type of element (Archimate 2.0 Device from the technology layer in my case).

I need the extented element to respect the following constraints:

1.  Has default tag values (CPU, memory, etc.) when I drag and drop the element in a diagram
2.  Has the same look and feel than a Archimate 2.0 device when I drop it in a Archimate 2.0 Technology layer diagram.

Thanks in advance!

[Glassboy]

w00t I beat Paolo

Yes, you use the Archimate type as an abstract meta-type and have an extend from it, and the base class (which from memory is class).  If you need more help sing out and i'll try and work out if I can upload a picture to anywhere from here.

[gpatenaude]

Thanks for your reply!

The problem is there is no abstract metatype for Archimate elements.  From my understanding, it is a stereotype "ArchiMate_Device" on a class that makes the rendering.  I can't find a way to extend the stereotype.

Here's my profile diagram:
https://www.dropbox.com/s/e1gpgkhy1eshrib/2016-03-03_15-27-42.png?dl=0

[Glassboy]

You're using the quick linker?  Don't, just grab the extend from the toolbox.

[Glassboy]

Oh and make the abstract metaclass, a metaclass not a stereotype.

[gpatenaude]

I'm missing something    I can't find any Metaclass element for "Archimate_Device".

Another screenshot:
https://www.dropbox.com/s/1idah1kgkl2sb4a/2016-03-03_15-52-29.png?dl=0

[gpatenaude]

I was thinking... Is it possible to export the Shape Script from the original "Archimate_Device" stereotype and reimport it for my  derived stereotype?

Thanks in advance!

[qwerty]

The shape script is stored in the MDG in a base64 encoded and packed format. You need to decode the base64 which results in a zip data file. This can be unpacked using standard zip tools. The contents might be copyrighted by Sparx. I guess as long as you use it for your company internally it should not really be an issue. Asking Sparx wouldn't be the worst to do, I guess.

q.

[Glassboy]

I've never done it the way you are.  I just created it manually.  Drop a metaclass on and give it the appropriate name (inc namespace).

yes you can copy the shapescript.  Create some shapescript on an element.  Open the MDG file.  Cut and paste the shapescript attribute over top of the shapescript attribute you created.  Open and verify you did it properly.

But I wouldn't, I'd extend the abstract metaclass.

[Glassboy]

The shape script is stored in the MDG in a base64 encoded and packed format. You need to decode the base64 which results in a zip data file. This can be unpacked using standard zip tools. The contents might be copyrighted by Sparx. I guess as long as you use it for your company internally it should not really be an issue. Asking Sparx wouldn't be the worst to do, I guess.

That's a torturous method when you can simply cut and paste the attribute.

[Paolo F Cantoni]

w00t I beat Paolo

[SNIP]

Not to rain on your parade, but you ARE a fair few hours ahead of me...     According to the site, your first post was at 4:04 am - when I was snug in bed.

From the west side of the West Island of New Zealand... 

Paolo

[Glassboy]

From the west side of the West Island of New Zealand... 

I'm aware of WAFL country :-)

[Geert Bellekens]

This page of the help explains it quite nicely

http://sparxsystems.com/enterprise_architect_user_guide/12.1/building_models/non-uml_metatypes.html

Geert