Scribd
Upload
27 views23 pages

DBS Part 3

Uploaded by

shaniii7426
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
27 views23 pages

DBS Part 3

Uploaded by

shaniii7426
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 23

Database Design

You
don
’t c
ons
tru
ct hou
se s
wit
hou
t de
sign
…
ER model
ER model stands for an Entity-Relationship model. It is a high-level data model.
This model is used to define the data elements and relationship for a specified
system.
• It develops a conceptual design for the database. It also develops a very
simple and easy to design view of data.
• In ER modeling, the database structure is portrayed as a diagram called an
entity-relationship diagram.
• Uses:
• Databases
• Reports
• Projects
ER model..
For example, Suppose 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,
etc and there will be a relationship between them.
Component of ER Diagram
Entity:
• An entity may be any object, 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.
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
Attribute
• The attribute is used to describe the property of an entity. Ellipse is used to
represent an attribute.
• For example, id, age, contact number, name, etc. can be attributes of a
student.
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.
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.
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.
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 over time and can be derived from
another attribute like Date of birth.
Relationship
• A relationship is used to describe the relation between entities. Diamond or
rhombus is used to represent the relationship.
One-to-One Relationship
• When only one instance of an entity is associated with the relationship, then
it is known as one to one relationship.
• For example, One Person has one passport and a passport may have one
owner.
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.
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.
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.
E-R Diagrams - Chen’s
notation

Entity–relationship modeling was developed for database


and design by Peter Chen and published in 1976
E-R Diagrams - Chen’s notation
• Entity Set • Attribute

• Weak Entity Set • Example


E-R Diagrams - Chen’s notation
• Key • Drived Attribute

• Multivalued Attribute
E-R Diagrams - Chen’s notation
• Composite Attribute
E-R Diagrams - Chen’s notation – Relationship
• Strong Relationship

• Weak (identifying) Relationship


E-R Diagrams - Chen’s notation – Relationship
• Cardinality
• one-to-one (1:1)

• one-to-many (1:N)

• many-to-many (M:N)
E-R Diagrams - Chen’s notation – Relationship
• Participation

• Total

• Partial

You might also like