Step by step to a tailored UI for Enterprise Architect

Making Modelling Simpler

There are lots of ways you can help:

1. By creating a cut down version of the properties UI for each element you are using
2. By adding customized help links
3. By giving modellers drop down lists of permitted field values
4. By prompting with re-usable assets
5. Guiding modellers with permitted diagram and connector types
6. And even generating your own MDG toolboxes

All these can be applied on a package by package basis. Which means they can be made available just in those places where extra help is needed, or a set of bespoke standards can be applied across your whole model.

Here's how...

1. Firstly, create a Reference model that illustrates the standards you want your modellers to follow. This contains the permitted element and connector types, and the diagram types that are allowed.
2. If the Reference model isn’t 100% right, you can customize it by adding or deleting element types that are allowed, and, for each element type, editing the connector types, direction and multiplicity that can be (or must be) connected.
3. PS You can also add Help text or a URL linked to your training resources, that will pop-up when users start modelling.
4. Then create the customized UI for each element in your Reference model.
5. Find your Reference Model in the Specialize > Model Expert> Reference models list – accessed from the top EA menu.
6. Expand the model, and choose an Element type to edit. The attributes tab lets you select just the attributes you want to display in the tailored properties window. Specify
   1. if the attribute is required or optional,
   2. allowed values
   3. the order of fields
7. Through this menu you can also edit the diagram types and content allowed, which will be used to guide or correct modellers if they try to create something that isn’t in accordance with the Reference model.
8. The final step is to apply the Reference model and these changes to a package – the one where your modeller will be adding their content. To do this, make the package managed.
9. For each managed package, you can specify the location in your model of content that must be re-used – e.g. stakeholder actors, or common requirements – to stop your modellers creating their own duplicate versions. These locations are defined for each managed package, so each Reference Model can be applied to a range of different packages.
10. Each managed package is set up to apply the Reference model rules in either strict or relaxed mode. Strict = only content that follows the rules will be allowed; Relaxed = advice will be given, but the modeller can ignore it.
11. Finally you can also save your Reference model as an MDG – so your users will get a toolbox containing just the elements and connector types they are allowed to add to this package.