Tailoring and Deploying a Sparx Enterprise Architect Configuration
How can we make sure that our user community gets the right Enterprise Architect configuration? How can we automatically configure their user experience so that it is adapted to our company-standard modeling language (MDG)?
You will find in this document a set of guidelines and examples for tailoring and deploying a Sparx Enterprise Architect configuration.
Out of the box, Sparx is optimized for UML modelers. So, if people in your organization need to model with another language than UML, then you might need to adapt the Enterprise Architect user’s experience and modeling constraints. The following guidelines will help you configuring this either manually or automatically.
Target audience of these guidelines
- The community of modelers working at higher levels of abstraction than UML, for example users of the Labnaf, Archimate or BPMN modeling languages. The default Enterprise Architect configuration does not always bring the required user’s experience.
- Sparx MDG (Model-Driven Generation) and add-in developers who created their own modeling language and who want to deploy their Enterprise Architect extension on end users’ computers.