Visual Paradigm’s Open API allows you to create all kind of our supported connectors in diagram. They are not necessary to be in simple straight line form. You can create complex connectors with multiple turning points just like those you created in diagram with your mouse. This article will teach you how to create connectors with turning points using Open API. Read more
Open API not only allows you access the model data within the project, but also creating new model elements and connector. This is not only for standard connectors such as association, but also relationships such as containment. This article will show you how to create containment relationship using Open API. Read more
Communication diagram is a kind of behavior diagram in Unified Modeling Language (UML) which helps in visualize the interactions within and between systems. The Communication diagram focus on how objects collaboration together in particular scenario. Instead of creating communication diagram manually, you can also create it programmatically using Open API in Visual Paradigm’s products.
Association is one of the key elements for constructing class model. It is not just a line relating 2 classes but also carrying lots of information describing their relationship. Giving a meaningful name to the association would help to make it easier to understand. Visual Paradigm allows you to show and hide the name of the association in a flexible way. Read more
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 UML (Unified Modeling Language), an association can be used to represent that two classifiers which are related with each other. On any binary association, you may optionally put a solid triangular arrowhead near the name of the association to define the way the association should be read. In this article, we will see how to show the triangular arrowhead on an association in Visual Paradigm.
Sometimes when you reopen your project and try to edit the diagram, you find that the shapes in your diagram are not resizable. This probably caused by you have turned on the auto-fit size option of your diagram. This could be caused by you accidentally turned on this option, or your other team member turned it on when they editing the same diagram in teamwork environment. By turn on this option, all the shapes in your diagram will be fitted its size automatically, thus, all the resize points around the shape will be disabled. 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