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.