An
Presentation Topic
“ REALATIONAL DATABASE MANAGEMENT SYSTEM ”
For
Session:- 2025-26
Guided By:- Presented by:-
Saket verma
[Link] sahu
(Assistant professor) (BCA III Semester)
Columbia College of Science & Commerce
Affiliated to
[Link] Shukla University Raipur (C.G.)
ER Model (Entity-Relationship
Model) :
Definition :
The ER Model (Entity-Relationship Model) is a conceptual data model that shows how
data is connected to each other inside a database.
It was introduced by Peter Chen in 1976.
It helps database designers to visually represent
entities (objects), their attributes, and relationships
among them before building the actual database.
Entity :
An entity can be a real-world object, either animate or inanimate, that can be
easily identifiable.
For example, in a school database, students, teachers, classes, and courses
offered can be considered as entities.
All these entities have some attributes or properties that give them their identity.
An entity set is a collection of similar types of entities.
An entity set may contain entities with attribute sharing similar values.
Weak Entity :
A weak entity is an entity that depends on the existence of another entity.
In more technical terms it can defined as an
entity that cannot be identified by its own
attributes.
It uses a foreign key combined with its
attributed to form the primary key.
Strong Entity :
A strong entity is an entity that does not
depend on any other entity for its identification.
It has its own primary key that uniquely
identifies each record.
Attributes :
Entities are represented by means
of their properties, called attributes.
All attributes have values.
For example, a student entity may have
name, roll-no, and dob as attributes.
There exists a domain or range of
values that can be assigned to attributes.
Types of Attributes :
Simple attribute - Simple
attributes are atomic values, which
cannot be divided further.
For example, a student's phone
number is an atomic value of 10
digits.
Derived attribute - Derived attributes are the
attributes that do not exist in the physical
database, but their values are derived from other
attributes present in the database.
For example, Age from Date of Birth: Instead
of storing an employee's age, which needs
frequent updating, the system can calculate it
dynamically from their date of birth and the
current date.
Composite attribute - Composite attributes
are made of more than one simple attribute.
For example, a student's complete name may have
first_name and last_name.
Single-value attribute - A single-valued
attribute is a property that can only have one
value for a specific entity, such as a person's
age or gender, a student's roll number, or an
employee's Social Security Number.
For example - A product's price or a bank account's
number.
Multi-value attribute - Multi-value attributes may
contain more than one values.
For example, an attribute in "student " table
called " Interests " which can contain multiple
values of the student's interests.
Relationship :
The association among entities is called a
relationship.
For example, an employee works_at a department,
student enrolls in a course.
Here, Works_at and Enrolls are called relationships.
Relationships are represented by diamond shapes
and are labeled using verbs.
Degree of Relationship :
The number of participating entities in a relationship defines the
degree of the relationship.
o Binary = degree 2
o Ternary = degree 3
o n-ary = degree
Mapping Cardinalities :
Definition :
Cardinality defines the number of entities in one entity set, which can be
associated with the number of entities of other set via relationship set.
One-to-one - One entity from entity set
A can be associated with at most one entity
of entity set B and vice versa.
One-to-many - One entity from entity
set A can be associated with more than one
entities of entity set B however an entity
from entity set B, can be associated with at
most one entity.
Many-to-one - More than one entities
from entity set A canbe associated with at
most one entity of entity set B, however an
entity from entity set B can be associated
with more than one entity from entity set
A.
• Many-to-many - One entity from A can
be associated with more than one entity
from B and vice versa.
ER Diagram (Entity Relationship
Diagram) :
An ER Diagram is a visual
representation of data and how
different entities (objects) are
related to each other in a database.
An ER Diagram shows the structure
of a database using entities,
attributes, and relationships
between entities.
Conclusion :
The ER Model helps us understand and design a database [Link]
shows how different objects (entities) are related to each other using
a simple diagram.
By using entities, attributes, and relationships, we can clearly plan
how data will be stored before creating the actual database.