A diagram is a two-dimensional geometric symbolic representation of information according to some visualization technique.


An entity-relationship model (ERM) is an abstract and conceptual representation of data, information aspects of a business domain or its process requirements

Parallel models data


"Entity-relationship modeling is very parallel to object modeling except that object modeling models behavior as well as data and entity-relationship modeling only models data;the problem with learning entity-relationship modeling for this purpose is that in the present state of affairs most of the professionals who use entity-relationship diagram do not use them to depict a conceptual model"

from question  

One-to-many relationship between same entity in Core Data

"Unlike most people i prefer to make a sharp distinction between diagram that depict an entity-relationship model and ones that depict a relational model;contrary to prevailing opinion entity-relationship modeling isn t just relational lite"

from question  

What are the symbols for specializations and generalizations etc. in crow foot notation



First entity-relationship modeling is more than just an erd;we tend to try to put the entire entity-relationship model on one diagram

from question  

Why is a specific cardinality not allowed in the ERD?

An entity-relationship diagram is more abstract;sql server let you create a physical data model diagram that could come from a entity-relationship diagram or not

from question  

Is database diagram in SQL Server Management Studio considered as ER diagram?

Another article s the only conceptual modeling tool available for relational data the others - erwin and another article ilk - being at best logical modeling tools with nothing much better than entity-relationship diagram and ddl synchrnoization which are also provided by object role modeling tools

from question  

* (no title is found for this review)

Entity-relationship diagram aren t a good fit for document databases;the entity-relationship model supports many-to-many binary as well as ternary and higher relationships composite keys and attributes on relationships all of which aren t directly supported in hierarchical network model dbmss

from question  

Why we don't draw ER for NoSQL databses

Oo class diagram is more abstract and has more features than entity-relationship diagram

from question  

Is there any relationship with ER and class diagram?

Back to Home
Data comes from Stack Exchange with CC-BY-SA-4.0