Logizian enables you to publish your project to the web. You can share your latest business process and system designs with your clients, team members and colleagues from other departments through the Project Publisher. All information about the project gets published, including the documentation, property details, internal references and external references of each diagram and model element.
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2010-05-04 10:28:092013-11-08 15:34:12Publish Your Business Process Using the Project Publisher
Properties or tags are used to keep information about use case and can be viewed in Use Case Details. In there, you will see a number of fields such as level, complexity and author that are provided by default. In VP-UML, if you need to store additional information in use case details, you can create custom fields to do that.
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2010-04-29 10:29:472013-11-08 15:34:16How to Add Custom Fields to Use Case Details?
Visual Diff is a feature providing visual comparison between diagrams. We can make use of Visual Diff to compare the structure of different databases. Assume we have 2 databases, Database1 and Database2. To compare different databases:
Using Object-Relational Mapping (ORM) approach is very popular in developing modern database applications. ORM allows you to handle relational data in a pure object-oriented approach, which is more natural to developers and also the modern programming language they are using (i.e. Java, .NET).
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2010-02-05 08:58:062013-11-08 15:34:24Comparison of Query Performance when Working with ORM
GUID (Global Unique Identifier) is a special type of identifier in Microsoft SQL Server, which commonly use for generate unique value for key columns. You can specify column as GUID through the Entity Relationship Diagram (ERD). The steps for specify GUID column is quite simple:
Specify MS SQL Server as default database server of the project
Specify the datatype of primary key column as uniqueidentifier
When working with a large, enterprise scale model that involves many diagrams and model element, we may find experience slowness in application, uneasy to model effectively in large diagram and difficult to locate model element. In this article, we will introduce some tips to help improve application performance, reduce time in modeling and diagramming, and to find elements easier.
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2009-12-18 16:02:192013-11-08 15:34:31Tips for Working with Large Projects
A cycle in software development or process improvement is often formed by many distinct phases. For example, one may hold a meeting with end user to collect the requirements. Next, s/he thinks of the room for improvement and then documents the new idea. Furthermore, s/he discusses with the user again and finally puts the idea into practice by providing a solution.
Throughout a cycle, visual modeling helps to express an idea and formalize changes. Different types of diagrams can be applied in accord with various situations. For example, business process diagram can be used to model the current process of an organization, and the improved one. Use case diagram can be used to model the features of a system at high level. Requirement diagram can be used to model user’s specific requirement. When a cycle evolves, the models will get evolved too. Take a look at the image below. The as-is process diagram is evolved into a to-be process diagram that illustrates the process to be applied in future, and the tasks in to-be process diagram are evolved into a use case in a use case diagram for modeling system level user goal. We can imagine when the model evolves in further, the use case can be transited into a set of requirement.
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2009-12-15 18:51:292013-11-08 15:34:35Transition and Navigation with Model Transitor
Gateways is a BPMN notation used to control how a process flows. Connected by sequence flows, a gateway acts as a decision point that decides which (outgoing) sequence flow to take based on the result of the evaluation of condition(s) specified. According to the Business Process Model and Notation (BPMN)’s definition, only sequence flow will affect the flow of activities while message flow does not. If you want to know message flow usage, please see How does BPMN message flow work? article. In this article, we will show you the different types of gateways and their behavior using the BPMN modeler featured by Visual Paradigm.
In this page, we will have an overview on how administrator and team members can work together with Visual Paradigm’s team collaborative features, and to clarify some of the major concepts in collaborative modeling.
/know-how_files/2017/12/vp_logo_header-1.png00Visual Paradigm Team/know-how_files/2017/12/vp_logo_header-1.pngVisual Paradigm Team2009-12-08 17:20:192016-09-08 13:50:23Overview of Team Collaboration Support
Business Process Model and Notation (BPMN) message flow is used to visualize communications between organization. This article is going to show how to use message flow. There are two flash animation examples to show how message flow works in action.