ONLINE CAR RENTAL SYSTEM

(A CASE STUDY OF CAR HIRING)

LUKAS MUNENE NGARE

BBIT/601J/2018
Supervisor
DR.MATHEW EGESA

A RESEARCH PROPOSAL SUBMITTED TO THE DEPARTMENT OF MANAGEMENT

SCIENCE IN FULLFILLMENT OF THE REQUIREMENT FOR THE COMPLETION OF
THE COURSE IN BACHELOR OF BUSINESS INFORMATION TECHNOLOGY AT THE
TECHNICAL UNIVERSITY OF MOMBASA.
DECLARATION
I declare that this proposal is my original work and has not been previously published or submitted
elsewhere for marking. I also declare that this work contains no material written or published by other
people except where due reference is made and author duly acknowledge.

LUKAS MUNENE NGARE

Student numbers: BBIT/601J/2018

Signature ………………………………… Date…………………………………

DR MATHEW EGESA (TUM)

Signature …………………………………. Date……………………………………

 DEDICATION
I dedicate this piece of work to my lovely family who have supported my education and also
friends. Thank you so much.

ACKNOWLEDMENT
I would like to express my sincerest gratitude to my supervisor DR MATHEW EGESA for
guiding us through research methods which enabled us come up with the idea of what to do in
the project. Also for taking us through the necessary steps that has helped us come up with a
successful project as I have learned more about the project. In the end I would like to also thank
my parents as without them would have not achieved anything. God bless you all.
ABSTRACT
The online car rental system is a website for enabling persons be able to rent cars at any given time. This
project has been developed to carry out the processes easily, quickly and to meet the required
expectations of the customer. The project is set to replace the perception of relying on people to bring
customers to you thus it will be easier for them to reach out without having to pass through a
middleperson. I have used the prototyping model to develop the system. This will ensure customer
satisfaction as the requirements will be met which is the expected output of the system.
Table of Contents
ONLINE CAR RENTAL SYSTEM.........................................................................................................1
DECLARATION.......................................................................................................................................2
ABSTRACT...............................................................................................................................................4
1 CHAPTER ONE: INTRODUCTION..............................................................................................7
1.1 Introduction...............................................................................................................................7
1.2 Background of the study...........................................................................................................7
1.3 Problem Statement....................................................................................................................8
1.4 Objectives of the study..............................................................................................................8
1.4.1 General objectives..............................................................................................................8
1.4.2 Specific objectives..............................................................................................................9
1.5 Research Questions....................................................................................................................9
1.6 Significance of the study............................................................................................................9
1.7 Limitations of the study...........................................................................................................10
1.8 Scope of the study....................................................................................................................10
1.9 Organization of the study........................................................................................................11
References.................................................................................................................................................11
2 CHAPTER TWO: LITERATURE REVIEW...............................................................................12
2.1 Introduction.............................................................................................................................12
2.2 Theoretical Review..................................................................................................................12
2.3 Similar Systems........................................................................................................................12
2.3.1 Case study 1: My Hire car rentals..................................................................................12
2.3.2 Case Study 2: Houston Luxury Car Rental...................................................................13
2.4 Critical Review and Research Gap Identification.................................................................14
2.5 Chapter Summary...................................................................................................................14
References.................................................................................................................................................15
3 CHAPTER THREE: METHODOLOGY......................................................................................16
3.1 Introduction.............................................................................................................................16
3.2 Research design........................................................................................................................16
3.2.1 Target population............................................................................................................16
3.2.2 Sample size.......................................................................................................................16
3.2.3 Data collection procedures and instruments..................................................................17
3.3 System development methodology..........................................................................................17
 3.3.1 Methodology justification................................................................................................19
3.3.2 Non- functional Requirements........................................................................................20
3.4 Unified Modelling Language...................................................................................................21
3.4.1 Use Case Modelling..........................................................................................................21
3.4.2 Activity Diagram..............................................................................................................22
3.4.3 Sequence Diagram...........................................................................................................23
3.4.4 Class Diagram....................................................................................................................25
3.4.5 Deployment Diagram........................................................................................................25
3.5 Database Design........................................................................................................................26
3.5.1 Table Design.....................................................................................................................26
3.5.2 3NF Normalized Form.....................................................................................................27
3.6 Testing Design..........................................................................................................................28
3.7 Chapter Summary.....................................................................................................................30

Figure 1:MyHire Car Rental..................................................................................................................13

Figure 2:Houston Luxury Car Rental....................................................................................................14
Figure 3:RAD...........................................................................................................................................17
Figure 4:Prototyping Model...................................................................................................................18
Figure 5:Use Case Diagram....................................................................................................................21
Figure 6:Activity Diagram......................................................................................................................22
Figure 7: Sequence Diagram...................................................................................................................23
Figure 8: Class Diagram.........................................................................................................................24
Figure 9:Deployment Diagram..................................................................................................................25
Figure 10: Test Cases..............................................................................................................................28
 1 CHAPTER ONE: INTRODUCTION
1.1 Introduction
The chapter shows the overview of contents. It entails the background of the study which gives
the specifics of the problem and allows you to give the history of the case (Case, 2016) and to
give citations and authoritative sources building the case, the problem statement shows what the
problem is and what the research is seeks to solve giving relevant citations of what has been
done and what should be done. The objective of the study has general objectives and specific
objectives. The general objective gives the main goal of the study while specific objective gives
the specifics of what the study aims to achieve. The Research Questions are based on the
research questions and should not be Yes or No based. The significance of the study justifies and
gives the benefits of the study (Salter, 2001). The limitations of study show the flaws the
research could go through to make it not possible. The scope of the study tells the boundaries
with which the project will be performed based on the geographical, content, timeframe and the
concept.

1.2 Background of the study

The earliest records of car hire can be traced as far back as 1904, when a bicycle shop in
Minneapolis started offering cars for rent. A few years later, the German company Sixt was
established in 1912. It first started off with three cars for rent and quickly expanded. In 1915, in
Omaha, Nebraska, Joe Saunders had a eureka moment and realized that nobody in Omaha
offered cars for renting. He employed only one salesperson, Frank Arndt, from Germany, and
started renting out Arndt’s Model T. This venture turned out to be so successful that by 1917, he
was renting out 120 of these. He named the company ‘Saunders Drive-It-Yourself System’ and
put an advertisement in the local paper. Joe Saunders’ three brothers and father started taking
part in the business and by 1927, the Saunders System had branches in over 85 cities. This took a
great part in influencing other people to venture in car rental business. As the automotive
industry progressed and expanded, so did car rental companies. In the UK, Arnold Clark Car &
Van Rental was established in 1963. It was one of the first British companies to offer car hire
and now has a fleet of over 6,000 vehicles. In the 21st century, rental companies have
mushroomed all over the world as demand is on the rise. As the world becomes more globalized,
people travel at an unprecedented rate and they hire cars, vans and other vehicles more often than
ever.

1.3 Problem Statement

With the volume of cars increasing by the years, the car rental business has a lot of potential.

People travel at an unprecedented rate and they hire cars, vans and other vehicles more often

than ever. However, there has not been a system that allows any person to rent a car without

having to look for the dealers in person which is hard. Furthermore, owners of the cars for hire

wholly rely on specific people to bring customers to them more of “I KNOW A GUY WHO

KNOWS A GUY” which makes their businesses be limited. The system enables the people who

are on the verge of starting to venture on the car rental business a platform to which they will be

able to get customers quickly and more so have as many customers as possible so as for the

business to be successful. It’s not only for the ones beginning the business but also for the ones

who have been in the game for some while but feel that there is need for more customers.

1.4 Objectives of the study

1.4.1 General objectives

To create a platform where people can freely and easily link up with the various car rental business
people so as to reduce the struggle of reaching them when there is need for them to rent a car when in
need of travelling.
1.4.2 Specific objectives
 Faster Process – To make sure a user gets his desire car as early as possible; the car
rental system will provide a faster response to complete the process.
 Minimize paperwork – As all the system is computerized, there is no need to fill any
application form for renting purpose. So, the paperwork will be very less.
 Enable people get the desired car they need for their use.
 Ease the struggle to reach out to a car hire business person.
 Enable customers be able to reserve cars of their choice.

1.5 Research Questions

1. How will customers reach out to the car rental business person easily?

2. For how long will it take for the car rental person reach out to the customer?

3. Will the customer get his desired car?

4. Will there be need for paperwork in renting the car?

5. Will the customers be able to reserve the cars of their choice for hire?

1.6 Significance of the study

The car rental system will be beneficial in the following ways:
It will help the car rental business owner to advertise his/her business through showing the cars
available and their prices.
It will ease the reaching out of the customer to the car rental person.
It will help the car rental business owner to transition from paper recording methods to a
database and will help in storage of the data.
It will help the customers in reserving their desired cars for hire.
 1.7 Limitations of the study
i. Data Collection Process
The data collection process may have been flawed because it is based on obsolete data
and a certain population which is a biased process. This study might not be good on areas
where the population is sparse, computer illiterate, an urban setting and a not so spending
population based on the data collection process.
ii. Sample Size
This study seeks to investigate and develop a plan for Mombasa County, Tudor area
issues and the challenges that affect the car rental business around that area. This might
not be the case across the other parts of the country depending on the population present,
level of literacy and their occupation. This could give a false impression due to the issues
addressed.

1.8 Scope of the study

This study aims at the development of an online car rental system whose focus is on car
owners and the customers. It aims at advertising cars provided by a car rental business
person and the pricing of the various cars for hire as well as reserve them.

1.9 Organization of the study

Chapter 1 focuses on background of the study and its problem statement. It also looks into the objectives;
specific and general objectives, its scope, significance and the limitation of the study. Chapter 2 discusses
the literature review that gives a theoretical outline theory of this study. It also provides a review of
related work and similar projects. Similar and existent systems are provided in this section to provide a
comparison of system effectiveness and user friendliness. Gap identification, summarizes and critical
review which are also highlighted in this section. Chapter 3 focuses on explaining the materials, tools,
design principles employed throughout the design and technology and the implementation of this project.
It also provides a manual like the explanation of how testing design, design flow is enacted, sample size,
requirement analysis and the target population will be discussed here. Chapter 4 will focus on my project
findings and discussions.
Chapter 5 will concentrate on conclusions, recommendations and suggestions for further study.

References
Case, D. O. (2016). A survey of research on information seeking, needs, and behavior.
Salter, A. J. (2001). The economic benefits of publicly funded basic research: a critical review. .
 2 CHAPTER TWO: LITERATURE REVIEW

2.1 Introduction
In this chapter, Theoretical Literature of the problem your system is solving is given; the
theories, concepts and their definitions should show how they are relevant to the problem you
seek to solve, Similar systems show the difference between these systems and your proposed
system by using snapshots of the existing systems as evidence of their existence should be from
global to local systems ,Critical Review and Research Gap Identification show the uniqueness of
the system you are building and should be seen as clearly filling the gap to avoid looking like
plagiarism. Chapter Summary highlights keys issues raised and facts established, reviewed issues
that show up are also indicated.

2.2 Theoretical Review

It’s very common that for a successful business, there should be ease of reach (Ranganathan, 2002). The
system lies on this aspect in that for many upcoming or the ones already in the game car hire business
people, there is too much relying on middlemen to search customers for you. This can limit the number
of customers as it is based on luck. The system ensures one can reach out anywhere and anytime when
in need of renting a car for a particular reason and it also maximizes the profits. The system also helps
the customers choose the cars to their liking giving them the prices for each. The system is set to
eradicate all the negative aspects to the car rental business people.

2.3 Similar Systems

2.3.1 Case study 1: My Hire car rentals.
My hire car rental is a system built to enable the business owner market his car hires services in
Kenya. It aims to digitize the car rental experience through an integrated, user-friendly web-
based software and a new-age customer booking app powered by MyHire-
Connect® technology and Artificial Intelligence.
Figure 1:MyHire Car Rental

2.3.2 Case Study 2: Houston Luxury Car Rental

This is an online car rental system located at the United States of America. It is a thriving
business as it for the white-collar job people. with over 15 years of experience, the founders have
seen the right and wrong in the rental vehicle industry. When renting a vehicle, they want to
provide a moment for you to truly enjoy. They are changing the industry by giving clients not
just a vehicle to drive, but an experience to remember for the rest of their lives. The setback
about it, it is that its limited to a category of people thus not every person can be able to acquire
their services.
Figure 2:Houston Luxury Car Rental

2.4 Critical Review and Research Gap Identification

The proposed online car rental system is developed on the basis of ‘EASE OF REACH’ and it also gives a
human friendly approach where the customer has a place to book the car they want offered to
them. The system also aims at maximizing profits of the business owner which is by eliminating
the middlemen who tend to connect customers to the car business owner. This is because the
middlemen need to be tipped off thus no full payment to the business owner.

2.5 Chapter Summary

The Literature Review gives the conceptual framework which gives theories and concepts of the
studies done in relation to your system. Similar systems done across the world inform on the
Do’s and Don’ts of the proposed system by exploiting the weaknesses of those applications to
develop a customer friendly experience and the customer to be in control of the decisions they
make upon the service delivery as well as the owner of the premise. The system has borrowed a
lot from HERTZ, US based application that is based on booking services on cars for hire.
References
Case, D. O. (2016). A survey of research on information seeking, needs, and behavior.
Ranganathan, C. &. ( 2002). Key dimensions of business-to-consumer web sites. Information &
management.
Salter, A. J. (2001). The economic benefits of publicly funded basic research: a critical review. .
 3 CHAPTER THREE: METHODOLOGY

3.1 Introduction
This chapter involves the research design in the study, analysis of the methodology technique that was
used to aid the development of the proposed system. It involves design method to be used, fact finding
approaches – diagrams and database design, research design, target population, the sample size and
sampling techniques, and methods used to collect data and analysis. It simply involves the development
process and procedures that were used in the development of the Car Rental System.

3.2 Research design

The study employed a descriptive survey and exploratory design sampling techniques.
Descriptive and exploratory design is regarded as the most appropriate research design to
measure perceptions of the respondents in a study. It enables the researcher to collect a cross-
sectional data important for comparative analysis. In addition, they are advantageous in terms of
cost, extensiveness, flexibility, dependability among others. Sampling is a technique where one
selects a group of subjects for study from a large group. The probability sampling design
technique is used by simple random method as it is simple, not biased and not time consuming.

3.2.1 Target population

The study targeted both the members of the public wishing to book or hire car for travelling
purposes and the owners of the cars who want them rented.

3.2.2 Sample size

For an efficient research operation, I collected data necessary for analysis from the county city
(outside TUM). The respondents from the sample population were the individuals majorly from
showrooms who not only sell cars but also provide hiring services, owner of the showrooms and
the customers who were present at that time at the showroom place.
3.2.3 Data collection procedures and instruments
This section spotlights how data was collected from the users of the system. The data collection
techniques used included the following:
a) Questionnaires
Questionnaire is a set of printed or written questions with a choice of answers, devised for the
purpose of survey or statistical study. The questionnaire administered contained both closed-
ended questions and open-ended and were hand-delivered to the target group. This method
provided more information from various individuals under my study and offered greater
flexibility as it had the opportunity to restructure questions. This technique was most preferred
because it provided the people with opportunity to express their views with regards to how
services are being provided and their expectations suppose a new system was implemented.
b) Secondary Data Collection
I collected this data from existing sources e.g. books, internet and customer files as well as
statistics provided earlier by other researchers and analysis. It is from that data that I afterwards
compared with the primary data and made a final decision and conclusion.
c) Interviews
Face-to-face interviews were used to collect data from the target population as it provided a clear
and explanatory information. Interviews were used to collect data from the staff and the
customers.

3.3 System development methodology

The methodology used was Prototyping. Prototyping, also known as heuristic development,
which is an incremental and iterative process of developing a system through controlled trial and
error with the creation of models/prototypes which can be tested. This model or a program is not
based on strict planning but is an early approximation of the final product which is flexible to
change. A prototype act as a sample to test the process. This type of methodology is employed
when the customer requirements are expected to change during the development process, and
when it is very difficult to obtain exact requirements from the customer while making the model.
User keeps giving feedbacks from time to time and based on it, a prototype is made. Completely
built sample model is shown to user and based on this feedback, the SRS (System Requirements
Specifications) document is prepared. After completion of this, a more accurate SRS is prepared,
and now development work can start using Rapid Application Development (RAD).

Figure 3:RAD

Phases of prototyping methodology

1. Requirement Collection: In this phase, the requirements for the development process are
identified and brought together. Users, managers, and IT specialists discuss and agree on
business needs, project scope, constraints, and system requirements. This process ends when
there is a mutual agreement among the parties.
2. Feasibility Study: Is an analysis of the ability to complete a project successfully, taking into
account legal, economic, technological, and scheduling and other factors. The feasibility study
focuses on helping answer the essential question of “should I proceed with the proposed project
idea?” All activities of the study are directed toward helping answer this question.
3. Develop Prototype: In this phase, the software engineers build a sample model to test the
concept to be replicated.
4. Prototype Testing: Here, the prototype that has been developed tested with the intent of
finding defects before the system goes live. The main aim is to experience some aspects of the
service idea with customers, stakeholders or professionals in order to improve the solutions
before they are realized.
5. Customer Evaluation: The prototype developed is then presented to the customers and other
important stakeholders in the project. The feedback is collected in an organized manner and used
for further enhancement in the system under development.
6. Design: In this phase the architecture is established. It starts with the requirement document
delivered by the requirement phase and maps the requirements into architecture. The architecture
defines the components, their interfaces and behaviors.
7. Coding: The coding phase of the software life-cycle is concerned with the development of
code that will implement the design. This code is written is a formal language called a
programming language. The goal of the coding phase (development of software) is to translate
the design of the system into code in a given programming language.
8. Testing: Software/System testing involves the execution of a software component or system
component to evaluate one or more properties of interest. In this phase, an investigation is
conducted to provide stakeholders with information about the quality of the product or service
under test. The product is tested to confirm its quality.
9. Installation & Maintenance: Here, the system is handed over to the users. This is performed
when the system or software passes the testing phase successfully. Software can be installed,
modified, updated to a new version, or removed.
In the maintenance stage, the system is assessed to ensure it does not become obsolete. Here,
changes are also made to initial system. It involves continuous evaluation of the system in terms
of its performance.

Figure 4:Prototyping Model

3.3.1 Methodology justification

Prototyping is chosen because of the following advantages it has over the rest of the
methodologies
1. Flexibility: Prototyping allows changes at every stage of development. In waterfall
once a phase is complete no changes can be made. Also helps to eliminate
ambiguities and improve accuracy in interpretation of system requirements and
functionality
2. Code re-use: Prototype methodology allows the re use of the codes used in
developing other systems.
3. Reduced Risk: Prototyping method has a high amount of risk analysis. It reduces
risk of failure, as potential risks can be identified early and mitigation steps can be
taken.
4. Reduced Time and Cost: Prototyping method is easy to manage and helps the
developer to estimate development costs, timescale, skills and potential resource
requirements.
5. Involve user feedback and help to do multiple-test. It’s a key factor to iterate and
update. It gives the client and end-user a greater sense of involvement, ownership
and a better appreciation of the final solution
6. Chance of success: In waterfall there is lower chance of success since it is a
traditional method while in prototyping method the project’s success is highly
dependent on the risk analysis phase.
7. Simplicity: Prototyping method is simple and easy to use compared to spiral.
8. Expertise requirement: Lower expertise is required in prototyping method since it is
an easy to use and understand while the spiral, Rad Case and other methods requires
high specific expertise.
 3.4 Chapter Summary

In this Chapter, much about data collection procedures, implementation of the proposed system
and database design has been covered. System development methodology and the justification
have also proven on why it is profitable to adopt the new system once deployed.
CHAPTER 4: ANALYSIS AND DESIGN
4.1 Introduction
This chapter contains the technical approach for analyzing and designing the system as well as
using visual modeling of how the system will look like.
4.2 Functional Requirements
4.2.1 Hardware Requirement
The system is based on using the following hardware specifications
 A laptop having the following specs;
o 8GB RAM
o WINDOWS 10 PRO
o 700GB ROM
o 4 LOGICAL PROCESSORS
o 1.9GHZ PROCESSOR
4.2.2 Software Requirements
The system is based to have the following software specifications;
 XAMPP
 VISUAL STUDIO
 BROWSER(CHROME)
The languages used in writing and designing the system are;
 PHP
 MY SQL
 CSS
 HTML
 JAVASCRIPT

Functional requirements mainly deal with explaining what has to be done by identifying the
necessary task, action or activity and functionalities the system should provide to users and the
tasks that must be accomplished. This web-based car rental system enables customers book or
reserve cars for future use, helping them view the different types of cars and the prices for each
of them.
 Function Requirement Descriptions
admin interface  View registered users or clients
 View booked cars
 Approve or decline the bookings made
 Manage the pages of the system
 List the available vehicles for renting.
User interface.  Login into the system by signing up
 Book the vehicles of their choice
 View the different prices of the vehicles
 Log out the system.

3.4.1 Non- functional Requirements.

Nonfunctional requirements are criteria used to describe the operation of the system, rather than
specific behaviors. They ensure the effectiveness and usability of the system and failing to meet
any one of them can lead to failure of the system. They include;
i. Security- The system should provide authorized access to the system, users will login to
their accounts only if the password is correct. The data will be confidential and safe since
all passwords will be stored in a database.
ii. Usability- The system will easily be used by the users since the system will have a user-
friendly interface.
iii. Performance- The system will have a quick response time that is refreshing time and
loading screen would be faster. Maintainability-The system is developed in such a way
that its functionality can be enhanced to support further developments in the system.
iv. Reliability-The system will be reliable for instance if server crashes, the data will not be
lost because a backup will be maintained.

v. Availability- The system will be available for access from any location from an online
platform.
vi. Flexibility- the system should be ready for expansion and changes.
vii. Backup- The system will provide a means to backup data so as to avoid loss.
viii. Maintainability-The system is developed in such a way that its functionality can be
enhanced to support further developments in the system.

4.3 Design Interface

4.3.1 Front End of the system
The front end is basically the development of the graphical user interface of a website through
the use of HTML, CSS and JavaScript so that users can view and interact with the website.

4.3.1.1 Login Interface

The picture below illustrates an overview of how the login interface will look like so that to
enable the users have an access to the system by providing the required credentials that is the
username and password.

Car rental
Login/Register
portal

home About Us Car Listing FAQs Contact Us search

By tapping the login button, the pop-up menu below will be portrayed.
 login
x

Email Address

Password

Login

Don’t have an account? Sign up

Forgot password?

4.3.1.2 Search Algorithm

From the login interface, its evident there is a search button. The search button uses
LINEAR/SEQUENTIAL search algorithm. Linear search is a very simple search algorithm. In
this type of search, a sequential search is made over all items one by one. Every item is
checked and if a match is found then that particular item is returned, otherwise the search
continues till the end of the data collection

package algorithms.searching;

public class Linear Search {

public static void main(String[] args) {
char[] cars = {maruti, Mazda, BMW, Toyota, Nissan};
char target = BMW;
System.out.println(search (CARS, target));

static char search(char[] cars, int target) {

for (char index = 0; index < char.length; index++) {
if (cars[index] == target) {
return index;
}
}
 return null;
}
}

4.3.1.2 Admin login interface

Below is the interface of how the admin panel looks like after a successful login by the admin.

dashboard

brands
Listed Total
Reg users
Vehicles vehicles bookings

Manage Bookings

Manage Testimonials

Manage Contact Us Listed brands subscribers queries

Reg users

Manage pages

Update contact info

Manage subscribers testimonials

3.4.2 Design Layout.

Unified Modelling Language.

UML Diagrams produces analysis models which focus on structuring and formalizing system
requirements.
Analysis models contains three models; functional, object and dynamic models. Functional
models can be described as use case diagrams. Class diagrams describe the object model.
Dynamic model is described by sequence, state chart and activity diagrams.

Use Case Modelling.

Use case model diagrams model the functionality of the system using actors and use cases. Use
cases are services or functions provided by the system to its users. They are used to gather
requirements of a system including internal and external influences. They are also used to gather
requirements of a system, get inside view of a system and show interaction between
requirements and actors.
Figure 5:Use Case Diagram

Activity Diagram.
An activity diagram is a special kind of state chart diagram. It illustrates the dynamic nature of
the system by modelling the flow of control from activity to activity. An activity represents an
operation on some class in the system that results in a change in the state of the system.
Typically, activity diagrams are used to model workflow or business processes and internal
operations.
 View the desired car of your choice

Enter your reservation details

Figure 6:Activity Diagram

Sequence Diagram.
It’s a type of interaction diagram which describes how and in what order a group of objects work
together. It helps software developers to understand the requirements for a new system or
document existing process, models the logic of a sophisticated procedure function or operation.
It helps developers see how objects and components interacts with each other to complete a
process.
Figure 7: Sequence Diagram
 Class Diagram
Class diagram is a static diagram. It represents the static view of an application. Class diagram is not only
used for visualizing, describing, and documenting different aspects of a system but also for constructing
executable code of the software application. The purpose of class diagram is to model the static view of
an application.

Figure 8: Class Diagram

 Deployment Diagram
Deployment is a UML diagram type that shows the execution architecture of a system including
nodes such as hardware, software execution environment and the middleware connecting them. It
comprises of node, component, artifacts and interface. It is used to visualize the physical
hardware and software of a system.

Figure 9:Deployment Diagram

4.3.3 Backend of the system

This design layer comprises of the database and how the tables are related.
 Database Design
Database design is the organization of data according to the Chambers. The designer elements
determine what data must be stored and how the elements interrelate.
The system comprises of 11 tables which are;
 Admin table
 Members table
 Booking table
 Brands table
 Contact us table
 Contact us query table
 Pages table
 Subscribers table
 Testimonials
 Users table
 Vehicles table

3.4.3 Table Design

Here are some of the tables within the database.

1. Users Table
Attribute Data type Primary Key Foreign Key Constraints
User_id Int(10) PK - Not Null
F_name Varchar(20) - - Not Null
L_name Varchar(20) - - Not Null
Email Varchar(20) - - Not Null
Password Varchar(20) - - Not Null
2.Booking Table

Attribute Data type Primary Foreign Constraints

Key Key
User_id Int(55) PK - Not Null
Start_Date Varchar(16) - - Not Null
End_Date Varchar(16) - - Not Null
Area_Loc Char(16) - - Not Null

3.Vehicles tables

Attribute Data type Primary Key Foreign Key Constraints

User_id Int(4) PK - Not Null
Vehicles title Varchar(12 - - Not Null
)
Vehicles brand Varchar(12 - - Not Null
)
Fuel type Char(7) - - Not null
Price per day Int(6) - - Not null
CHAPTER 5: IMPLEMENTATION.
Login interface
Booking interface
Admin interface

3.5 Testing Design

This is done when the system development is complete and the system is ready for
deployment. The testing phase comes next to determine if the earlier intended
objectives have been realized. Testing is done based on whether completeness will
have been realized or functional testing that determined whether the software is
doing what it is expected correctly and in the right way.
Test Cases
This is a set of actions executed to verify a particular feature or functionality of
requirements of software.
Test Scenario: Check the log in functionality in the car rental system
Test Case 1: check results using correct email and password
Test Case 2: Check results using incorrect email and password
Test case3: Check results when email and password are empty
 Test Test Steps Test Data Expecte Actual Pass/
Case d Result Fail
Results s
Check Go to https:// Email=test The
the localhost/car_rental/index.p password=te user
user hp st should
login Enter email be
with Enter password logged
valid in the
data system
Check Go to https:// Email=test The
the localhost/car_rental/index.p password=te user
user hp st should
login Enter email not be
with Enter password logged
invali in the
d data system
Check Go to https:// Email=test The
the localhost/car_rental/index.p password=te user
user hp st should
login Enter email not be
with Enter password logged
empty in the
data system
Figure 10: Test Cases
After inputting incorrect username and password, the error below is displayed.

After inputting correct username and password, the system successfully allows you to now use the site.