Faculty Of Computer Science

Database Concept

Lecturer: Lutfullah Haqnesar

ER Modeling
 Agenda
 Data Modeling
 ER Model
 Component of ER Model
 Entity
 Attribute
 Relationship
 Reduction of ER diagram to Table
 Data Modeling

• Data Modeling provides the conceptual tools for describing the design
of a database at each level.

• Data Model is the modeling of the data description, data semantics, and
consistency of the data.
 ER Model

• ER model stands for an Entity-Relationship model.

• ER model is used to define the data elements and relationship for a

• In ER modeling, the database structure is displayed as a diagram called an

For example:
• We design a school database. In this
database, the student will be an entity
with attributes like address, name, id,
age, etc.
• The address can be another entity with
attributes like city, street name, pin code
and etc, and there will be a relationship
between them.
Component of ER diagram
 Component of ER diagram

1. Entity:
• An entity may be any object, class, person or place. In the ER diagram,
an entity can be represented as rectangles.
• Consider an organization as an example- manager, product, employee,
department etc. can be taken as an entity.
 Component of ER diagram

a. Weak Entity

• An entity that depends on another entity called a weak entity. The weak
entity doesn't contain any key attribute of its own. The weak entity is
represented by a double rectangle.
 Component of ER diagram

2. Attribute
• The attribute is used to describe the property of an entity. Eclipse is used
to represent an attribute.
• For example, id, age, contact number, name, etc. can be attributes of a
student.
 Component of ER diagram

a. Key Attribute
• The key attribute is used to represent the main characteristics of an
entity. It represents a primary key. The key attribute is represented by an
ellipse with the text underlined.
 Component of ER diagram

b. Composite Attribute
• An attribute that composed of many other attributes is known as a
composite attribute.
• The composite attribute is represented by an ellipse, and those ellipses are
connected with an ellipse.
 Component of ER diagram

c. Multivalued Attribute
• An attribute can have more than one value. These attributes are known as a
multivalued attribute. The double oval is used to represent multivalued
attribute.
• For example, a student can have more than one phone number.
 Component of ER diagram
d. Derived Attribute
• An attribute that can be derived from other attribute is known as a
derived attribute. It can be represented by a dashed ellipse.
• For example, A person's age changes can be derived from another attribute
like Date of birth.
 Component of ER diagram

3. Relationship:
• A relationship is used to describe the relation between entities. Diamond
is used to represent the relationship.
Types of relationship are as follows:
1. One-to-One Relationship
2. One-to-many relationship
3. Many-to-one relationship
4. Many-to-many relationship
 Component of ER diagram

1. One-to-One Relationship

• When only one instance of an entity is associated with the relationship,

• For example, A female can marry to one male, and a male can marry to
one female.
 Component of ER diagram
2. One-to-many relationship
• When only one instance of the entity on the left, and more than one
instance of an entity on the right associates with the relationship then
this is known as a one-to-many relationship.
• For example, Scientist can invent many inventions, but the invention is
done by the only specific scientist.
 Component of ER diagram

3. Many-to-one relationship
• When more than one instance of the entity on the left, and only one
instance of an entity on the right associates with the relationship then it is
known as a many-to-one relationship.
• For example, Student enrolls for only one course, but a course can have
many students.
 Component of ER diagram

4. Many-to-many relationship
• When more than one instance of the entity on the left, and more than
one instance of an entity on the right associates with the relationship then
it is known as a many-to-many relationship.
• For example, Employee can assign by many projects and project can
have many employees.
 Reduction of ER diagram to Table

• The database can be represented using the notations, and these notations
can be reduced to a collection of tables.

• In the database, every entity set or relationship set can be represented in

• The ER diagram is given below:

There are some points for converting the ER diagram to the table:
Entity type becomes a table.

All single-valued attribute becomes a column for the table.

A key attribute of the entity type represented by the primary key.

The multivalued attribute is represented by a separate table.

Composite attribute represented by components.

Derived attributes are not considered in the table.