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).
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
- Change the ID Generator of the primary key column as GUID
The following flash movie demonstrate how to specify the primary key column as GUID.
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.
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.
Gateways are used to control how the process flows. In Business Process Model and Notation (BPMN) definition, only sequence flow will affect the flow of work and message flow should not affect the flow of work. If you want to know message flow usage, please see How does BPMN message flow work? article. Gateways can only be connected by sequence flow only. This article will show different type of gateways and their behavior with Business Process Animacian.
|Team collaboration development on CVS, SVN, Perforce and ClearCase had been discontinued starting from Visual Paradigm version 13.0|
Visual Paradigm supports collaborative and concurrent modeling, and versioning of works in the following ways:
- Visual Paradigm Teamwork Server (A native product developed 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.