Extending a technology other than UML via a MDG

[Glassboy]

Hi is it possible to extend a technology other than UML via a MDG.

Specifically can you extend or generalise Archimate 2?

e.g. ArchimatePlus::Archimate_Risk(Archimate2::ArchiMate_Driver)

Or do you basically have to copy Archimate 2 Drivers extension of UML and its shapescript?

[Glassboy]

And supplementary question, how to you create a profile like Archimate 2 and UPCC which doesn't appear to extend basic UML?

[KP]

Hi is it possible to extend a technology other than UML via a MDG.

Specifically can you extend or generalise Archimate 2?

e.g. ArchimatePlus::Archimate_Risk(Archimate2::ArchiMate_Driver)

Or do you basically have to copy Archimate 2 Drivers extension of UML and its shapescript?

You will need to create an abstract «stereotype» element in your profile named "Archimate2::ArchiMate_Driver" and create a Generalization to it from your own «stereotype» element. Your own «stereotype» element will have an Extends connector to «metaclass»Class (which is what Driver extends, according to our profile).

And in your toolbox profile, you will need an attribute named "ArchimatePlus::Archimate_Risk(UML::Class)"

[KP]

And supplementary question, how to you create a profile like Archimate 2 and UPCC which doesn't appear to extend basic UML?

Essentially, you must extend UML or EA won't understand, so choose the closest UML metaclass to the concept you're modeling and extend that. (Who said it would be easy?)

[Glassboy]

And supplementary question, how to you create a profile like Archimate 2 and UPCC which doesn't appear to extend basic UML?

Essentially, you must extend UML or EA won't understand, so choose the closest UML metaclass to the concept you're modeling and extend that. (Who said it would be easy?)

Those two technologies based on their files in C:\Program Files (x86)\Sparx Systems\EA\MDGTechnologies\ are noticeably different.  The UML element isn't in the toolbox sections.

Which is why I was wondering.  

[KP]

The UML element isn't in the toolbox sections.

If a stereotype only extends one metaclass, the toolbox can work out what it needs to create, so adding the UML extension to the toolbox definition is optional. The advantage of adding it is that if the stereotype is changed at a later date to extend further metaclasses, the toolbox will still work.

[Glassboy]

Thanks for that.  I just quickly whipped up the suggested implementation of the ISSRM domain model in Archimate from the Open Group white paper "Modeling Enterprise Risk Management and Security with the ArchiMate Language".

Now to compare it with implementing the domain model as straight extended UML.

[Glassboy]

Here's the MDG if anyone is interested https://onedrive.live.com/redir?resid=D323B9F737BF685E!18705&authkey=!AE6b76Bo28Az4zM&ithint=file%2cxml