MDG - How to extend ArchiMate 2.x ?

[eerhosi]

How to extend ArchiMate 2.x by creating profile with extended ArchiMate elements with some custom attributes / tagged values?
So is it possible to create an ArchiMate profile with Profile Helper?

I'm using version 11.0.1106

[KP]

To create a stereotype that extends an ArchiMate stereotype:

1. In your «profile» package, create a class.
2. Name it after the stereotype that you want to extend, including the profile in its name, e.g. "Archimate2::ArchiMate_BusinessActor".
3. Give it the stereotype «stereotype».
4. Make it abstract.
5. Create a Generalization from your stereotype class to this stereotype class.
6. (You may also need to add an Extension connector to a «metaclass» class).
7. Save profile, build MDG Technology etc etc

[cuninghamd]

I have followed the steps outlined in the answer. I get stuck by what you mean on step 5 & 6. could you please be more explicit in your instructions. alternatively (better)  can you attach a diagram containing what you mean please.

Many thanks.
Dave.

[Geert Bellekens]

Dave,

You can find an example in the manual: http://sparxsystems.com/enterprise_architect_user_guide/12.1/building_models/non-uml_metatypes.html

Geert

PS. Look like everyone here is somehow doing the same. Must be the fifth time this week I posted this exact link

[Glassboy]

Yup, UMLized Archimate leads to more UMLising.  Nobody asks the question "why exactly are we using Archimate".

[Paolo F Cantoni]

Yup, UMLized Archimate leads to more UMLising.  Nobody asks the question "why exactly are we using Archimate".

What do you mean by the term UMLising?  Extending ArchiMate is surely not the same as UMLising?

While many (perhaps your good self) may see ArchiMate as "plat du jour"; there is, nevertheless, a lot of good stuff there for creating better models of reality for use in making and revealing the consequences of architectural decisions.

Hopefully, if it is "flavour of the month"; "the baby won't get thrown out with the bath water".

Paolo

[Glassboy]

I think Archimate would have been better as a knowledge model and a set of style guidelines for stereotyped UML.  The Essential Project (http://www.enterprise-architecture.org/) has also done a better job at what Archimate set out to do.

The two main problems with Archimate are that it is essentially proprietary and the people developing it are the same people trying to make money out of it, and it represents computing from the eighties.

Plus it gets all squigly in the middle when you try and model anything complex.