![]() ![]() In the diagram, select the elements that you no longer want to include in the layer. Click on the icon again to restore all elements to full display. With a layer checkbox selected, click on this icon to fade all elements NOT in the layer, leaving the selected layer displayed in clear. If you select the checkbox, those elements are shown again. If you now clear the layer checkbox, the elements assigned to it are hidden on the diagram. The icon is enabled when the elements and layer are selected. Then click on the name of the layer, and on this icon. On the diagram, select the element or elements to show or hide using a layer. You now select elements to add to the new layer. If you clear the checkbox the layer is not active and the elements within it are not shown. The checkbox is selected so that the elements in the layer are shown on the diagram. Overtype the text with whatever name you want to apply to this layer of elements. Simply click on this icon to display a selected checkbox and the text 'Layer n'. Diagram legends can also be used in conjunction with both Layers and Filters to assist in improving the narrative of the diagram. ![]() ![]() Advanced modelers might want to use Layers and Filters together to create powerful visualizations of the underlying diagrams, remembering that the definitions of Filters apply at the level of the repository but their usage and application with Layers apply to a user's view of a diagram. Layers, on the other hand, are intentionally defined on and for a specific diagram and cannot be applied to other diagrams. So, for example, a Filter that hides all elements except critical requirements can work on a business level diagram in Project A and a technical level diagram in Project B. Layers can be used to separate elements in architecture diagrams to show strategic, tactical or implementation intent, or to show particular sequences of activations in a Sequence diagram, or to show a time-ordered sequence in a Business Process model, and much more.Īn important difference between Filters and Layers is that Filters are defined at a meta-level and so can be applied to any diagram in the repository. Filters are applied using element metadata such as status or complexity, whereas Layers are applied using any ad hoc criterion for the separation of the elements for example, items to be focused on in a workshop or elements of a particular architectural style. Diagram Layers will be a welcomed tool for people who need to present complex models to an audience, creating an easy-to-understand narrative built up in stages rather than confusing the audience with the complete diagram from the start.ĭiagram Layers - like the related Diagram Filters - can be used to hide or expose parts of any diagram. The tool also has the ability to bring a selected layer to the foreground while showing the other layers with reduced opacity. The tool has the added flexibility of being able to selectively apply any subset of the layers, which can't, of course, be done with the encyclopedia transparencies. The analogous process with Enterprise Architect's Diagram Layers is to reveal parts of any diagram including Business Process Models, Architecture diagrams, Kanban or Roadmap diagrams. The layers can be compared to transparencies laid on top of one another in a stack, as in paper-based encyclopedias where, for example, a base image of a human skeleton would have a transparent sheet showing the arteries laid on top, then one for veins and another for nerves. Diagram Layers provide a way of creating and viewing segments of a diagram to represent any concept that is the basis for separating or grouping the elements on that diagram.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |