User story is a very important component in capturing and managing requirements. In Visual Paradigm you can create and manage user stories in agile development (scrum) approach using UeXceler. The user stories you created in UeXceler is not just for requirement management purpose, they can also visualize on diagram to provide extra annotation to visual models. To put your user story into diagram: Read more
When you maintaining, or even creating a diagram very often you may want to change an existing element into another model type. Unlike most of the diagramming software where user need to manually create the new element and re-establish the connectors, with Visual Paradigm you can done it in few clicks. In this article we will show you how it works. Read more
Visual Paradigm support define guideline with necessary constraints for executing certain business operations into business rules. The business rules are not just defined as reference in the business process models, but also can be visualize in diagram. To visualize h the business rule in business process diagram: Read more
Visual Paradigm supported modeling with various notations, including the Unified Modeling Language (UML), System Modeling Language (SysML), Business Process Modeling Notation (BPMN), Entity Relationship Diagram (ERD), Data Flow Diagram (DFD), Organization Chart, etc… When creating diagrams very often you may want to cross reference the notations from other diagram type, or even from other notation standards. In Visual Paradigm you can do it easily by customizing the diagram toolbar. In this article we will show you how it works. Read more
Association is a very comment relationship between classifiers. The association is not a simple connector, it carry lots of information related to the relationships between classifiers. Those information may/may not presented on diagram, but they are vital to the definition of your models. In Visual Paradigm there are several ways to define the details for your association and in this article we will show you one by one. Read more
Visual Paradigm support wide range of databases for user to model the data structure of their systems. Once the data model is done you can generate persistent layer source code in Hibernate and use it as the out-of-the-box data access layer for building your database applications. All the data types which covered by Hibernate are directly supported by Visual Paradigm. But what if your model involved some domain specific data type which not covered by Hibernate? In this case you can make use of the User Type property to model it. To model with non-supported column types:
The Visual Paradigm Resource Centric interface is a handy feature for user to create diagrams without the need to memorize the syntax of the modeling language. It automatically filtered what you can do with the model element you working on in the diagram. In recent release Visual Paradigm enhanced the Resource Centric interface to become the Resource Catalog, which further boost the usability of the Resource Centric interface and make your diagraming task even easier. By default you will be switched to the Resource Catalog interface. But just in case you have missed the switch you can follow the details in this article to change the interface to Resource Catalog.
Entity Relationship Diagram (ERD) is a tool for model the structure of a database. It mainly consists of the entity (database tables) as well as the relationships between them. Unlike the traditional UML diagrams, the relationship in ERD not just indicate the entitles are related to each other, it also specifies which column(s) between the source and target entities are linked, which also known as the primary key and foreign key relationship. People often want to have the relationships stick to its associated columns. But instead of manually adjust the connection point for the relationship connector, Visual Paradigm can automatically do it for you.
Sometimes you may notices that the elements on diagram having a small “a” and “M” icon showing on its top left corner. What is this mean?
Method overriding is a very common technique in object-oriented programming. It allows developer deliver specific implementation of a method in the subclass although it already defined by the superclass. When overriding a method the subclass replace the implementation in superclass by providing a method which exactly same as the one in superclass, i.e same name, parameter and also the return type. In Visual Paradigm you don’t need to redefine the operation in subclass to model the override. You can simply do it in one click inside the specification dialog. To override the operation: Read more