Explore databases from file-based systems to modern DBMS, covering data modeling, functional dependencies, and normalization for data integrity.

Computer Science Bootcamp

A database is a structured collection of data stored in a computer system. Data modeling involves designing the structure of a database to ensure efficient data storage, retrieval, and manipulation. Learning data modeling and design is essential as it enables the effective creation of database systems. This module introduces us to databases to gain a competitive edge in the tech industry. We’ll start by exploring the evolution of databases, from file-based systems to the modern era of database management systems (DBMS). Then, we’ll dive deep into fundamental concepts such as data modeling, entity-relationship models, and the relational data model. Next, we’ll learn about functional dependencies, normalization techniques, and their benefits in ensuring data integrity. By the end of this module, we’ll have a solid understanding of databases and their management, empowering us to excel in our careers as a developer and leverage this knowledge to contribute to innovative projects in the industry.

Data Modeling and Design

## The flight database

The flight database stores details about an airline’s fleet, flights, and seat bookings. Again, it’s a hugely simplified version of what a real airline would use, but the principles are the same.

Consider the following requirements list:

**Entities:**

* AIRPLANE entity

* FLIGHT entity

* PASSENGER entity

* BOOKING entity

**Attributes:**

* An airplane has a model number, a unique registration number, and the capacity to take one or more passengers.

* An airplane flight has a unique flight number, a departure airport, a destination airport, departure date and time, and arrival date and time.

* A passenger has a first name, surname, and unique email address.

**Relationships:**

* Each flight is carried out by a single airplane.

* The airline has one or more airplanes.

* A passenger can book a seat on a flight.


Try to design the ER diagram on your own. Give it some time and if you have trouble remembering some of the concepts, feel free to take a look at the previous lessons. 

---

In the next lesson, we will discuss the solution to this problem.

# The flight database

The flight database stores details about an airline’s fleet, flights, and seat bookings. Again, it’s a hugely simplified version of what a real airline would use, but the principles are the same.

Consider the following requirements list:

**Entities:**

* AIRPLANE entity

* FLIGHT entity

* PASSENGER entity

* BOOKING entity

**Attributes:**

* An airplane has a model number, a unique registration number, and the capacity to take one or more passengers.

* An airplane flight has a unique flight number, a departure airport, a destination airport, departure date and time, and arrival date and time.

* A passenger has a first name, surname, and unique email address.

**Relationships:**

* Each flight is carried out by a single airplane.

* The airline has one or more airplanes.

* A passenger can book a seat on a flight.


Try to design the ER diagram on your own. Give it some time and if you have trouble remembering some of the concepts, feel free to take a look at the previous lessons. 

---

In the next lesson, we will discuss the solution to this problem.

In this exercise, you will design the ER model for flight database.

Introduction

Fundamental Concepts

Data Modeling

Entity-Relationship Data Model

The Relational Data Model

Functional Dependencies

Normalization

Conclusion

Exercise 2

The flight database