DATABASE DESIGN AND IMPLEMENTATION
DAT604

CAR RESERVATION SYSTEM

Prepared by:
Atittegeb Gebreselassie
Raj Gopal Parimi
Rakesh Mudireddy
Sreenesh Tokala

Instructor:
Mohammad Amin

Table of Contents

1. Introduction 2.1. Purpose 2.2. Scope 2. Chen ER Diagram 3. Relations 4. Database schema and tools used 5. Pros and Cons of this project 6. Application for different uses 7. Conclusion 8. References

1. Introduction

2. Chen ERD
To describe car reservation database, the first step we used is high level or conceptual data model. Conceptual data model uses entities, attributes and relationships. We have 4 strong entities and one weak entity. Below is a list of each entity and their attributes in a table. We selected a primary key for each strong entity. The primary key is underlined and noted with (PK) under the attributes list.
We have one weak entity named DRIVER. It doesn’t have a primary key by itself. It depends on the customer. But we chose the driver ID as a partial key. The relationship among entities will be described using ERD later in the Chen ER diagram section of this project. ENTITY | ATTRIBUTES | CUSTOMER | * Name * address * Phone number * Email * Customer ID (PK) | DRIVER | * Name * Address * Phone Number * Driver ID (Partial K) | RESERVATION | * Reservation ID(PK) * Deposited amount * Pickup date * Return date | RENTAL_COMPANY | * Address * Name * Company Code (PK) | CAR_TYPE | * Type Code (PK) * make * model * maximum weight | CAR_DETAIL | * license number (PK) * engine serial number * year * available * mileage * number of seats |

The second step is to present the ERM using the entities, their attributes and relationship among them.
In this diagram, each entity is described by the attributes it