Sparx Systems Forum
Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: Sunshine on September 24, 2024, 05:31:51 am
-
Since 2008 we developed and updated our own ArchiMate MDG which defined stereotypes with shape scripts and tagged values, connectors, diagrams and toolboxes etc. When Sparx Enterprise Architect started to support ArchiMate some time later we changed our ArchiMate MDG to redefine ArchiMate elements so we could utilise the shape scripts. Our objective now is to just add tagged values the ArchiMate elements however, we are hitting a few sticking points and seeking advice from the forum members.
- We figured out if we redefine ArchiMate element we need to use the same stereotype name. For example OurArchiMate::ArchiMate_ApplicationComponent -- Redefine--> ArchiMate3::ArchiMate_ApplicationComponent. However, we can't figure out how we ensure that OurArchiMate::ArchiMate_ApplicationComponent is create with the tagged values from the ArchiMate diagram and toolbox. Looks like we have to create our own diagram type and associated toolbox. Is that correct or is there another way where we can utilise the ArchiMate3 diagrams and toolboxes already supplied to create our redefined ArchiMate elements with Sparx EA ArchiMate3 MDG?
- For usability purposes as we have a few elements with a number of tagged values we would like to group the tagged values using _tagGroups, _tagGroupings and _tagGroupStates however putting those attributes under the archimate element being redefined doesn't appear to work. For example adding those attributes to ArchiMate3::ArchiMate_ApplicationComponent. We did find that if we also extended Component meta class and add those _tagGroup, _tagGroupings and _tagGroupStates we do manage to group the tagged values in Sparx EA. Is that the correct way to do it?
-
1. If you've created the redefinition then you need to set your technology as active so that it's used when you try to create the original stereotype.
Specialize > Technologies > Manage Technology
2. Yes, those properties need to be added to a metaclass that is being extended. That's a little trickier when extending another profile but you've found the way to do it.
-
1. If you've created the redefinition then you need to set your technology as active so that it's used when you try to create the original stereotype.
Specialize > Technologies > Manage Technology
The problematic part about this is that this is an option stored in the personal settings.
Even worse, when the MDG is stored in a model, and you open up another model (that doesn't have this MDG) EA forgets the "Active technology" setting.
We solved that by executing a script on loading a model to set the active technology (in the registry)
Geert