Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
260 views11 pages

C14 - Task 1 Group 24

The document discusses the conceptual and logical database design of a car rental booking management system. It outlines the scope of the system, task distribution among group members, compares two case studies, identifies business rules and relationships, and lists required entities and attributes for the database design.

Uploaded by

nur syahkina
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
260 views11 pages

C14 - Task 1 Group 24

The document discusses the conceptual and logical database design of a car rental booking management system. It outlines the scope of the system, task distribution among group members, compares two case studies, identifies business rules and relationships, and lists required entities and attributes for the database design.

Uploaded by

nur syahkina
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 11

Faculty of Computer Systems & Software Engineering

Universiti Malaysia Pahang

DCI1043 Database Systems


Semester 2 2018/2019

Project Task No: Part I

Project Title: Car Rental Booking Management System

Group No: 24

Lab Section: C14

Lecturer Name: Dr Salwana bt Mohamad @ Asmara

Group Members:

Name StudentID

1. Nursyahkina bt Othman CC18180


2. Muhammad Azrul Amri bin Noordin CC18258
3. Muhammad Syahmi bin Mohd Zulkefli CC18275
4. Umarul Imran bin Ahmed Qamal CC18291
5. Noor Athirah bt Irwan CC18407
TABLE OF CONTENTS

TOPICS PAGES
1.0 Conceptual and Logical Database Design
1.1 Introduction 3
1.2 Scope of the system 3
1.3 Task distribution 4
1.4 Case Study 5-7
1.5 Business Rule 8-9
1.6 Entity-Relation Diagram (ERD) 10
1.7 Extended Entity-Relation Diagram (EERD) 11
Part 1: Conceptual and Logical Database Design

1.1 INTRODUCTION
“CAR RENTAL BOOKING SYSTEMS”
This project Car Rental Booking System Management is a web based online system because
it’s easier for the customer to rent a car. This project Car Rental Booking System
Management has been provided car history details, their engine and parts details, insurance
registration and expiration details, car check in and check out details, car servicing details,
payment details etc. This project also have to facility to check their customrs and suppliers
details and their payment method mode and status details along with date and time. First time
customers will have to create a profile if they are taking a car on rent and select the
appropriate payment method. However customers are taking this service by visiting our
office, then they will get their ID and password. Customer will have the facility to select any
type of car and search their favourite car by their brand name. Upon selection of particular
type customers will able to get their entire details like rent type, cost for taking a particular
car, mileage details in kilometer an hour. This systems can also help for customer to fill the
basic information details like name, address, duration take the car rental etc. The main aim of
this project car rental system project is to maintain records of cars. Basically this sytem help
car rental shopper to make daily record and easy billing of customers. This system work 24/7
because its online existence which customer can use this system from anywhere and anytime.

1.2 SCOPE OF THE SYSTEM

System scope
●The car rental system to keep detail records of both the cars and the customers, the
duration they rent car as well as the type of car they rent.
● The system will be mainly design for small a company that renders it car rental
services to customers.
● The system will have the ability to generate and print invoice for each successful
transactions.
● Every work process activity is done by computer means no need of hardcopy.
1.3 PLANNING/WORK DISTRIBUTION

TASK STUDENT’S NAME


●The content of the report: NURSYAHKINA BINTI OTHMAN
(CC18180)
Project title
Background/ Introduction
●Scope (systems and users) MUHAMMAD AZRUL AMRI BIN
●Planning and work distribution NOORDIN (CC18258)
● Comparing case studies MUHAMMAD AZRUL AMRI BIN
-Analyze and compare two case studies on NOORDIN (CC18258)
database design that related to our project.
● Business rules UMARUL IMRAN BIN AHMED QAMAL
-Identify the business rules and relationship (CC18291)
of each entity including any assumptions.
● ER and EER diagram 1. NOOR ATHIRAH BINTI IRWAN
(CC18407)
2. MUHAMMAD SYAHMI BIN MOHD
ZULKEFLI (CC18275)
Case Study 1

Figure 1: The case study of car rental booking Figure 2: The user registration interface

Car Employee Custome


r

Car ID Customer ID
Employee ID
Plat no Customer name
Position
Car model Customer phone no
Address
Address
Employee name
City
Country

Rent Payment

Customer ID Customer ID
Time Date
Date Time
Payment ID
Case Study 2

Figure 3: The user registration interface of the system


Comparison

Case 1 (Book My Car) Case 2 ( Bohor Motorcycle Rental)


Entities 1. Employee 1. Type_of_Motorcycle
2. Rental_Car_Centre 2. Employee
3. Users 3. Admin
4. Admin 4. Users
5. User_Name 5. Rental_Motor_Centre
6. User_Name
Attributes  Car_ID  Motor_ID
 Plat_No  Plat_No
 Employee_ID  Employee_ID
 Position  Positon
 Address  Address
 Payment_ID  Name
 Customer_ID  Password
 Name  Payment_ID
 Password  Customer_
 Customer_Rent_No
Business  One admin can update to many  One admin can update to many
Rules employees. employees
 One employee can create one to  One employee can create one
many rent. to many rent
 A rent can only create by one  One payment can only be made
employee. by employee
 One payment can only produce  One rent can only be handle by
one rent. one employee
 One rent can modify many cars.  One rent can modify to many
 One to many cars can be motorcycle
modified by one rent.  One to many motorcycle can
 One to many rent can only be be modified by one rent
checked by one employee.  One to many rent can only
 One customer can checked one checked by one employee
to many rent  One customer can checked one
to many rent
Business Rules and Relationship Types

Entity Relationship Entity Business Rules


Type
Admin 1:M Employee One admin can update to many
employees. One to many employee can
be updated by one admin.
Employee 1:1 Maintenance One employee can maintain a
maintenance. Only one maintenance
can be maintain by one employee.
Employee 1:M Rent One employee can create one to many
rent. A rent can only be created by one
employee.
Rent 1:M Car One Rent can modify many cars. One
to many cars can be modified by one
rent.
Payment 1:1 Rent One payment can only product one
rent. One rent can only be produced by
one payment.
Rent M:1 Customer One to many rent can be checked by
customers. One customer can check
one to many rent.
REQUIRED ENTITIES AND ATTRIBUTES

NO REQUIRED ENTITY REQUIRED PRIMARY KEY


ATTRIBUTES
1. User Name No_ID

2. Admin Name Admin_ID


Password

3. Employee Employee_ID Staff_ID


Position
Address
Employee_Name

4. Motorcycle Motorcycle_model Motorcycle_ID


Plat_no

5. Maintenance Plat_no Car_ID


Car_model

6. Customer Adddress Customer_ID


Name
Phone_number

7. Rent Date Rent_ID


Time

8. Payment Date Payment_ID


Time

9. Car Car_model Car_ID


Plat_no
Employee Maintenance
Admin Car

Car_ID
Employee_ID Plat_no
Name Position maintain Car_ID
Password update Address Car model
Employee_name Plat_no

create

modity

Payment Rent Customer


ER Diagram for Car Rental Booking Management System

Payment_ID Time Address


Date product Date Customer_ID
Rent_ID Customer_name
Time check Customer_phone_no
Employee Maintenance
Admin

Car_ID (PK) Car


Employee_ID Plat_no
Name
(PK) maintain Car_ID (PK)
Password update Position
staff_ID Car model
Address Plat_no
EER DIAGRAM

Employee_name

create

modity

Payment Rent Customer


ER Diagram for Car Rental Booking Management System

Payment_ID Time Address


(PK) product Date Customer_ID (PK)
Rent_ID (PK) Customer_name
Date check Customer_phone_no
Time

You might also like