Eliminating an inherited connection metamodel when specializing an MDG

[adepreter]

Hello, Does anyone know how to eliminate inherited connection metamodels?

Context: In a custom MDG, we redefine most stereotypes that exist in another MDG.

Question: How to avoid that the redefined element stereotypes inherit the related connections metamodel ?

For example:
- In the ArchiMate MDG, there is a built-in Assignment meta-connection from Application Component to Application Function.
- In a custom MDG that redefines Application Component and Application Function, how to AVOID that the Assignment (and all other meta-connections) gets inherited ?

[Eve]

I think the only option is to override each allowed relationship.

[Geert Bellekens]

For some client's I've completely rebuilt the ArchiMate profile to suit their specific needs.

That is a bit of work, but it allows full control of which relations are allowed or not.

Geert

[adepreter]

Thank you.
Indeed full control is always better.
Is the Sparx version of the ArchiMate MDG QEA available to boost partners' productivity and Sparx sales ?

[Sunshine]

Whilst not the Sparx EA version of archimate MDG I did create an externded version of the archimate MDG to add tagged values. You can find it here as EAMDGProfile.zip - Full EA Model and files, icons etc to create a ArchiMate MDG from
https://github.com/EASunshine/Sparx-EA
Instructions built into model how to build.
Might help get you started.