When creating a class diagram, sometimes we would draw it using the diagram toolbar and there are times we would reuse elements by drag & drop. However, when you start from scratch, sometimes it can be difficult to know which class goes with which because we may not necessarily know all relationships among them.
When one shape is nested inside another, such as sub-process, its content (shapes) inside would show along with what’s outside in diagram at the same time. For example, if a sub-process is not composed of any other sub-processes, it will appear in business process diagram, with the shapes (e.g. tasks) that make it up inside itself. However, the viewing works up to one level of nesting only by default.
In an ideal world of system design, we’d probably want to create a generic library to store common components for reuse. That way, we can avoid creating the same components over and over again. Also, any changes you need to make to a component will automatically be rippled down to all projects which point to the same generic library.
A template enables you to retrieve and display information about your model elements. You can use a documentation template to generate documentation on different model elements of the same type. By creating a documentation template, you can also customize the content and presentation of your documentation of specific model element type.
Visual Paradigm considers that showing the html content in preview shape, to a large extent, is one of the reasons of slowing down the operation of an application. The preview shapes in all VP products, therefore, don’t show the html content by default. For the sake of users, VP products enable users to change this setting in their current workspace. This article will demonstrate how to render the html content of a note in an Overview Diagram.
A class diagram shows a set of classes, interfaces and their relationships and illustrates the static design view of a system, while a sequence diagram shows the sequence of actions that occurs in a system and illustrates the dynamic view of a system. Within VP products (e.g. VP-UML and Agilian, etc.), you can easily share the models between class diagram and sequence diagram. The changes that made in the sequence diagram can be automatically added to the class diagram as well and vice versa.
Mouse gesture is one of the most useful visual modeling tools in all our VP products. It helps you to draw and manage your diagram with just a click of your mouse. Mouse gesture are mainly divided into three types: the drawing gesture, the command gesture and the connection gesture. This article will give a brief introduction of these three types of mouse gesture and another 11 basic gestures, and then show how to apply these three types of mouse gesture on the diagram.
All the model elements in most diagrams are blue by default. In some cases, you may want to distinguish a specific model element, for instance, a note from others by setting a default color for it. In this article, we will demonstrate how to specify default fill color for a note in UML class diagram.