ER diagram notation in DBMS Theory - Step-by-Step Execution

Concept Flow - ER diagram notation

Identify Entities

↓

Define Attributes

↓

Set Primary Keys

↓

Determine Relationships

↓

Assign Cardinalities

↓

Draw ER Diagram Symbols

The flow shows how to create an ER diagram by identifying entities, attributes, keys, relationships, cardinalities, and then drawing the notation symbols.

Execution Sample

DBMS Theory

Entity: Student
Attributes: StudentID (PK), Name, Age
Relationship: Enrolls in Course
Cardinality: Student (1) to Course (M)

Defines a Student entity with attributes and a relationship to Course with cardinality.

Analysis Table

Step	Action	Notation Symbol	Example
1	Identify Entity	Rectangle	Student
2	Define Attributes	Ovals connected to Entity	StudentID, Name, Age
3	Set Primary Key	Underline attribute	StudentID
4	Determine Relationship	Diamond	Enrolls
5	Assign Cardinality	Numbers or symbols near lines	1 (Student) to M (Course)
6	Draw Connections	Lines connecting symbols	Student -- Enrolls -- Course
7	End	Complete ER Diagram	Visual representation ready

💡 All entities, attributes, relationships, and cardinalities are represented with correct ER notation symbols.

State Tracker

Element	Initial	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
Entities	None	Student	Student	Student	Student	Student	Student
Attributes	None	None	StudentID, Name, Age	StudentID (PK), Name, Age	StudentID (PK), Name, Age	StudentID (PK), Name, Age	StudentID (PK), Name, Age
Relationships	None	None	None	Enrolls	Enrolls	Enrolls	Enrolls
Cardinalities	None	None	None	None	1 (Student) to M (Course)	1 (Student) to M (Course)	1 (Student) to M (Course)

Key Insights - 3 Insights

Why is the primary key attribute underlined in the ER diagram?

The underline shows which attribute uniquely identifies each entity instance, as seen in step 3 of the execution_table where StudentID is underlined.

How do we represent the relationship between entities?

Relationships are shown using diamonds connected by lines to entities, as shown in step 4 and 6 where 'Enrolls' is the diamond connecting Student and Course.

What does cardinality mean and how is it shown?

Cardinality shows how many instances of one entity relate to another, represented by numbers or symbols near the connecting lines, like '1' and 'M' in step 5.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What notation is used to indicate the primary key?

A Use a rectangle

B Draw a diamond around the attribute

C Underline the attribute

D Connect with a dashed line

💡 Hint

Refer to step 3 in execution_table where StudentID is underlined to show primary key.

At which step in the execution_table do we assign cardinalities to relationships?

A Step 2

B Step 5

C Step 4

D Step 6

💡 Hint

Look at the 'Assign Cardinality' action in step 5 of the execution_table.

If we add a new attribute 'Email' to the Student entity, which step in variable_tracker will change?

A After Step 2

B After Step 1

C After Step 4

D After Step 5

💡 Hint

Attributes are defined at step 2, so changes appear after Step 2 in variable_tracker.

Concept Snapshot

ER Diagram Notation:
- Entities: Rectangles
- Attributes: Ovals (Primary key underlined)
- Relationships: Diamonds
- Connections: Lines
- Cardinality: Numbers/symbols near lines
Use these symbols to visually model database structure.

Full Transcript

An ER diagram uses rectangles to show entities like Student. Attributes such as StudentID, Name, and Age are shown as ovals connected to the entity. The primary key attribute is underlined to indicate uniqueness. Relationships between entities, like Enrolls between Student and Course, are shown with diamonds. Lines connect entities and relationships. Cardinality, such as one-to-many, is shown with numbers or symbols near the lines. This notation helps visualize how data is organized in a database.

Practice

1. Which shape in an ER diagram represents an entity?

easy

A. Rectangle

B. Oval

C. Diamond

D. Triangle

Solution

1. Step 1: Recall ER diagram shapes

   Entities are shown as rectangles in ER diagrams.

2. Step 2: Match shape to entity

   Rectangles represent entities, ovals represent attributes, diamonds represent relationships.

3. Final Answer:

   Rectangle -> Option A

4. Quick Check:

   Entity = Rectangle [OK]

Hint: Entities are rectangles, attributes are ovals [OK]

Common Mistakes:

• Confusing attributes (ovals) with entities
• Thinking diamonds are entities
• Mixing shapes with cardinality symbols

2. In ER diagrams, which shape is used to represent an attribute?

easy

A. Diamond

B. Rectangle

C. Hexagon

D. Oval

Solution

1. Step 1: Identify attribute symbol

   Attributes are shown as ovals in ER diagrams.

2. Step 2: Confirm shape usage

   Ovals represent attributes, rectangles represent entities, diamonds represent relationships.

3. Final Answer:

   Oval -> Option D

4. Quick Check:

   Attribute = Oval [OK]

Hint: Attributes are always ovals in ER diagrams [OK]

Common Mistakes:

• Choosing diamond instead of oval
• Confusing entity and attribute shapes
• Selecting shapes not used in ER diagrams

3. Consider an ER diagram where a diamond connects two rectangles with a line labeled '1' on one side and 'N' on the other. What does this cardinality mean?

medium

A. One entity relates to one entity only

B. Many entities relate to one entity

C. One entity relates to many entities

D. Many entities relate to many entities

Solution

1. Step 1: Understand cardinality symbols

   '1' means one entity, 'N' means many entities.

2. Step 2: Interpret relationship

   The side with '1' relates to many entities on the 'N' side, so one entity relates to many entities.

3. Final Answer:

   One entity relates to many entities -> Option C

4. Quick Check:

   Cardinality 1 to N = One to many [OK]

Hint: 1 to N means one entity connects to many [OK]

Common Mistakes:

• Reversing the direction of cardinality
• Confusing 'N' with one
• Ignoring the diamond relationship

4. Identify the error in this ER diagram description: "A diamond represents an attribute, and an oval represents a relationship."

medium

A. Diamond represents a relationship, not an attribute

B. Oval represents an entity, not a relationship

C. Rectangle represents an attribute, not a relationship

D. There is no error in the description

Solution

1. Step 1: Recall ER diagram shape meanings

   Diamonds represent relationships, ovals represent attributes.

2. Step 2: Check the description correctness

   The description wrongly says diamond is attribute and oval is relationship, which is incorrect.

3. Final Answer:

   Diamond represents a relationship, not an attribute -> Option A

4. Quick Check:

   Diamond = Relationship [OK]

Hint: Diamonds = relationships, ovals = attributes [OK]

Common Mistakes:

• Mixing diamond and oval meanings
• Thinking rectangles are attributes
• Assuming no error exists

5. You want to model a "Student" entity with attributes "StudentID" (unique), "Name", and "PhoneNumber" in an ER diagram. Which notation correctly shows the uniqueness of "StudentID"?

hard

A. "StudentID" attribute inside a diamond connected to the Student rectangle

B. "StudentID" attribute underlined inside an oval connected to the Student rectangle

C. "StudentID" attribute inside a rectangle connected to the Student oval

D. "StudentID" attribute inside an oval with a double border connected to the Student rectangle

Solution

1. Step 1: Recall notation for key attributes

   Key (unique) attributes are shown as underlined text inside ovals.

2. Step 2: Apply notation to "StudentID"

   "StudentID" should be underlined inside an oval connected to the Student entity rectangle.

3. Final Answer:

   "StudentID" attribute underlined inside an oval connected to the Student rectangle -> Option B

4. Quick Check:

   Key attribute = Underlined oval [OK]

Hint: Underline key attributes inside ovals [OK]

Common Mistakes:

• Using diamond for attributes
• Placing attributes inside rectangles
• Using double border for uniqueness