Unit 1 — Introduction to DBMS & Entity-Relationship Model

Unit Overview

This unit lays the foundation for your entire understanding of database management systems. It introduces two major areas: the fundamental concepts of DBMS (what databases are, why we need them, how they are structured) and the Entity-Relationship model (how we design databases before implementing them).

Think of this unit as learning both the "what" and the "how to plan" of databases. Before you can write SQL queries or normalize tables, you need to understand what a database system actually does, how it differs from simple file storage, and how to model real-world scenarios as database structures. The ER model gives you a visual, intuitive way to design databases that correctly represent the relationships and constraints in your problem domain.

Topics Covered in This Unit

Conceptual Flow

The unit is structured in two halves. The first half covers DBMS fundamentals — understanding what databases are, their architecture, and the people who work with them. The second half introduces the ER model — the primary tool for conceptual database design.

These halves connect at a critical point: once you understand the three-level architecture and data models, you can appreciate why conceptual design with ER diagrams is necessary before jumping into relational tables. The ER model captures the real-world structure at a high level, which is then mapped to relational schemas in Unit 2.

Real-World Context

Consider designing a database for a university. You need to represent students, courses, faculty, departments, enrollments, grades, classrooms, and schedules. Each of these is an entity with specific attributes. Students enroll in courses (a many-to-many relationship), faculty belong to departments (many-to-one), and courses are taught in specific classrooms at specific times.

Before creating any SQL tables, a database designer would draw an ER diagram showing all these entities, their attributes, and relationships with cardinality constraints. This visual model serves as the blueprint — agreed upon by stakeholders — before any physical implementation begins. This is exactly the process you will learn in this unit.

Learning Objectives

After completing this unit, you should be able to:

1. Explain why DBMS is preferred over traditional file systems with specific examples of problems file systems create
2. Describe the three-level ANSI-SPARC architecture and explain both types of data independence
3. Differentiate between schema and instance, and between various data models
4. Identify entities, attributes (simple, composite, multivalued, derived), and relationships from real-world scenarios
5. Draw complete ER diagrams with proper notation including cardinality constraints
6. Distinguish between strong and weak entity sets and identify partial keys
7. Apply specialization, generalization, and aggregation concepts in ER modeling
8. Identify all types of keys and explain their roles in maintaining data integrity

These skills form the prerequisite knowledge for relational database design, SQL programming, and normalization covered in subsequent units.