Introduction - If you have any usage issues, please Google them yourself
One of the most misinterpreted terms in the software industry is actually one we know very well: entity relationship (ER).
That’s because we often lack a common definition that is understood by all members of the development team. We assume
that everyone on the team shares the same clear understanding of the methodology, syntax, and mechanics associated with
ER and ER modeling.
ER modeling itself defines the methodology used in the analysis and design of information-based systems. Database
designers often use this methodology to gather requirements and define the architecture of the database systems. The output
of this methodology is a list of entity types, relationship types, and constraints.