Scribd
Upload
15 views

03 DBMS Lab

The document discusses entity relationship diagrams (ERDs), including their components like entities, attributes, relationships, and cardinality. It explains how to construct an ERD by identifying entities and relationships between them.

Uploaded by

GANESH RAJESHWAR CHINTALWAR
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
15 views

03 DBMS Lab

The document discusses entity relationship diagrams (ERDs), including their components like entities, attributes, relationships, and cardinality. It explains how to construct an ERD by identifying entities and relationships between them.

Uploaded by

GANESH RAJESHWAR CHINTALWAR
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

DBMS Lab

12 / 11 / 2021
Definitions

• Data • Primary – Key

• Information • Foreign – Key

• System • Relationship(s)

• Database – 1 to 1

• Table – 1 to Many
ER Diagram

• Entity Relationship Diagram


– An entity relationship diagram (ERD) shows the
relationships of entity sets stored in a database.

– An ER diagram is a means of visualizing how the


information a system produces is related. 
ER Diagram

• Entity
– An entity in this context is an object, a component
of data.
– An entity set is a collection of similar entities.
These entities can have attributes that define its
properties.
ER Diagram

• Entity Relationship Diagram


– By defining the entities, their attributes, and
showing the relationships between them, an ER
diagram illustrates the logical structure of
databases.
– ER diagrams are used to sketch out the design of a
database.
ER Diagram

• Entity Relationship Diagram


– Peter Chen developed ERDs in 1976.
– Since then Charles Bachman and James Martin
have added some slight refinements to the basic
ERD principles.
E – R Diagram ( Entity )
• Entities, which are represented by rectangles.
An entity is an object or concept about which
you want to store information.
E – R Diagram ( Weak Entity )
• A weak entity is an entity that must defined by
a foreign key relationship with another entity
as it cannot be uniquely identified by its own
attributes alone.
E – R Diagram ( Actions )
• Actions, which are represented by diamond
shapes, show how two entities share
information in the database.
E – R Diagram ( Actions )
• In some cases, entities can be self-linked. For
example, employees can supervise other
employees.
E – R Diagram ( Attribute )
• Attributes, which are represented by ovals. A
key attribute is the unique, distinguishing
characteristic of the entity. For example, an
employee's social security number might be
the employee's key attribute.
E – R Diagram ( Attribute )
• A multivalued attribute can have more than
one value. For example, an employee entity
can have multiple skill values.
E – R Diagram ( Attribute )
• A derived attribute is based on another
attribute. For example, an employee's monthly
salary is based on the employee's annual
salary.
E – R Diagram ( Attribute )
• Connecting lines, solid lines that connect
attributes to show the relationships of entities
in the diagram.
E – R Diagram ( Cardinality )
• Cardinality specifies how many instances of an
entity relate to one instance of another entity.
– While cardinality specifies the occurrences of a
relationship, ordinality describes the relationship
as either mandatory or optional.
– In other words, cardinality specifies the maximum
number of relationships and ordinality specifies
the absolute minimum number of relationships.
E – R Diagram ( Inf. Style )
E – R Diagram ( Chen Style)
E – R Diagram ( Bachman Style)
E – R Diagram ( Martin Style)
How to Construct an E – R Diagram

• Identify the entities. The first step in making an ERD is to

identify all of the entities you will use.

– An entity is nothing more than a rectangle with a description of

something that your system stores information about. This could

be a customer, a manager, an invoice, a schedule, etc. Draw a

rectangle for each entity you can think of on your page.


How to Construct an E – R Diagram
• Identify relationships. 
– Look at two entities, are they related?
• If so draw a solid line connecting the two entities.

• Describe the relationship. 

– How are the entities related?

• Draw an action diamond between the two entities on the line you just

added.

• In the diamond write a brief description of how they are related.


How to Construct an E – R Diagram
• Add attributes. 
– Any key attributes of entities should be added using oval-shaped
symbols.

• Complete the diagram. 

– Continue to connect the entities with lines, and adding diamonds to

describe each relationship until all relationships have been described.

• Each of your entities may not have any relationships,

• some may have multiple relationships.


E – R Diagram (Summary)
• Make sure that each entity only appears once per diagram.

• Name every entity, relationship, and attribute on your diagram.

• Examine relationships between entities closely.

– Are they necessary?

– Are there any relationships missing?

– Eliminate any redundant relationships.

– Don't connect relationships to each other.

• Use colors to highlight important portions of your diagram.

You might also like