Entity-Relationship Model (ER Model)
ER model is a high-level view of database. This model was designed by Peter Chen and published in 1976 papers. It is the logical representation of data as objects and relationships among them.
Using this model, we represent the real-world problem in the pictorial form to make it easy for the stakeholders, developers to understand by just looking at the ER diagram. ER diagram as a visual tool to represent an ER Model. ER diagram has the following three components:
Entities: Entity is a real-world thing. Entity can be a person, place, or even a concept. Example: Teachers, Students, Course, Building, Department, etc. are some of the entities of a Student Management System.
Attributes: An entity contains a real-world property called attribute. This is the characteristics of that entity. Example: The entity student has the property like student id, name , registration date, department etc.
Relationship: Relationship tells how two attributes are related. Example: student admitted into a department.

In the above diagram, the entities are Student, Program and Department. Entities student and department are connected using the relationship. Hence student and program, department and program are connected. Here, each sudent admitted into a department, each dudent admitted into a program and each program are running under a department.
Features of ER Model
Advantages of ER Model
Disadvatages of ER Model
No industry standard for notation: There is no industry standard for developing an ER model. So one developer might use notations which are not understood by other developers.
Hidden information: Some information might be lost or hidden in the ER model. As it is a high-level view so there are chances that some details of information might be hidden.
Statlearner
Statlearner