Now included is an extremely powerful and flexible Views system based on both system defined and user defined meta-models. The Views system is intended to provide highly focused diagrams that limit the number of elements and connections available to the minimum required to achieve a specific task. For example, a Hierarchy View imposed on a Class diagram may limit the only element available to Class and the only connector to Inheritance.
Build tight and purposeful diagrams
By using the Views system to guide the modeling palette and relationships available, the modeler is ensured of building tight and purposeful diagrams that use only the required elements within the current modeling context. Cutting out the noise and reducing the set of constructs available is a great way of making sure a design is addressing the intended purpose and avoiding extraneous elements that may negatively impact the readability and correctness of the model.
- Reduces the noise and only presents conformant elements and relationships to be applied
- You can extend an existing metamodel or crate your own
- Diagram toolbox items are automatically restricted to the underlying meta-model
- Quick Linker menu items are narrowed to ensure you choose a valid and conformant connector
Accurate, fit for purpose diagrams
In addition to limiting the available palette, the View system also allows the modeler to enable a diagram filter that will gray out any elements that are not part of the current view set. This allows the modeler to correct any parts of their model that don't meet the purpose of the selected View, or to filter out elements that are required to be there, but do not form part of the current modeling goal.
View based UI and Toolboxes
The diagram properties dialog now includes a new drop list of available Views for the currently selected diagram type. Selecting one of these Views will reduce the palette of constructs available and limit the entries in the Quicklinker. Modelers can easily activate a View or even remove one if necessary - the actual model content will not change.
There are a number of different Views that offer different palette sets and focus goals for diagrams types such as UML, SysML, BPMN, UAF and others. If you have the goal of modeling a simple activity diagram with no advanced features, the Simple Activity View under the UML Activity Diagram section may be a better option than using the full Activity Diagram set.
Wide range of built in meta model Views.
Enterprise Architect version 14 comes with a wide range of built in meta model Views that address numerous modeling scenarios and domains. Many of the Model Wizard patterns come pre-set with a meta model View and the new Diagram dialog includes many derivative diagram views that extend and refine the capabilities of the base diagram types.
Build your own.
In addition to the system defined meta-model based views that Sparx distribute with Enterprise Architect 14, it is also possible for the modeler to create their own meta models and easily add them to the current model, where they or other modelers may then apply them to various diagrams as needed. For example, you may define a specific meta-model set that addresses the needs of Requirements modeling in your organization and then mandate that all Requirements diagrams use that Metamodel View.