Technical Support
Have technical issues or suggestions? Please contact Visual Paradigm Support Team.
Sales Support
Have questions related to registration, licensing or payment? Feel free to contact Visual Paradigm Sales Team.
Entity relationship diagram (ERD) represents a detailed picture of the entities needed for a business. In forward engineering, ERD will be transformed into a relational database eventually. There are at least two types of ERD – Logical and Physical. They are used in different stages of development, and are inter-related.
Logical ERD models information gathered from business requirements. Entities and relationships modeled in such ERD are defined around the business's need. The need of satisfying the database design is not considered yet.
Physical ERD represents the actual design of database. It deals with conversion from logical design into a schema level design that will be transformed into relational database. When modeling a physical ERD, Logical ERD is treated as base, refinement occurs by defining primary keys, foreign keys and constraints. Sometimes, relationships need to be resolved by introducing additional tables, like a Linked table for a many to many relationship.
Since physical ERD and logical ERD represent the business requirement and database schema respectively, comparing physical and logical ERD helps to find out the differences between them in order to confirm the database is exactly following the initial business requirements regardless of the changes.
Two ERDs are compared: one for modeling the Logical Model and another one for modeling the Physical Model. With the features of Visual Diff, the differences between Logical and Physical ERD can be found easily.
| NOTE: | Alternatively, you can start Visual Diff as follows:
|
![]() |
| The Visual Diff dialog box |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description of various parts of Visual Diff dialog box |
![]() |
| Select Use Working Project |
![]() |
| Select a diagram |
![]() |
| Two diagrams are selected |
![]() |
| Select a strategy |
![]() |
| Select a compare |
![]() |
| Select a base |
![]() |
| Select a filter |
![]() |
| Select a node in the result pane |
| 2. Comparing as-is and to-be business process diagram | Table of Contents | Chapter 6. Using design pattern |
Technical Support
Have technical issues or suggestions? Please contact Visual Paradigm Support Team.
Sales Support
Have questions related to registration, licensing or payment? Feel free to contact Visual Paradigm Sales Team.