Lecture 5 ER Diagram in DBMS
Lecture 5 ER Diagram in DBMS
DBMS
(with Example)
WHAT IS THE ER MODEL?
The ER or (Entity Relational Model) is a high-level conceptual data model diagram. Entity-
Relation model is based on the notion of real-world entities and the relationship between them.
ER modeling helps you to analyze data requirements systematically to produce a well-
designed database. So, it is considered a best practice to complete ER modeling before
implementing your database.
IN THIS TUTORIAL, YOU WILL
LEARN-
What is the ER Model?
History of ER models
What is ER Diagrams?
Why use ER Diagrams?
Components of ER Diagram
Relationship
Weak Entities
Attributes
Cardinality
ER- Diagram Notations
Steps to Create an ERD
Best Practices for Developing Effective ER Diagrams
HISTORY OF ER MODELS
ER diagrams are a visual tool which is helpful to represent the ER model. It was proposed by
Peter Chen in 1971 to create a uniform convention which can be used for relational database
and network. He aimed to use an ER model as a conceptual modeling approach.
WHAT IS ER DIAGRAMS?
Entity relationship diagram displays the relationships of entity set stored in a database. In other
words, we can say that ER diagrams help you to explain the logical structure of databases. At
first look, an ER diagram looks very similar to the flowchart. However, ER Diagram includes
many specialized symbols, and its meanings make this model unique.
Sample ER Diagram
FACTS ABOUT ER DIAGRAM
MODEL:
ER model allows you to draw Database Design
It is an easy to use graphical tool for modeling data
Widely used in Database Design
It is a GUI representation of the logical structure of a Database
It helps you to identifies the entities which exist in a system and the relationships between
those entities
WHY USE ER DIAGRAMS?
Here, are prime reasons for using the ER Diagram
Helps you to define terms related to entity relationship modeling
Provide a preview of how all your tables should connect, what fields are going to be on each table
Helps to describe entities, attributes, relationships
ER diagrams are translatable into relational tables which allows you to build databases quickly
ER diagrams can be used by database designers as a blueprint for implementing data in specific
software applications
The database designer gains a better understanding of the information to be contained in the
database with the help of ERP diagram
ERD is allowed you to communicate with the logical structure of the database to users
COMPONENTS OF THE ER
DIAGRAM
This model is based on three basic concepts:
Entities
Attributes
Relationships
Example
For example, in a University database, we might have entities for Students, Courses, and Lecturers.
Students entity can have attributes like Rollno, Name, and DeptID. They might have relationships
with Courses and Lecturers.
WHAT IS ENTITY?
A real-world thing either living or non-living that is easily recognizable and nonrecognizable. It is
anything in the enterprise that is to be represented in our database. It may be a physical thing or simply a
fact about the enterprise or an event that happens in the real world.
An entity can be place, person, object, event or a concept, which stores data in the database. The
characteristics of entities are must have an attribute, and a unique key. Every entity is made up of some
'attributes' which represent that entity.
Examples of entities:
Person: Employee, Student, Patient
Place: Store, Building
Object: Machine, product, and Car
Event: Sale, Registration, Renewal
Concept: Account, Course
NOTATION OF AN ENTITY
Entity set:
Student
An entity set is a group of similar kind of entities. It may contain entities with attribute sharing
similar values. Entities are represented by their properties, which also called attributes. All
attributes have their separate values. For example, a student entity may have a name, age,
class, as attributes.
EXAMPLE OF ENTITIES:
A university may have some departments. All these departments employ various lecturers and
Some courses make up each program. Students register in a particular program and enroll in
various courses. A lecturer from the specific department takes each course, and each lecturer
teaches a various group of students. offer several programs.
RELATIONSHIP
Relationship is nothing but an association among two or more entities. E.g., Tom works in the
Chemistry department.
Entities take part in relationships. We can often identify relationships with verbs or verb
phrases.
FOR EXAMPLE:
You are attending this lecture
I am giving the lecture
Just loke entities, we can classify relationships according to relationship-types:
A student attends a lecture
A lecturer is giving a lecture.
WEAK ENTITIES
A weak entity is a type of entity which doesn't have its key attribute. It can be identified
uniquely by considering the primary key of another entity. For that, weak entity sets need to
have participation.
In the ER diagram the relationship between two strong The relationship between one strong and a weak entity
entity set shown by using a diamond symbol. set shown by using the double diamond symbol.
The connecting line of the strong entity set with the The line connecting the weak entity set for identifying
relationship is single. relationship is double.
ATTRIBUTES
It is a single-valued property of either an entity-type or a relationship-type.
For example, a lecture might have attributes: time, date, duration, place, etc.
An attribute is represented by an Ellipse
Types of Attributes Description
Simple attribute Simple attributes can't be divided any further. For example, a student's
contact number. It is also called an atomic value.
Composite attribute It is possible to break down composite attribute. For example, a student's
full name may be further divided into first name, second name, and last
name.
Derived attribute This type of attribute does not include in the physical database. However,
their values are derived from other attributes present in the database. For
example, age should not be stored directly. Instead, it should be derived
from the DOB of that employee.
Multivalued attribute Multivalued attributes can have more than one values. For example, a
student can have more than one mobile number, email address, etc.
CARDINALITY
Defines the numerical attributes of the relationship between
two entities or entity sets.
Different types of cardinal relationships are:
One-to-One Relationships
One-to-Many Relationships
May to One Relationships
Many-to-Many Relationships
1.ONE-TO-ONE:
One entity from entity set X can be associated with at most one entity of entity set Y and vice
versa.
Example: One student can register for numerous courses. However, all those courses have a
single line back to that one student.
2.ONE-TO-MANY:
One entity from entity set X can be associated with multiple entities of entity set Y, but an
entity from entity set Y can be associated with at least one entity.
For example, one class is consisting of multiple students.
3. MANY TO ONE
More than one entity from entity set X can be associated with at most one entity of entity set
Y. However, an entity from entity set X may or may not be associated with more than one
entity from entity set X.
For example, many students belong to the same class.
4. MANY TO MANY:
One entity from X can be associated with more than one entity from Y and vice versa.
For example, Students as a group are associated with multiple faculty members, and faculty
members can be associated with multiple students.
ER- DIAGRAM NOTATIONS
ER- Diagram is a visual representation of data that describe how data is related to each other.
Rectangles: This symbol represent entity types
Ellipses : Symbol represent attributes
Diamonds: This symbol represents relationship types
Lines: It links attributes to entity types and entity types with other relationship types
Primary key: attributes are underlined
Double Ellipses: Represent multi-valued attributes
STEPS TO CREATE AN ERD
Following are the steps to create an ERD.