Core Concept Mastery • DBMS Module
Imagine an Architect's Blueprint.
Entities (Rectangles): These are the "Main Things". E.g., Student, Teacher, Course.
Attributes (Ovals): These are the "Details". Student has Name, Age, Roll No. Teacher has Salary, Subject.
Relationships (Diamonds): These are the "Actions". Student 'Learns' Course. Teacher 'Teaches' Student.
Before you create a database, if you draw an ER diagram, you get a clear idea. Otherwise, it's like building a house and realizing, "Oops! I forgot the kitchen!"
You wouldn't build a house without a drawing first, right? Same for databases. We map it out visually before writing a single line of code.
A Rectangle labeled "Student" has Ovals connected to it like "Name", "Age", and "Marks".
"In an ER diagram, an attribute that can be divided into sub-parts is called?"
Composite Attribute.