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
Your diagrams are not necessary to be modeled just with the standard notations. With the Diagram Image Shapes, you can enrich your diagram with customized image files. The Diagram Image Shapes can be created via the prattle of the diagram, as well as using Open API. This article will show you how to create Diagram Image Shapes from an image file deployed in your plugin using Open API. Read more
When your project is simple, you are able to express all of the design ideas with just a few diagrams. The diagrams are simple and self-explanatory. Each of them represents a distinct design idea and there is no overlapping between diagrams.
When you are dealing with a complex project, you may need to draw multiple diagrams to represent different contexts. You need to borrow shapes from a diagram to make them appear in other diagrams (i.e. contexts). In fact, this is extremely common when modeling with class diagram and business process diagram. Take UML class diagram as an example, there may be a domain diagram that presents all the entity classes and, another diagram that presents the associations and dependencies between a specific controller class and its related entity classes. So in this case, both diagrams contain the same set of entity classes.
Instead of re-creating those classes again and again in different diagrams, Visual Paradigm allows you to “re-use” them. Through simple copy and paste (Ctrl-C and Ctrl-V), you can easily copy a shape from one diagram to another. Each shape is formally known as a “view”. So with this, you can create multiple views for a model element in representing different contexts. Changes made on a shape are all synchronized to other instances that appear in other diagrams without extra effort. This is great, but there is a drawback though.
There are two common misunderstanding about use case modeling or UML use case diagram. One is that, use case diagram is too simple, as it does not explain anything important and it is not worth drawing. Another misunderstanding is just opposite to the first one. Some people believe that use case diagram is so powerful that can represent many different aspects of a software, from describing system requirements to modeling the internal behaviors of the system. So what is use case? What is use case diagram and is use case modeling simple or powerful?
Use case modeling is simply an answer to “What do the users (customers) want”. It allows you to visually represent the goals that users want to achieve through using the final end product, which can be a system, a software, a program, etc. Use case modeling is a useful technique in establishing a solid foundation for software developers to develop software system that meets with customers’ needs. While the notations applied in a use case diagram seem simple and do not express much detailed, the way how use cases are collected, organized and elaborated do significantly influence the direction of the software development lifecycle and thus the quality of the final software product. In this article, we will go through ten tips that can maximize the effect of drawing use case diagram. We are not going to explain what are use cases in detail but some of the key concepts regarding to UML modeling, use case diagram and requirements capturing will be covered.
In helping you organize your modeling project, use cases can act as generic containers for all software development artifacts. Development teams can group and locate design artifacts by navigating use cases.
In this tutorial we are going to show you how to create a new data model (i.e. entity relationship diagram) and associate that with a use case. And in future, you can easily identify existing associations as such by use cases and conveniently, be taken to the related diagrams right on the spot in just a few clicks.
When the default attributes do not suffice to describe your model elements, you can add your own custom ones by using tagged values. These custom attributes can be added to model elements in various diagrams, such as an actor in use case diagram.
So if you are looking at model elements in a diagram, just how do you show their tagged values? This tutorial will show you how.
As an example, we will walk you through how to show tagged values associated with devices in an ArchiMate diagram.