DBMS Topics
Unit 1 Summary — Introduction to DBMS & ER Model
Last Updated : 21 May, 2026
Key Concepts at a Glance
DBMS Fundamentals
| Concept | Key Point |
|---|---|
| DBMS | Software to define, create, maintain, and control database access |
| Database | Organized collection of structured, persistent data |
| File System vs DBMS | DBMS solves redundancy, inconsistency, security, concurrency issues |
| DBA | Central administrator responsible for schema, security, performance |
Three-Level Architecture
External Level
Multiple user views
Customized views for users/apps
Conceptual Level
Single logical schema
What data exists
Internal Level
Physical storage
How data is stored
Physical Independence: change internal without affecting conceptual.
Logical Independence: change conceptual without affecting external.
Data Models
| Model | Structure | Relationships | Still Used? |
|---|---|---|---|
| Hierarchical | Tree | 1:N only | Legacy |
| Network | Graph | M:N | Legacy |
| Relational | Tables | M:N via FK | Yes (dominant) |
| Object-Oriented | Objects | References | Limited |
| ER Model | Entities+Relationships | Design tool | Yes (design phase) |
ER Model Components
| Entity | Rectangle |
| Attribute | Oval |
| Key Attribute | Underlined Oval |
| Multi-valued | Double Oval |
| Derived | Dashed Oval |
| Relationship | Diamond |
| Weak Entity | Double Rectangle |
| Weak Relation | Double Diamond |
Types of Keys
Cardinality Types
| 1:1 | Each A maps to at most one B, and vice versa |
| 1:N | One A maps to many B's; each B maps to one A |
| M:N | Many A's relate to many B's; implemented with a junction table |
EER Extensions
| Concept | Direction | Description |
|---|---|---|
| Generalization | Bottom-up | Combine entities into superclass |
| Specialization | Top-down | Divide entity into subclasses |
| Aggregation | — | Treat relationship as entity |
| Weak Entity | — | Depends on strong entity for identity |
Important Formulas / Rules
- Partial Key (Weak Entity): Full PK = Identifying entity's PK + Discriminator
- M:N Relationship: Always requires a junction table with composite PK
- Total Participation: Enforced by NOT NULL on foreign key
- Foreign Key Rule: FK value must exist in referenced PK column (or be NULL)
Common Exam Questions
- Draw an ER diagram for a given scenario
- Identify the type of key from a given relation
- Convert ER diagram to relational schema
- Explain physical vs. logical data independence
- Identify weak entities and their discriminators
- Explain specialization vs. generalization with examples
Exam Focus
Revise definitions, diagrams, examples, and short-answer points for Unit 1 Summary — Introduction to DBMS & ER Model.
Interview Use
Prepare one clear explanation, one practical example, and one common mistake for this DBMS topic.
Search Terms
dbms, database management system, database notes, sql, unit, summary, unit 1 summary — introduction to dbms & er model
Related DBMS Topics