The Matrix Diagram in Visual Paradigm provides a macro view to show the relationships between model elements. This is not limited to model elements having the physical relationship connectors, but also for some more abstract relationships, such as containment, model transitions and even references. Read more
For every model element, there is a description property that allows you to describe detailed information about individual element, so that readers can understand the intended use, intended behavior and other important information. For example, specific implementation guideline can be written in a UML class or class diagram, and precautions can be written in a BPMN task in a business process diagram.
Sometimes, we may not have the information we need to enter in the description at the time the model element is being created. We may leave it first and enter it later on. But then the problem comes: After several days or weeks, how do I remember which shapes in a diagram has description missing? To check shape-by-shape is time-consuming…
In this article, we will show you how to indicate in diagram shapes that has description entered. This allows you to concentrate on shapes that have no description entered. Besides, it allows readers to check and read the description of shapes only when description has been entered which makes the diagram more legible.
When you copy and paste formatted text into a description editor in Visual Paradigm, it automatically brings along the formatting properties. This sounds reasonable and is quite a nice behavior if you really want to keep the style of text contents. However, there are several reasons why you might not want to keep the formatting. First, when you copy from web page, it may bring along crappy HTML contents, say the hidden table borders and layers. In fact, when CSS is widely used in most of the modern websites, what you copy from a webpage is not necessarily what you can get when pasting without the existence of the CSS. Second, you may not want to mix up the style of text in your description with the source. Third, although the crappy formatting properties may look invisible in the description editor, they may affect the content in generated documentations. After all, to clear those formatting tags is time consuming and error prone.
Account for the reasons above, it would be nice to have certain ways to paste text without including formatting properties, which means, to paste as plain text. In Visual Paradigm, the “Paste without formatting” function is provided to serve this purpose.
As your project grows, it is inevitable to have more and more orphans model elements left in your project. Such model elements are not visualized in any diagrams and are not useful anymore. This article will show you how to locate those elements so that you can remove them from your project. Read more
The find feature allows you to search for specific words or sentences within text in the description editor. Finding starts from the beginning of the description, regardless of the position of text cursor. The first occurrence of text that matches with the entered search text will be highlighted. You can move to the next occurrence by clicking on the Next button. You can perform finding in all the RTF description editors, such as the description editor in specification window.
When you are documenting your model, you may come across the situation where you want to make a reference to certain diagram in the project to help you explain an idea or to give reader supplementary information they may find useful. For example, you may want to add into the description of a class, a note to tell the developers that if they want to know more about the state change of the class, refer to certain state machine diagram. While the reference feature allows you to establish formal and contractual reference between model elements and diagrams, the reference function you can find within the description editor enables you to add diagram link into any part within a description, casually and informally. Such a diagram shortcut enables reader to jump from description to a diagram, which makes navigation much easier.
ID is a very useful property for a model elements. Having an unique ID for your model elements not just can ease the communication between your team but also help to structure your model in a more systematic way. Visual Paradigm can help you to generate unique ID for your model elements. Besides, you can apply customized patterns to the ID to accommodate your needs in different situations. In this article, we will show you how to configure the ID generator to generate customized ID for your model elements with Visual Paradigm. Read more
You may have a big project, with hundred, thousand, or even more model elements in it. When you are working primarily on a diagram and you want to know the model hierarchy of certain shape, a possible way would be to find out the model element in the Model Explorer and view the hierarchy there. But with so many model elements listed in Model Explorer, how do you effectively locate the model element you want? In this article, we will show you how.
The file reference feature provides a handy way for you to associate your design with whatever kind of external files, to aid in the explanation and studying of design. You can make a UML use case link to a set of requirement specification, make an entity in ERD link to a scanned copy of order form, make an activity in business process diagram link to a document of instruction, etc.
Knowing that different people may store the same files in different places, in order to make the referenced files accessible in any environment, one can define a user path to the folder where the files are stored. Users can replace the user path themselves to make the file reference accessible in their own environments. Read more
Visual Paradigm’s modeling tools are running in share model basis. This is meaning that a single model element can appear on different diagrams, or even on the same diagram multiple times (we call it the “views”). Changing the model element on one of the view will automatically reflected to other views. But sometimes you can may found that when you make changes on a new model element, changes also applied to other elements in your project, which is not what you looking for. There are 2 possibilities for this problem to be happen: Read more