About Us
 
Newsletter March 2014
 
Dear users,

Entity Relationship Diagram (ERD) is widely used in database design and database management. ERD provides a visual representation of database, helping database designer and developer to understand the composition of a database easily without having to study the underlying schema.

Database design grows and evolves along with the system they serve. When the design grows larger, complexity may grow exponentially as more entities and relationships are added. As a result, ERD may become hard to understand and manage.


Although the growth of database design is hard to avoid, complexity can be kept under control. In this month we will share with you some ideas about how to deal with the complexity in database design, by drawing context based ERD.


Sincerely,
Visual Paradigm
ERD per context
ERD per context
By designing database with multiple context based ERDs, you will have a more clear understanding of your database structure, which can save a lot of time in database management as well as reduce potential chance of failure. We prepared a short video to show you how things work.
reuse entities between diagrams
Re-use entities between diagrams
It's pretty common for an entity or a set of entities to fall into multiple contexts, especially the look-up entities. The ability to re-use entities between diagrams enables you to keep your design compact, yet complete.
from ERD to data specification
From ERD to data specification
Produce data specification from your ERD, and send it to the developers for referencing when programming. You may read the tutorial From Data Modeling to Data Dictionary for details.

Entity Relationship Diagram is available in Visual Paradigm for UML Modeler Edition and Agilian Standard.