Users can create UML class with template parameter to form the template class. With Visual Paradigm for UML 8.0 (VP-UML), you can add and remove template parameters. In this page, you can learn how to add template parameter to class and how to remove it from class in class diagram.
A pin in an UML activity diagram is used to provide values to actions and accept result from them. In this article, you can learn how to create an exception pin from an output pin which is responsible for keeping the output values produced by an action.
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.
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.
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 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.
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.
Read more
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 use case diagram, associations between actors and use cases are explicitly shown. We can see it clearly when an actor carries out a use case (or goal) from a line drawn between them. However, what if an actor does not carry out a use case but do refer to the output from it? How do we model that?
To pass a message between two sequence diagrams in UML modeling, we can make use of gates. Through modeling gates, we could relate the message outside an interaction fragment with message inside another interaction fragment.
Graphically a gate, with an arrowed line, connects to the sequence diagram’s frame edge with one end and the other end connected to a lifeline.
In this tutorial we will show you how to model gates in sequence diagrams using Visual Paradigm for UML (VP-UML).
