CAR AND CHAUFFEUR HIRING SERVICES.

BY

BASSEY DAVID ANIETIE

BU/16C/IT/2244

DEPARTMENT OF COMPUTER

SCIENCE

BAZE UNIVERSITY, ABUJA.

NIGERIA.

JUNE 2021.
DESIGN AND IMPLEMENTATION OF CAR AND CHAUFFEUR
HIRING SERVICES.

THESIS SUBMITTED IN PARTIAL FULFILMENT OF

THE REQUIREMENT FOR THE DEGREE OF

B.Sc. IN SOFTWARE

ENGINEERING

THE DEPARTMENT OF COMPUTER SCIENCE

FACULTY OF COMPUTER AND APPLIED

SCIENCES.

BAZE UNIVERSITY, ABUJA

JUNE 2021.
DECLARATION

This is to certify that this Thesis/Report entitled “DESIGN AND IMPELMENTATION OF

CAR AND CHAUFFER HIRING SERVICE which is submitted by DAVID ANIETIE
BASSEY in partial fulfillment of the requirement for the award of degree for B.Sc. in Software
Engineering to the Department of Computer Science, Baze University Abuja, Nigeria,
comprises of only my original work and due acknowledgement has been made in the text to all
other materials used.

Date: 28th June 2021. Name of Student: DAVID ANIETIE BASSEY

APPROVED BY ……………………

Head

Faculty of Computing & Applied Science

i
 CERTIFICATION

This is to certify that this Report entitled DESIGN AND IMPLEMENTATION OF CAR AND
CHAFFEUR RENTING SERVICES, which is submitted by DAVID ANIETIE BASSEY in
partial fulfillment of the requirement for the award of degree for B.Sc. in Software
Engineering to the Department of Computer Science, Baze University Abuja, Nigeria is a
record of the candidate’s own work carried out by the candidate under my/our supervision. The
matter embodied in this thesis is original and has not been submitted for the award of any other
degree.

Date: 28th June 2021. Supervisor: Dr. Lawrence Morolake

Date: 28th June 2021. Supervisor: Mr. Gilbert George

ii
APPROVAL
This is to certify that the research work, CAR AND CHAUFFEUR RENTAL SERVICES and the
successive preparation by DAVID ANIETIE BASSEY id BU/16C/IT/2244 has been approved by
the Department of Computer Science, Faculty of Computing and Applied Science, Baze
University, Abuja, Nigeria.

By

Dr. Lawrence Morolake Date/Sign

1st Supervisor

Mr. Gilbert George Date/Sign

2nf Supervisor

Dr. Chandrashekhar Uppin Date/Sign

Head, Department of Computer Sciences

Prof. Mohammed Hammawa Baba Date/Sign

iii
 Dean, Faculty of Computing and Applied Science

Prof. Ahmed Baita Garko

External Examiner Date/Sign

iv
 DEDICATION

All forms of praise! Thank you Lord, the creator of mankind, the most merciful and gracious for
his blessings, protections, courage and guidance.

I would like to acknowledge and thank Dr. Lawrence Morolake, who stood by me and made sure
I did everything concerning this project efficiently and effectively. I also thank my second
supervisor Mr. Gilbert George and my Parents for their immense support, guidance and
encouragement to make sure that I complete this program successfully. I would also like to
acknowledge my lecturers and all who have contributed to this point in the success of my
academic pursuit.

v
ABSTRACT
This application presents an application (on the design and implementation) for a car/chauffeur hiring
services. This enables the administrator to keep track of all the customers’ information and also enables easy
process of hiring a car as well as a chauffeur which dedicates time to an assigned customer for any duration of
time chosen by a customer.

The aim of this study is to develop and implement an application where by individuals can rent cars with
different variety of cars and what makes it more interesting is that all cars come with a chauffeur whereas, the
chauffeur stays with you for the assigned duration or period of time you need its services. Also, there is a
Management and Centralized Database System that aids capturing of information of customers where
bookings and transactions are enabled. This was developed to reduce the effect of labor-intensive system of
registering customers while booking.

vi
Table of Contents

ABSTRACT.................................................................................................................................VI

CHAPTER 1: INTRODUCTION.................................................................................................1
OVERVIEW................................................................................................................................1
BACKGROUND AND MOTIVATION.....................................................................................1
STATEMENT OF THE PROBLEM...........................................................................................2
AIM AND OBJECTIVES............................................................................................................3
SIGNIFICANCE OF THE PROJECT.........................................................................................3
PROJECT RISKS ASSESSMENT..............................................................................................3
SCOPE/PROJECT ORGANIZATION........................................................................................4

CHAPTER 2: LITERATURE REVIEW....................................................................................6

INTRODUCTION.......................................................................................................................6
HISTORICAL OVERVIEW.......................................................................................................6
RELATED WORK......................................................................................................................7
SUMMARY...............................................................................................................................21

CHAPTER 3: REQUIREMENTS ANALYSIS AND DESIGN..............................................22

OVERVIEW..............................................................................................................................22
PROPOSED METHODOLOGY...............................................................................................22
REQUIREMENT ANALYSIS..................................................................................................24
REQUIREMENT SPECIFICATIONS......................................................................................24
Functional Requirement Specifications.................................................................................24
Non-Functional Requirement Specifications.........................................................................25
SYSTEM DESIGN....................................................................................................................25
Use case Diagram..................................................................................................................25
Class Diagram.......................................................................................................................29
Database Design....................................................................................................................30
Dataflow Diagram (DFD).....................................................................................................31
Activity Diagram....................................................................................................................33
Application Architecture........................................................................................................38
vii
 SUMMARY...............................................................................................................................40
SYSTEM DESIGN....................................................................................................................25
Use case Diagram..................................................................................................................25
Class Diagram.......................................................................................................................29
Database Design....................................................................................................................30
Dataflow Diagram (DFD).....................................................................................................31
Activity Diagram....................................................................................................................33
Application Architecture........................................................................................................38
SUMMARY...............................................................................................................................40

CHAPTER 4: IMPLEMENTATION AND TESTING............................................................41

OVERVIEW..............................................................................................................................41
DEVELOPMENT TOOLS AND TECHNOLOGIES...............................................................41
IMPLEMENTATION PROBLEMS..........................................................................................41
TESTING...................................................................................................................................46
Test Plans...............................................................................................................................46
Test Traceability Matrix........................................................................................................48
Test Report Summary.............................................................................................................48
USE GUIDE...............................................................................................................................49
SUMMARY...............................................................................................................................49

CHAPTER 5: DISCUSSION, CONCLUSION, AND RECOMMENDATIONS..................50

OVERVIEW..............................................................................................................................50
OBJECTIVE ASSESSMENT....................................................................................................50
LIMITATIONS AND CHALLENGES.....................................................................................51
FUTURE ENHANCEMENTS..................................................................................................51
RECOMMENDATIONS...........................................................................................................52

viii
 CHAPTER 1: INTRODUCTION

Overview
They are various improvements where the web and internet that has impacts and upgrades to individuals, the
public get a distinct character with a whole lot of information and data. The network/web aids communication
on devices. While, world has become an overall town where there is a lot of imaginative improvement this
expresses change and making most equipment automated. Lately, particular activities work done or exercises
are restricted by information structures. A driver/chauffeur registering in an organization where individuals
rent vehicles and these vehicles are hired for a particular period of time. People rent vehicles for their
different reasons and tasks. The vehicle rentals similarly as a driver/escort with the strategy to travel or move
beginning with one spot then onto the following for business purposes, visit, and occasions.

Background and Motivation

Background
Online Chauffeur/vehicle rental administration data framework is fundamental having one which
isn't practical prompts complexity, vulnerability and required decisions, knowledge and much
between close to home ability to complete their assignments. Data streams are fundamental thus
there ought to be a lot of dependence on PC overwhelmed frameworks. All in all, Africa One
Travels required control framework with input, which were fundamental in completing the
checking job. There is need for the executives data frameworks to get data about the
Climate by checking and data gathering measure. (Lucey, 1997) This was done to differentiate
likely dangers and openings. Having no administration data framework left the association not
ready for hazard and this presented it to more prominent misfortune.

An Information System like an online vehicle rental administration framework should be subsequently taken a
look at as a collection of apparatus, individuals and techniques used to achieve capacities. Directors at this
level are worried about the execution and control of everyday exercises of the association and how these
frameworks or data might be executed which made the association vulnerable to hazards.

 Team, P. (2017, August 11). 01 Cyber Attacks. Retrieved from

http://intelligentsystemsmonitoring.com/community/security-community/01-cyber-attacks/
This is so on the grounds that successful and effective data handling is fundamental since controls
are various, observing is steady, information volumes are very high also, prompt reaction is
required.
Vehicle rental has been around for longer than a century! At the point when vehicles were
acquainted with individuals, sharp business people distinguished a developing interest for leasing.
Notwithstanding, before vehicles are created, individuals would in any case lease ponies and
carriages. Indeed, even in old Rome, chariots were leased. The most punctual records of vehicle
recruit can be followed as far back as 1904, when a bicycle shop in Minneapolis started offering
vehicles for lease. A few years after the fact, the German organization, named "Sixt Car Hire" was
developed in 1912. It recently started with three vehicles for lease and quickly expanded. In 1915,
in Omaha, Nebraska, Joe Saunders had a second and perceived that nobody in Omaha offered
vehicles for leasing. He utilized just a single salesman, Frank Arndt, from Germany, and started
leasing Arndt's Model T. This undertaking wound up effectively that by 1917.

 9.22.17 by STLTODAY.COM - issuu. (n.d.). Retrieved from

https://issuu.com/dmsgroup/docs/09-22-2017.pdf

Motivation

In supposed believe with authentic and quick advancement of vehicle rental organizations, the path
measures in the organizations are occurring today which is very tricky, this task is wanted to facilitate those
cycles through fostering a viable and proficient vehicle rental framework, actually like other created nations
are utilizing innovations towards working with their clients measures through projects like Sixt Car Hire,
Germany.

Statement of the Problem

2
The manual vehicle rental framework offers types of assistance just during available time. Thus, clients have
restricted chance to make any exchanges or reservation of the vehicles. The issue with the current framework
is that some organizations as of now have a vehicle rental framework which isn't an online application. This is
an obstacle that gives them ability to store client's restraints, and yet they can't make their administrations
more accessible to general society through the web, they rather utilize banners to publicize their
administrations to general society. They likewise utilize call reservations which is additionally restricted to
not many highlights as contrast with a web base framework. For instance, a client may settle on a telephone
decision booking for a specific vehicle, however when he/she comes to pick the vehicle, he/she may go not to
like the vehicle, this could be on the grounds that the client couldn't see an example image of the vehicle
he/she needs to lease. The following are a few issues with running vehicle rental organization physically:

• To lease a vehicle, an imminent leaseholder should initially go to the closest office to enlist as a
customer, what of if the client needs more an ideal opportunity to do that?

• Cars that give troubles to lease are ordinarily promoted in nearby or public paper. It includes a great
deal of administrative work and devours time.

• The interaction of dealing with client's information is moderate if the organization is utilizing manual
framework and there may be a large number of customers.

• It is difficult to keep record of every single rental vehicle, etc.

3
Aim and Objectives
• To foster a straightforward and secure framework that ensures customer data and private data of the
association

• Basically the plan is to use frameworks which empower customers to have access to automobiles or
ordering various hold a cars /trucks through the web.

• Planning a framework that empowers customer compensation their vehicle lease on the web.

• To foster a framework that stores appointments and reservations data just as installment history to help the
association monitor exchanges.

•To execute geo-fencing and distant vehicle endless supply of rental period.

Significance of the Project

The development of this project offers an elastic background putting students through in exploring
various topics whereby key abilities are developed and some of these skills are based on
communication, cooperation, and machinery skills.
The car rental management system aids to solve various difficulties which deal with labor-
intensive way of carrying out a task. Therefore, errors waste valuable time and energy which
causes elimination within the system. This delays the improvement in output and competence in
an association.
Also, it would help students and researchers that are working actively towards enhancing the car
rental management system, this work would serve as a reference to them as they strive to develop
the car rental company technologically. Additionally, issues of insecurity, trustfulness could be
resolved, because payment system would be linked to the system to eliminate these issues
between people and the scammers as well as customers and the company’s staffs.

4
Project Risks Assessment
Table 1. 1 Risk and Prevention

Loss of power There is likelihood of loss of power when

working on the project. To avoid that, the
laptop used last for nearly five hours this is
good enough between the times taken to bring
back the light.
Inability to carry out research due to loss of Required hardware will be bought instantly
hardware or software resources while relevant software that may likely be lost
will be kept in the computer for easy repair
or reinstallation.
Loss of work due to equipment failure /loss Weekly data backup to portable hard drive
Lack of Internet access To prevent lack of internet access, two means
of internet access was provided purposely for
this project, which is not from the same ISP
and one is wired whereas the other one is
wireless.
RISK PREVENTION

5
Scope/Project Organization
The aim of this project is to establish a mobile based car rental/chauffeur management system.
At this stage of development, the project would be launched using android Studio.
The remaining part of this project is organized as follows:
Chapter One - contains the Introduction: Basically talking about how, what the project entails, how the app
works and uses of what the app does basically showing us an idea of what the app has to offer.

Chapter Two- contains literature review; historical overview of the system and some related
works and incredible achievements made by other researchers and entrepreneurs towards
enhancing car rental company and the current implemented functionalities which will help in
deciding what to add, remove or which part of the system to enhance to reflect the modern way
of carrying out those processes.
Chapter Three - primarily covers the analysis and design of the system, which are noted after
intensively and carefully chosen the development methodology and how the methodology
would be approached. In the analysis part, combination of data gathering techniques such as
interview and observation were used to gather the data, followed by the modelling that depicts
the logical model of the system and the subsequent design that shows the physical design of
the system.
Chapter Four - comprises the implementation of the system, the programming language used,
test cases i.e. the functionalities tested and some errors encountered during the development,
those that are resolved and those that are not.
Finally, Chapter - Five defines the project evaluation, conclusion, further studies as well as
recommendation. Evaluation these are literally the assessment of the project with respect to its
objectives and subjective, followed the expected further studies then at the end the conclusion.

6
CHAPTER 2: LITERATURE REVIEW

Introduction
So many car rental management systems that have been developed, and all these car rental
systems are aiming at offering reliable services which can be accessed by customers at any time
regardless of the location. This chapter contains the literature review of the car rental
management system to be developed. This chapter will also review the existing systems that are
similar to the car rental management system. References are made to sources from the internet.

Historical Overview

A car rental/chauffeur hiring service is an organization that rents vehicles for a short period of
time. Vehicle rental organizations most times do not attend to individuals who want to rent a
short-term vehicle, for example, the individuals who don't own entitlement to their own vehicle,
travellers who are away, or proprietors of harmed or annihilated vehicles who are anticipating fix
or protection remuneration.

The known blueprint of vehicles being offered for rent follows straightforwardly in 1906

[1]. The German alliance Sixt was set up in 1912 under the name Sixt Autofahrten und
Selbstfahrer (Sixt Car Cruises and Self Drivers) [2]. Joe Saunders of Omaha, Nebraska from the
beginning started with only one got Model T Ford in 1916, regardless by 1917; his Ford Livery
Company was renting 18 Model Ts at a dime for every mile. The alliance name became Saunders
Drive-It-Yourself System and accordingly Saunders System. By 1926, Saunders had extricated
up to 56 metropolitan regions. The layout of vehicles being offered for rent follows
straightforwardly in 1906.
 Damayanti, Y. (n.d.). Retrieved (2005) from “Car Rental Information System Design using Microsoft
visual basic version 6.0”. Gunadarma University.

The association was bought by Avis in 1955. An early competitor to Saunders was Walter L. Jacobs, whose
Chicago-based Rent-a-Car opened in 1918 with the twelfth Ford Model T. The connection was bought
in 1923 by John Hertz. In Britain, vehicle rental started with Godfrey Davis, set up in 1920, and bought
by Europcar in 1981. (Walter L. Jacobs, 88; Rent-a-Car Pioneer, 2015) The region expanded rapidly in
the US; in 1926, the American Drive yourself Association amassed in excess of 1200 specialists in
Chicago. The progress being created after World War II influenced the establishment a couple of
prominent by and large affiliations, including National Car Rental (1947), Europcar (1949), Enterprise
Rent-A-Car (1957), Thrifty Rent A Car (1958), and Budget Rent a Car (1958).

7
  McLeod, R., & Schell, G. (2009). Management information systems. Retrieved June 29, 2021, from
https://www.amazon.com/Management-Information-Systems-Raymond-McLeod/dp/0131889184
(Walter L. Jacobs, 88; Rent-a-Car Pioneer, 2015)

Related Work
The existence of the internet and the World Wide Web in the mid-1980s and late-1980s
respectively resulted in an exceptional revolution that inspires provision of car rental related
services effectively and efficiently. Below are some related systems.

The chauffeur/car rental system services is designed and developed to offer the services listed below:
1. Increase vehicle rental/driver proficient cycle : The vehicle rental framework will permit business to
extend their compass to a worldwide market instead of restricting themselves to their neighborhood
market.

2. Online vehicle appointments/reservations: This will permit the client to choose accessible vehicles
and book before their normal get time.

3. Registration of clients/ Chauffer’s: This is more life a portal where clients key information their
subtleties and furthermore permits the vehicle enlist the board to screen client exchanges and use them
to convey altered assistance and offers.

4. Group appointments: This part will permit clients to reserve a spot for vehicles to be utilized by a
get-together on account of corporate gathering, weddings or some other occasion.

Objectives
 To develop a car rental/chauffeur service that will allow customers to register, and hire cars online.
 To develop a car hire/ chauffeur system that will simplify staff and vehicle management.
 To develop a car hire/ chauffeur system that will make it easy for customers to rent a car and track
their pick-up.

Requirements
8
When the car hire system is complete, a requirement analysis will be undertaken using a software engineering
technique involving tasks that will determine the conditions and needs that will have to be met for the system
to work. This assessment must consider all the possibly inconsistent requirements of entities with diverse
dimensions.

Functional Requirements
Functional requirements are those used to exhibit how the internal system architecture works to meet the
overall systems objectives. This also demonstrates subsystems with the main car rental system as well as the
descriptions of each step. This entails what tasks the systems have to execute, which data the system should
hold, processes involved, and the relevant user interface. The functional car rental system requirements are:

1. Registration of customers: The system will allow new customers to register online as users and
automatically create a membership card.
2. Reservation of vehicles online: Customers should easily create a car reservation from a remote
location.
3. Automated database updating based on real-time vehicle reservations: The system will
automatically update the database regarding cars hired, cars booked, available cars, etc.
whenever a customer reserves a vehicle or whenever a customer returns it.

Car/Chauffeur Hiring System

This project is designed to help individuals with operating transportation efficiently. Recently,
vehicles have become most profitable strategies for transportation. Basically "our vehicle/escort
enlisting structure helps in making this an easier, trouble free and beguiling experience to get and
use a vehicle as indicated by ones needs". An individual can book a vehicle unequivocally for his
development time, co-explorers and the possibility of development. The rental structure crosses
from arranging a data base to understanding business thought or all the more all to simplify this to
change system for various journeying needs.

 Individuals

 Clients

 Negotiators
9
  Workers

 Vehicles-data and type.

 Vehicle-reservations

 The–chauffeur

 Location

 Insurance

 Bill-generated

 Payment

 Checkout

 Return Car

Database entities are basically described as:

o The people-In this phase, Individuals table store a lot of data whereby, all individuals
connected with the movement and framework where workers are incorporated with
specialists and clients. In this element individual’s id is the essential key. Different ascribes
such as given name, surname, place of residence, municipal, email, phone and email.
o The customers table consists of all the data of clients used to enable the hiring package. The
customer id (CID) is used for identification. Therefore, Individuals ID is used as a reference
key here which helps to identify individual’s table. The other attributes of this entity are
identification category and package which serves as references to schedules table.

o The Agents table stores all the facts that have to do with the negotiators they enable the setup
of cars to enable several individuals to hire and then they take percentage charges. Also data
is provided based on the location where they work as a foreign key.
o In the Employees table, we have the entirety of the representatives working in the workplace,
excluding from field specialists, auto technicians, and so forth.
o The Car details entity keeps the records for all of the available cars. It has car id as primary

10
 key. This entity also includes car name, Vin, seating capacity of car, production year. It also
stores the price to rent the car.
o The Car bookings table keeps the records of the cars booked by the travelers at the specific
locations. The booked car is added to this table with its car id and itinerary id of the person
who booked the car.
o The driver(Which is known as Chauffeur); This is a weak entity derived from the
customers table which has customer id as a foreign key which references to the customers
table. This entity keeps the record of the person who might drive the rented car with the
customer. Driving license number will also store of that person.
o Insurance table has Insurance Type as primary key which keeps record of insurance type.
This table has other entities like collision coverage which stores amount of Collison, Body
coverage will cover amount of body damage of car and medical coverage will cover medical
issue with customer in accidents.
o Bill table holds the bill for the customers. This table has bill number as primary key. Rent per
day and rented days are attributes for counting bill amount which shows amount customer
needs to pay and then is paid by the use of paster.

11
.Below is an Entity Relationship Diagram for the car rental system. Whereas the
FLOW OF THE CHAUFFEUR RENTAL SERVICE and how the processes take place.

Figure 1. 0 Showing an entity activity diagram for a car/chauffeur rental hiring system.

12
 Figure 1. 1 Data Flow Diagram
Data flow diagram illustrates that customer set their usernames, passwords, and makes vehicle rental
history at whatever point they employ a vehicle. Clients can see their rental history. The operational director
gets client information, vehicle rental history for the power source, vehicle information, and Visa information.
Then again, operational supervisors can include the information their username and secret word. They can
likewise Create, Read, Update, and Delete client information and their own information. The proprietors and
tasks director have comparable data shipped off the framework also the data they can get from the framework
with the exception of proprietors approach reports across all outlets.

13
 The car rental system context diagram illustrates when customers and admin &staff send and receive
information from the system. The customer makes inquiries of the available car types and prices, the system
returns suitably available cars, the customers then make a booking and the system provides the booking
number then the customers confirm the reservation by paying. On the other hand, admin and staff update the
details of available cars based on cars returned or new cars added to the business. The admin and staff also get
notifications about new car reservations.

Figure 1. 2 Entity Relationship Diagram

14
2.1.1 Development of Car Rental Management Information System for Avis Indonesia
The data framework is intended to all the more intently administrator's requirements and the
framework is set up as significant PC application region. The Management Information System
(MIS) as a PC based framework makes data accessible to clients with comparative necessities.
Director utilized the yield data. The prior investigations shown that MIS could use to oversee
vehicle rental, expected to speed up just as documenting administrations to clients better and
more secure, making it simpler when needed whenever.

Figure 1. 3 Software Development Life Cycle.

Abg. (n.d.). Car rentals from avis, book online now & save. Retrieved 2009 from
https://www.avis.com/en/home

Mehta, A., Patil, V., & Shinde, A. Retrieved (2019, October 30). LeKeDe: from Online rental system. from
https://www.ijert.org/lekede-online-rental-system

15
1. Planning Phase: This is the first phase whereby the computer specialists fostering a data
framework search for the most squeezing/center issues which cause limitations that happen
when running the framework, this empowers the assembling of objectives and framework
advancement that spotlights on online vehicle rental framework. In earlier arranging stage,
specialists notice and gather information in Avis Indonesia.
2. Analysis Phase: The researchers analyze the company’s management, workflow, look
for problems that occur within the company, car rental procedures and car rental data
processing. System analysis aim is to find the ideal form of application a researcher will
develop by taking into account of various issues and needs that exist on the system as
specified in system planning.

3. Design Phase: The inventors utilized a few devices to make framework plan, for example
measure plan, flowchart for proprietor and region supervisor, and Data Flow Diagram
(DFD) for the vehicle rental framework.[18][19][20].
4. Implementation Phase: Investigators will plan to interpret or translate the system
application design into programming language that can be understood by computer
system so application can run and be used. Researchers used software and programming
language like PHP, MySQL for database and framework in visual web implementation
displayed.
5. Testing and Integration Phase: Beforehand the database is verified, the program must
be free from errors this is a necessary testing to find errors that may occur as in the
language errors, logic errors and error analysis program. Tests that are performed on the
system Car Rental System application include the entire menu of programs, processes
applications, and preparing reports.

16
Figure 1.4 – Represents Car Rental Systems Test Results

17
Database Design: after manipulating the system it also results to arranging the system whereby experts
plan the data base using the device of Entity Relationship Diagram (ERD) that depicts the association
between substances that exist in DFD [21] [22] [23].

Figure 1. 5 Entity Relationship Diagram Car Rental System

Citation - Olama, M. (n.d.). Development of car rental management information system. Retrieved from
https://www.academia.edu/5840265/Development_Of_Car_Rental_Management_Information_System

18
CAR RENTALS THAT HAVE BEEN ESTABLISHED

Suria Car Rental & Tour

Suria Car Rental and Tour Sdn TOUR Bhd (SCR and) has been submitted in offering particularly
incredible Budget Car Rental assistance and agreeable Malaysia Car Rental Services for both
homegrown and global explorers [6]. SCR center around conveying client situated administrations.
In other word, they center round clients' requirements and lease a vehicle custom-made to their
necessities. Their way of thinking is reflected in the administrations they offer, whereby they give
Budget Car Rental and Cheap Car Rental in Malaysia with amazing vehicle condition and great
help which not just gathering client’s transportation needs yet save their pocket. SCR have a broad
decision of Budget Car Rental arrangement and administrations in Malaysia including single
excursion to/from the air terminal inside Klang Valley, day by day driver rate, in Kuala Lumpur or
out of the town, conservative, family or extravagance vehicles, and the sky is the limit from there!

19
Figure 1.1 shows The home page of SCR & Tour website

Figure 1.2 shows the booking form of SCR & Tour

20
Fasim Rentals
Fasim rentals are web-based system that was developed by Mike Aric who was a student of Ahmadu Bello
University Zaria. According to Mike, the system was developed for a company named “Fasim rentals”. The
methodology used in developing the system was incremental methodology which helps in developing
software quickly during software life cycle. In addition to the methodology used, java programming language
was the language used to develop the system. Fasim rentals were running all their organization activities
manually before they began using the system. Some features of the system include managing customer
vouchers, transaction history, reports, reservation, online payment and more.

.WS RENT-A-Car
WSRAC is authorized by the Ministry of Culture, Arts, and Tourism to complete a vehicle rental business in
Malaysia. Their administrative center is situated at Kuala Lumpur. They offer vehicle rental and vehicle
renting administrations in significant urban communities and air terminals all through Malaysia. They offer
wide selection of vehicles, from affordable to extravagance vehicles, vans, MPV and SUV for their clients to
pick the one and generally proper for their excursion and voyaging comfort.

Figure 1.3 shows The home page of WS-RENT-A-Car

21
Link - Retrieved from https://www.wsrentacar.com.my/kl-car-rental- klia-klia2/

22
Link - Retrieved from https://www.wsrentacar.com.my/kl-car-rental- klia-klia2/

Figure 1.4 shows The booking form of WS-RENT-A-Car

 Nova Car Hire -The site novacarhire.com was revamped and launched in 2012 and now offers the
best vehicle rental shopper experience in the market [8]. They have become stronger to strength over
certain years because of their emphasis on their clients. Their persistent cycle of progress and
development guarantees. They offer their clients the best reserving and vehicle enlist experience
conceivable. Nova has had over 1.5million fulfilled clients and sold over 12million rental days across
the world. Development of car rental management information system ... (n.d.). Retrieved 2011from
https://core.ac.uk/download/pdf/11734590.pdf

23
Figure 1.5 shows The home page of Nova Car Hire

Retrieved from https://www.novacarhire.com/about/about-us.html

 About Us (2020,) https://www.scr.com.my/about-us/

 Few words about us (2020). Retrieved from https://www.wsrentacar.com.my/kl-car-rental-

klia-klia2/
 Qurratul, A. (n.d.). Development of car rental management information system (case study: Avis
indonesia). Retrieved 2011, from https://core.ac.uk/reader/11734590
 Waspodo, Bayu, Aini, Qurrotul and Nur, Syamsuri. (2011). Development of Car Rental
Management Information Systems (Case Study: Avis Indonesia).

24
Summary
This chapter shows that there is increase in the development of car rental industry, many
companies are established and digital innovation has extremely changed the way car rental
companies are running their businesses. In addition, customers can now rent a car without
suffering from manual registrations, booking and payment. Car rental companies also can keep
track of all their data without encountering any problem. Customer can also drop-off a car at any
location, provided there is a branch of a particular car rental company in that location.

25
CHAPTER 3: REQUIREMENTS ANALYSIS AND DESIGN

Overview

This chapter defines the analysis and intention of car rental/chauffeur hiring system. The
methodology used in the system development. The requirements of the car rental/ chauffeur
hiring system includes functional and non-function requirements. The tools that are used when
developing the system are identified, which consists of hardware and software tools as well as
the technologies used.
In addition, this chapter describes the model of the system which is a basic, wide-ranging, and
constant concept of the system which is developed to enable better understanding of the system
using DFDSs and UML diagrams. Finally, this chapter displays the system design; the system
architecture, the user interfaces, and the database design which are the physical view of the
system.

Proposed Methodology
Methodology in information system development is the process of dividing software
development work into distinct phases to improve design, product management, and project
management. Some of the methodologies used in system development include agile development
methodology, water fall development methodology, rapid application development methodology,
prototyping methodology and spiral development methodology. Each of these methodologies are
chosen based on the nature of the system to be developed or the information technology project
to be carried out and the stakeholders of the system.

Approach to Chosen Methodology/Methods

Prototyping methodology has six software development life cycle (SDLC) phases, at the first stage, all the
system requirements are gathered from the stakeholders by interviewing them, then the design of the system
is made, which shows a preview of the system to the stakeholders. The followed approach after design is
building the prototype. The prototype is built and its presented to the stakeholders for initial evaluation in
order to help find the strength and weakness of the prototype.
The prototype is refined according to the stakeholder’s feedback and suggestion, if the initial prototype meet
their needs then next prototype will be built and presented to them otherwise requirements will be clearly
26
gathered and reviewed, then another prototype will be built for them to evaluate. Repeatedly, that is how the
chosen methodology has been approached till the end of the project.

Tools and Techniques

The following tools are used throughout the project
•A computer with 1.6Ghz of processor, 8GB of RAM, and 1TB of Hard drive
•UML Diagrams for the analysis and modeling of the system
•Microsoft office programs for necessary documentations and visualizations
• Android Studio
• Visio Based on application architecture analysis.
•Emulator.
•SQLite
Technologies used in this project are as follows
•Asp.Net Core with C# programming language
•Bootstrap CSS
•JavaScript

Requirement Analysis
At the end of the requirement analysis process, the expected deliverable is System Requirement
Specification (SRS), which describes the behaviors and features of the system. It also contains
the list of requirements of the system as well as the diagrams.

Requirement list are the list of functions that a system must possess. Requirements are of two
categories, which are functional and non-functional. Functional requirements are the requirement
that the stakeholders need from the system, how is the system going to be operated and what the
system should have.

Non-functional requirements are the requirements that specify the criteria that can be used to
judge how the system operates.
The diagrams, which are also known as system model are the abstraction of the system. Each
model is presenting a particular view of the system. The diagrams also show the relationship
27
 between the system and the external entities.
Requirement Specifications
The two tables below contain the functional and non-functional requirements

Functional Requirement Specifications

Table 2. 1 Functional Requirements

Req. Description Type

No.
R-1 A customer should be able to register with email Functional

And phone number

R-2 A customer should be able to view the details of a Functional

particular car
R-3 Functional
R-4 The system should show available cars to the Functional
customer

during reservation
R-5 The system should allow customer to delete Functional
reservation and return car back
R-6 The system should be able to display the summary Functional
of successful reservations.
R-7 Admin should be able to login to the system using Functional

his/her username and password

R-8 The system should allow new user account to be Functional
created by the Admin

28
R-9 The system should allow users to logout Functional
R-10 Customer can select a car from the car list Functional
R-11 The system should allow users to select car of their Functional
choices.
R-12 The system should allow admin to modify or Functional
update any car information when there is need for
that
R-13 Customer should be able to display all the lists of Functional
cars
R-14 The system should be able to save all changes Functional
made by admin
R-15 The system should be able to print the summary of Functional
all successful rents

29
Non-Functional Requirement Specifications
Table 2. 2 Non-Functional Requirements

Req. Description Type

No.
R-1 Transactions should be securely made and users Security
data

should be protected from attacks

R-2 The system should be trusted and relied by the users Reliability
R-3 The system should be easy for the customers to use it Usability
R-4 The system should run on any hardware with any Portabilit
kind of browser. It should not conflict with other y and
processes compatibility
within these environments
R-5 System should keep running when its launched Performance
unless

there is an intentional shutdown of the system

30
 System Design
Use case Diagram
Below use case diagrams show the interaction between the external entities and the system.

Figure 2.0: Main phases in prototype method

3.0 Initial Requirement

Use case diagram is used to show the relationship between the actor and the use case.
Figure 2.1 shows the use case diagram for Car Rental Application in UTM.

31
 Table 1: Description of component in Use Case diagram

DEFINING USE CASES, ACTORS WITH THEIR FUNCTIONALITIES

USE CASE ACTORS DESCRIPTION

Share content  Customer This use case allows the user to

share information from the
application through social media.

Manage Profile  Service Provider Service Provider can view and

update their profile.

Login  Service Provider Users must login to application

 Service Provider

Logout  Customer Users can logout from application

 Service Provider

Manage Car  Service Provider This use case allows service

providers to view, add, edit and

32
 delete car information.

Comment And Rate  Customer Customers can comment and rate

car based on the performances of
the car and quality of the service.

View Car Information  Customer This use case allows customers to

view cars or services provided by
car rental company.

Each component in the use case diagram has its own function as summarized in Table

Descriptions of outputs/inputs/performance/security or controls.

This section describes system inputs and outputs as objects interact with the car rental system.
Member Registration: The customer enters the username and password, which give a chance for the system
to confirm whether there is an existing user with merging credential. If yes the user is logged into their
account and if not the user is asked to check the username and password or request for a new password. The
user is also given a chance to create an account if they are not registered. The system checks username, email
password, and phone numbers as mandatory fields.
LOGIN
The Customer enters email and password to check if this exists int the database of individuals registered if yes
it logs in. If no it shows a message user not identified so one has to use correct information which was used to
register.
Car Reservation: Users must be logged in to access this page. On this interface, customers select a pick-up
location, pick-up date, select a return location, return dates, select a vehicle, and enter payment details. Upon
returning the vehicle users get an email confirming that they have returned their rented car. This email
encourages them to leave a review about their experience. If the customer has a mobile app, they get instant
notification about this on their phone and can leave a review instantly. The customer picks the car from the
specified outlet on the set pick-update.
Customer Feedback: Customers log in to their accounts and select their rentals history with a pending

33
review. They will be prompted to leave feedback which is stored along with the car rental history. On the
other hand, the staff will get a notification about the customer’s feedback, when any one of the staff replies to
the customer’s feedback.
Rental Car Return: Customers returns a car to the designated outlet, the official checks whether the car is I
good condition, and confirms that the customer has returned the car. The system checks if the return date is
overdue and updates the database. This makes the car available for another customer to request.
Report Viewing: The admin user logs in the system and specifies the report he wants to view, the system
retrieves the report and outputs the report. The user will have the option of saving it as a pdf or printing.

Figure 2. 6 Admin use case diagram

This figure models the interaction between the admin and the system. In the diagram, from the
left is an admin actor. Within the rectangle which represents the system are what are called use
cases. The use cases are basically actions that an actor can perform in the system. From top left
within the system is login use case, before login in to the system, the details for logging in need
to be valid, which is represented by the valid use case at the top-left corner.

34
Figure 2. 7 Customer use case diagram
This figure models the interaction between the customer and the system. Within the rectangle, all
the use cases are the actions that the customer can perform with system. This figure shows the
overall actions that can be performed by the customer, staff, and the admin, which are
represented by what are called use cases. From left-side of the system are customer and staff
actors, while from the right side of the system is an admin actors.

Class Diagram

This figure represents the class diagram of the system which shows the classes, including their
attributes and operations. It also shows the relationship between the entities. From the top-left is
a user class which has three subclasses Admin, Staff and Customer that inherit the attributes of
the user class. The empty arrows that mapped from the three subclasses to the superclass show
the

35
inheritance. Every line that is drawn from a single class to another class in the diagram is called
Association. The shaded arrows from the payment and rent class to Customer class show that
payment and pent cannot exist with Customer, likewise rent and report.

Figure 2.8 Entity Relationship Diagram (ERD)

The Car Rental System ERD above shows the entities and the relationship between them. Each
and every entity has its own attributes. From the left, there is a many-to-many relationship
between Customer entity and Car entity. In this case, a Customer_has_Car entity is introduced
in-between the two entities which is called a Bridge Entity to solve the many-to-many
relationship. Each and every entity in the ERD above has a primary key; which is an attribute or
set of attributes that uniquely identify a specific instance of an entity

36
 Activity Diagram
Below activity diagrams model the workflow within a system with the use of activity, action, decision,
etc

Figure 2.9 Registration Activity Diagram

Figure 3.0.1 Shows When Placing an Order for the car Activity Diagram
37
Application Architecture

Figure 3.0.2 Car /Chauffeur System Application Architecture

38
ADMINISTRATION APP ARCHITECTURE

Figure 3.0.3 Admin Application Architecture

39
 Figure 3.0.4 Customer Application Architecture

Customer Application Architecture

The application architectures above give the high-level representation of the system. It also
represents the sub-process, component, and navigation to other parts of the system.

3.0 System architecture and Design

A model-View-Controller (MVC) architecture was used to design the Car Rental Application. This
architecture consists of three main parts, which are model, view and controller. Model is responsible to
managing the data of the application. It will respond the request from the view and controller. On the other
hand, view is the user interface of the application. Lastly, controller is the heart of the application. It will
respond to the input from user, manipulate the information structure in the view and responsible to the
interaction between the models.

REFERENCE

1. Mike, A. (2018).Design and development of online car rental system. Ahmadu Bello
40
 University Zaria.

Figure 3.1.1 illustrates the interface designing of a developed application which shows the booking of a car

41
Figure 3.1.2 shows the booking interface

42
Figure 3.1.3 shows the selection of car category interface.

3.1 Database Design

This logical data model contains all the needed logical and physical design choices and physical
storage parameters needed to generate a design in a data definition language.

Figure 3.1.4 shows the database design output.

43
This is basically used to create a database. A fully attributed data model contains detailed
attributes for each entity. This depicts the entity relationship diagram for the Chauffeur/Car
rental Mobile Application that was developed.

Summary
This chapter shows the analysis and design of the system requirements which are functional and
non-functional requirements, the models and designs of the system that were developed using
different kinds UML diagrams and DFDs. The application would also be developed using
prototyping methodology.

44
CHAPTER 4: IMPLEMENTATION AND TESTING

Overview
This chapter talks about the implementation and testing of the car rental system, the technologies
and tools that were used when implementing the system, the problems and errors encountered
during the implementation, and how the problems were solved. This chapter also describes the
implemented and functionalities of the system.

Development tools and technologies

Listed below are the tools that ware used during the implementation of the project

 A laptop with 1.6GHz clock speed, minimum of 8GB RAM and minimum of 500GB
HDD.

 Android Studio

 Microsoft SQL Server Express

 Emulator
Technologies used are
 Asp.net core MVC

 JavaScript

 Java

 Bootstrap CSS

Implementation Problems/Challenges

During the implementation of this web application, problems were encountered, but were nicely
solved. The problems encountered have to do with both the font-end and back-end
implementation.

Due to time constraint I couldn’t conduct the payment platform with the use of credit card or
paypal information but billing is based on assumption with the use of paster.

45
Testing

This section shows the test carried out in order to check whether the application is error free or
not. Test plan was developed and used which contains all the system functionalities that are
going to be tested in case of any error. System testing also helps to check whether the system
meets its requirements or not. MS-Unit framework is used to test all the functionalities to
confirm if there is error.
User Interface
This is the interface through which customer’s and the staff access and interact with the system. The
following are the designs proposed for the home page.
Home page UI
LOGIN INTERFACE

Figure 4.1 shows the login user interface of the car rental

46
REGISTRATION USER INTERFACE

Figure 4.2 shows the registration user interface of the car rental application for new users which are to
register.

47
BOOKINGS AND CONFIRMATION

48
Figure 4.3 shows the bookings and confirmation user interface of the car rental application for new
users which are to make and confirmation of bookings with a given Booking ID

49
Test Plans

Table 3. 1 Test Plans

Test Suite ID Car Rental System release 1.0 (MTP) 1.0

Test Case ID #1
Test Case Summary The system should allow user to sign up with or without
google
account
Expected Result After signing up, the application should redirect to home
page
Actual Result After signing up, the application should redirect to home
page

50
 Status Pass
Executed by DAVID ANIETIE BASSEY
Date of Execution 12/04/2021
Test Environment Android Studio

Table 3. 2

Test Suite ID Car Rental System release 1.0 (MTP) 1.0

Test Case ID #2
Test Case Summary Does the system allow user to make reservation
Expected Result After making reservation, the application should
navigate to
reservation details
Actual Result After making reservation, the application should
navigate to
reservation details
Status Pass
Executed by DAVID ANIETIE BASSEY
Date of Execution 13/04/2021
Test Environment Android Studio

Table 3. 3

Test Suite ID Car Rental System release 1.0 (MTP) 1.0

Test Case ID #3
Test Case Summary Admin should be able to assign roles to users
Expected Result Users should be able to access some functionalities
based on
their roles
Actual Result Users should be able to right to use some functionalities
51
 based on certain positions.
Status Pass
Executed via DAVID ANIETIE BASSEY
Date of Execution 13/04/2021
Test Environment Android Studio

Table 3. 4

Test Suite ID Car Rental System release 1.0 (MTP) 1.0

Test Case ID #4
Test Case Summary Does the system allow administrator to manage users,
roles,
cars, and reservations
Expected Result Admins should have the capabilities to deal with certain
roles, user’s cars and reservations.
Actual Result Admins should have the capabilities to deal with certain
roles, user’s cars and reservations.
Status Pass
Executed by DAVID ANIETIE BASSEY
Date of Execution 15/04/2021
Test Environment Android Studio

52
Test Traceability Matrix

Table 3. 5 Test Traceability Matrix

Req. No Description Priority Test Test Date Test

Case Result
R-1 The system should HIGH 1 12/04/2021 PASS
allow user to register
with google account
R-2 The system HIGH 2 12/04/2021 PASS
should allow
user to make
reservation
R-3 The system HIGH 3 13/04/2021 PASS
should allow
admin to assign
roles
R-4 The system should HIGH 4 15/04/2021 PASS
allow administrator
to manage users,
roles,
cars, and reservations

53
Test Report Summary
Table 3. 6 Test Report Summary

Summary of Test Carried Results

Tests carried out 4
Tests not carried out 0
Tests passed 4
Test failed 0
Percentage of tests carried out 100%
Percentage of tests not carried out 0%
Percentage of tests passed 100%
Percentage of tests failed 0%

54
User Guide

The user guide describes how user is going to use the system with ease to
accomplish his/her goal, including all the processes involved in operating the
system. The user guide also serves as a short reference to some particular
aspects of the system. The user guide for the application can be found in
Appendix E.

Summary
This chapter shows the implementation of the system, the tools and
technologies used during the implementation, which are asp.net core MVC,
bootstrap, jQuery, JavaScript, HTML and CSS. This chapter also covers the
problems that were encountered during the implementation and how the
problems were solved, test plans, test traceability matrix and test report
summary as well

55
 CHAPTER5:DISCUSSION,CONCLUSION,AND
RECOMMENDATIONS.
Overview
This chapter covers the evaluation of the project, the project conclusion and the project
recommendations. Firstly, it presents the objective assessment which is related with the aim of
the project and also the context of the project which give the general conclusion of the project.
This chapter also discusses the limitations of the project and the challenges encountered. Then,
some of the future enhancements are going to be made as the project got online and started to be
used. This chapter lastly contains the recommendations that are made.
As discussed in chapter 3, the methodology used in developing the software is prototyping
methodology, because it is one of the most important software developments models, it’s the
process of building prototype (which is the first design of the system). Prototyping methodology
allows you to build the first design of your system which will be shown to the system
stakeholders in order to go through the prototype and find their likes and dislikes based on how
the final system will look like. Stakeholders will constantly be going through the prototype until
an acceptable prototype is achieved, which is going to be used to develop the final application.
Objective Assessment
The car rental system has accomplished some its aims, up to this point, the
application:
 Allows users to register with the system
 Allows users to login with the system
 Allows user to return car
 Allows users to select return date
 Can allow the administrator to add and manage users, cars, and records.
 Allows users to view the cars that are added onto the system
 Allows user to print a particular page.
 Enables users to select specific types of car in the system
 Allows search for a record in the system.

56
Limitations and Challenges
 Majority of the cycles that will be completed physically in the organization are broke down and
carried out. In this way, it would be simple for them to utilize the framework than some other
individual external Nigeria. For a client to lease a vehicle, he/she should sign in to their own record,
and visitor should make their own record.

 During the investigation and execution of this undertaking, there are difficulties that were
experienced. While examining the prerequisites of the framework, there was trouble in understanding
what precisely the clients need, since they probably won't know what and how the framework will
resemble.

 Additionally, Due to time limitation I was unable to direct the installment stage with the utilization of
charge card or paypal data yet charging depends on suspicion with the utilization of paster however
this will be added to future upgrade just as different assortments of vehicles and tasks to make this an
adaptable application.

 The difficulties were tended to by the utilization of certain abilities which like; critical thinking
abilities, relational abilities just as basic suspecting abilities to think, take care of issues, and speak
with individuals. Difficulties were additionally looked during the model advancement which didn't fit
the clients; consequently, it must be examined and planned once more.

 Lastly, due to time constraints the addition of drop down menu for drivers was tasking so it will be put
into use for future enhancements because the syntax has to be included in the database and not enough
time to input that and then I will need to re-strategize the flow of codes in order not to mess up the
project.
Future Enhancements
 Some enhancements are supposed to be made as this project is launched, it includes
 Application should run on other mobile phones. e.g. apple

 Addition of card/paypal payments.

57
 Nowadays, the number of mobile phone users is very high than computer users most especially
in Nigeria. The application is going to be in android and iOS platforms and also developed in
order to increase accessibility and inclusiveness.

 Staff Interface

 Geo-fencing and remote car deactivation

 Addition of drop down menu for various drivers with ids.

.Recommendations
The car rental/chauffeur hiring services need to open branches in some other states
within Nigeria. The project should have a cloud storage for backing up user’s data
because the cloud storage can save costs, protects user’s data from malware, regulatory
compliance, and data tiering for cost savings. Also, the web-based car rental system
should also be developed in form of mobile application, to help improve usability for
mobile phone users.

6.0 System Evaluation And Discussion

Car Rental/Chauffeur Mobile Application for Android-based mobile is a cross-platform mobile

application. This application involves two main actors that are customer and service provider who are
mostly UTM student.

This application allow service provider to manage their car rental information more systematically.
They can easily add, edit, delete or view any info regarding the car that they put on rental. On the other
hand, customer can view the information on car rental including, any comments and rental rate per car.
Besides, customer can select specific car to check the details information about the car, which he or she
interested to rent. The displayed info including the average rating of the car by previous customers, car’s
specification and comments made by the customers on the service provided.

A software testing was conducted to make sure the developed mobile application manages to solve
the related problem as discussed in the previous sub-topic. We do the testing using two methods, which are
58
 user acceptance testing and black box testing.

7.0 Conclusion
This application manages to achieve the entire objectives, which are stated in the first
chapter. The first objective is to analyze the problem related to car rental management in
UTM by distributing a questionnaire among the UTM students. The analysis of the
problem can be referred in Software Requirement Specification (SRS) document. Then,
designing a suitable application based on the collected requirement. The detail of the
application design can be refer in Software Design Description (SDD). Next, implement
the Car Rental Application for Android. The application has been developed based on
the design in the fourth chapter. Lastly, conducting a test using two testing method
which are user acceptance and black box testing.

59
 REFERENCES
1. Car Renting Its Development And Future (2020).Retrieved from

https://www.automotive-fleet.com/147063/car-renting-its-development-and-future

1. “History–The beginning of a movingtale”, Sixt (2020).Retrieved from

https://about.sixt.com/websites/sixt_cc/English/0/about-us.html#HISTORY

2. “Joe Saunders, Omaha Innovators”(2020).Retrieved from

http://www.douglascohistory.org/

3. “Walter L. Jacobs,88;Rent-a-Car-Pioneer”(2020).Retrieved from

https://www.latimes.com/archives/la-xpm-1985-02-08-me-4716-story.html

4. Mike, A. (2018). Design and development of online car rental system. Ahmadu Bello
University Zaria.
5. About Us (2020,) https://www.scr.com.my/about-us/

6. Few words about us (2020). Retrieved from https://www.wsrentacar.com.my/kl-car-

rental- klia-klia2/
7. About us (2020). Retrieved from https://www.novacarhire.com/about/about-us.htm

8. Waspodo, Bayu, Aini, Qurrotul and Nur, Syamsuri. (2011). Development of Car Rental
Management Information Systems (Case Study: Avis Indonesia).
9. Sheth, J.. (2016). Car Rental System. 10.13140/RG.2.2.12716.87680.

10. Mcleod, R. and Schell, Jr. G. P.(2007). Management Information System, (10th Edition). India:
Pearson Education, Inc.
11. Damayanti, Y. (2005). “Car Rental Information System Design using Microsoft visual
basic version 6.0”. Gunadarma University.
12. Cahyanto, M. R.T. et al. (2010). “Car Rental Management Information
System CV transport with Java SE and MySQL based OOP”
13. Yodiyanto. (2006). “Analysis and Design of Web-based Car Rental and Travel

Transportation Information Systems at PT”. Bina Nusantara University.

14. Sar, R. D. (2011). “Building Application System Car Rental Reservation and Payment.

60