WACHEMO UNIVERSITY

COLLAGE OF ENGINEERING
AND TECHNOLOGY SCHOOL OF COMPUTING AND
DEPARTMENT
OF INFORMATION TECHNOLOGY
Project Title: Web based Car Rental Management System in

Case of Bereket and Gezahagn

Supervised By: Tsegaye mulu

Project Title Web based Car Rental System

Prepared By No Name of student ID

1. SIRGOTA NESRO 5319/10

2. TIGABU TEFESE 5334/10

3. MELKAMU 5974310/10
LAMBAMO

4 TSEGANESH DENEKE 5335/10

Hassana, Ethiopia
Date of submission: [Sep/2024]
 Approval sheet
This is to declare that the project work which is done under the supervision of Instructor Mr.
Tsegaye mulu having the title web-based car rental management system
GROUP MEMBERS
Full Name Signature

_____________________________________ ____________________

_____________________________________ ____________________

_____________________________________ ____________________
No part of the project work has been reproduced illegally (copy and paste) which can be
considered as Plagiarism. All referenced parts have been used to argue the idea and cited
properly. We will be responsible and liable for any consequence if violation of this declaration
occurs.
Advisor Name Signature Date
____________________ __________________
_______________________________

Examiner Name

_______________________________ ____________________ __________________

_______________________________ ____________________ __________________

_______________________________ ____________________ __________________

Department Head Name

_______________________________ ____________________ __________________

i
Table Contents

Contents
Contents......................................................................................................................................................ii
Abstract.......................................................................................................................................................v
Acknowledgement......................................................................................................................................vi
List of Figure.............................................................................................................................................vii
List of Table..............................................................................................................................................viii
LIST OF ABBREVIATIONS.......................................................................................................................viii
CHAPTER ONE..............................................................................................................................................1
1.1 Introduction.......................................................................................................................................1
1.2 Backgrounds......................................................................................................................................1
1.3. Statement of the problem................................................................................................................1
1.4. Objective of the project....................................................................................................................2
1.4.1. General Objective......................................................................................................................2
1.4.2. Specific objective.......................................................................................................................2
1.5 Proposed System...............................................................................................................................2
1.5.1 The actors and their role...........................................................................................................3
1.5.2 Payment Method........................................................................................................................3
1.6 Literature Review...............................................................................................................................4
1.7.1 Scope of the project....................................................................................................................4
1.7.2. Limitation of the project............................................................................................................5
1.8 Methods and Tools............................................................................................................................5
1.8.1 Methods of Data collection........................................................................................................5
1.8.2 Systems Analysis and Design Method.........................................................................................6
1.8.2 System implementation Design method.....................................................................................7
1.8.3 Development Environment and programing tools......................................................................7
1.9 Significance of the project.................................................................................................................8
1.10 Beneficiaries of the project...........................................................................................................9
1.11 Feasibility Analysis...........................................................................................................................9

ii
 1.11.1 Economic feasibility................................................................................................................9
1.11.2 Operational feasibility.............................................................................................................10
1.11.3 Technical feasibility.................................................................................................................10
1.11.4 Political feasibility...................................................................................................................11
1.12 Project Plan...................................................................................................................................11
1.12.1 Time Schedule........................................................................................................................11
1.12.2 Team composition..................................................................................................................12
CHAPTER TWO...........................................................................................................................................13
2. Description of the Existing System.........................................................................................................13
2.1 Introduction of Existing System.......................................................................................................13
2.2 Business Rule...................................................................................................................................14
2.3 Function Existing System.................................................................................................................14
2.5 Strength of existing System.............................................................................................................15
2.6 Weakness of existing System...........................................................................................................16
CHAPTER-THREE........................................................................................................................................17
Requirement Specification and Analysis (RSA)......................................................................................17
3.1 Introduction.....................................................................................................................................17
3.2 Description of Proposed Systems....................................................................................................17
3.2.1 User Characteristic....................................................................................................................18
3.2.2 Constraints................................................................................................................................18
3.2.3 Assumptions and Dependencies...............................................................................................18
3.3 Requirement Specifications.............................................................................................................19
3.1 Functional Requirements.................................................................................................................19
3.3.2 Non-functional requirements...................................................................................................19
3.4 System modeling.............................................................................................................................20
3.4.1 Actor identifications..................................................................................................................20
3.4.2 Use Case Identifications............................................................................................................20
3.4.3 Use Case diagram.....................................................................................................................21
3.4.4 Use case diagram description...................................................................................................23
3.5 Requirement Analysis......................................................................................................................27
3.5.1 Activity diagram......................................................................................................................27

iii
 3.5.2 Sequence diagram........................................................................................................................32
CHAPTER-FOUR.......................................................................................................................................36
SYSTEM DESIGN.........................................................................................................................................36
4.1. INTRODUCTION..............................................................................................................................36
4.1.1 Purpose of the system design document..................................................................................36
4.1.2 Design Goal...............................................................................................................................36
4.2 Class Diagram..................................................................................................................................37
4.3.1 Database diagram.....................................................................................................................39
4.3.2 Entity Relationship Diagram (ERD)............................................................................................39
4.3.3 Persistence Modeling................................................................................................................40
4.3.4 Mapping with Normalization....................................................................................................40
4.4 Subsystem Decomposition...............................................................................................................41
4.5 Deployment Diagram.......................................................................................................................41
4.6 System Architecture.........................................................................................................................42
4.7 User Interface (UI) Design................................................................................................................43
4.8 User Interface flow Diagram............................................................................................................46
Recommendation......................................................................................................................................47
Conclusion.................................................................................................................................................48
Reference..................................................................................................................................................49
Appendix...................................................................................................................................................50

iv
 Abstract
This application presents a data management system for a car rental company. This enables the
administrator to keep track of all the customers’ information. This system increases customer
retention and simplify vehicle and customers management in efficient way. Web Based Car
Rental System has a very user-friendly interface. Thus, the users will feel very easy to work on
it. By using this system admin can manage their rental, bookings, customer issues and vehicle
issues etc. The car rental information can be added to the system, or existing information can be
edited or deleted by the administrator. The transaction reports of the car rental system can be
retrieved by the administrator, when it’s required. Thus, there is no delay in the availability of
any car information, when ever needed the car rental information can be captured very quickly
and easily.

v
 Acknowledgement
First of all thanks, we thanks to our almighty God to give strength and health to finish this
project and for most our great appreciation goes to our advisor or his timely and technical advice
during all the project time and also to our department for giving us the chance to do this project.
Finally our limitless gratitude goes to our IT department staff members for giving us some data
about the project area

vi
 List of Figure
Figure 1.use case diagram .............................................................................................................
21
Figure2 Log in activity diagram ...................................................................................................
27
Figure3 Delete car for admin activity diagram .............................................................................
28
Figure 4 Upload car activity diagram ...........................................................................................
29
Figure5 Activity diagram of send comments ............................................................................... 30
Figure 6. Activity diagram Order car .............................................................................................
31
Figure 7. Login sequence diagram ...............................................................................................
32
Figure 8. Send comment sequence diagram ..................................................................................
32
Figure 9.View comment sequence diagram ..................................................................................
33
Figure 10.View information sequence diagram .......................................................................
33
Figure 11.Update car sequence diagram .......................................................................................
33
Figure 12.Delete car sequence diagram ........................................................................................
34
Figure 13.Class diagram ...............................................................................................................
37
Figure 14.Database diagram model ..............................................................................................
38
Figure 15 Entity Relationship Diagram .......................................................................................
39
Figure 16.Deployment diagram ....................................................................................................
41
Figure 17.Home Page.................................................................................................................... 42

vii
Figure 18.Customer page ..............................................................................................................
43
Figure 19.Admin Page ..................................................................................................................
44
Figure 20.User Interface Flow diagram .......................................................................................
45

List of Table
Table 1. Payment method ................................................................................................................
3
Table 2. Hardware tools ................................................................................................................. 8
Table 3. Software tools ....................................................................................................................
8
Table 4. Time schedule ..................................................................................................................
11
Table 5. Team composition............................................................................................................
11
Table 6. Use case description Login ..............................................................................................
22
Table 7. Use case description View car information .....................................................................
22
Table 8. Use case description upload car .......................................................................................
23
Table 9. Use case description view comments ..............................................................................
23

viii
Table 10. Use case description delete car ......................................................................................
24
Table 11. Use case description logout ...........................................................................................
24
Table 12. Use case description sends comment .............................................................................
25
Table 13. Use case description Order car ......................................................................................
26

LIST OF ABBREVIATIONS
CPU Central Processing Unit
ERD Entity Relationship Diagram
OOA Object oriented analysis
OOD Object oriented design
UI User Interface
UC Use Case
ID Identification number

ix
MS Microsoft office
PHP Hypertext Processor
UML Unified Modeling Language
SQL Structure Query Language
CSS Cascading Style Sheet
RSA Requirement Specification and Analysis
HTML Hypertext Mark-up Lang
ERT Extended reality technology
OOSAD Object Oriented System Analysis and Development

x
 CHAPTER ONE
1.1 Introduction
As the internet improves the life of people, it also gives accesses to things that were inaccessible before. The internet
is one of the most important tools of communication. The world has become a place where there is a lot of
technological development which brings the result of almost every single thing has been transformed into
computerized form. These days, individual activities have been changed into work done by information systems. One
of which is the primary objective of this project which is about car rental system. Renting car system exists in the
previous years where people rent cars for their own reasons. Car rental is basic to numerous individuals’ arrangement
to travel or move from one place to another for business purposes, tour, and visit occasions. Thus, car rental is
extremely useful. Our car rental management system is a system for an organization that rents out cars. This system
empowers the organization to make their services accessible to the public through the web and furthermore keep
records about their services. In Ethiopia there are many organizations that use the manual procedure for renting
different car. It includes the interference of a car broker to mediate between the company and the purchaser which
was wasteful and lacks full information to sell a car. Customer and providers waste their time, money and labor force
to get a broker. Bereket and Gezahagn car rental was established on September 14,2022, in order to satisfy the car
need for people who are living in Hassana city. Bereket and Gezahagn car rental is performing rents different types of
cars for those who are in need of and it also registers the personal information of the customer. The company
provides a means for sending the driver if it is a rental case and gives a 5 month guarantee for the purchased car. A
Car Rental is about renting cars to the public under terms and conditions, complying with the law. Car rental
consists of all the functions and procedures which allow a company to rent cars in order to facilitate and quicken
rental procedures. Car renting is essential to many peoples plan to travel or move from one place to another for
business purposes, tour, and visit or holidays, for these reasons Car renting is helpful.

1.2 Backgrounds
In Ethiopia there are many organizations that use the manual procedure for rent different car. It
includes the interference of a car broker to mediate between the company and the purchaser
which was wasteful and lacks full information to sell a car. Customer and providers waste their
time, money and labor force to get a broker. Bereket and Gezahagn car rental was established
September 14, 2022, in order to satisfy the car need for people who are living in Hosanna city.
Bereket and Gezahagn car rental is performing rents different types of car for those who are in
need of and it also registers the personal information of the customer. The company provides a
means for sending the driver if it is a rental case and gives a 5 month guarantee for the purchased

1
car. Car rent is essential to many peoples plan to travel or move from one place to another for

business purposes, tour, and visit or holidays, for these reasons Car renting is very helpful.

1.3. Statement of the problem

The company already has a car renting procedure which is not a web-based application. This
procedure lacks to store customer’s details and they cannot make their services more available to
the public through the internet, they rather make use of posters to advertise their services to the
public. The existing system poses different working problems. It performs every activity
manually. It handles file on a paper which lacks security, confidentiality, timely access of
customers.

The existing system:

 Needs the repeated appearance of customer physically
 Doesn’t allow customers to check the availability of the car they desire.

1.4. Objective of the project

The objective of the project is described in general and specific objectives as follows.

1.4.1. General Objective

The general objective of this project is to develop a web-based car rent system for
Bereket and Gezahagn car rental system to reduce the difficulties to find car rental
services for the people who wants to rent cars and to give a solution for the entire
problem in Online car rental systems and services.

1.4.2. Specific objective

There are some specific objectives to achieve the general objective. These are:
 Real-time Vehicle Availability: Provide customers with real-time information on vehicle
availability, eliminating the need for phone calls and manual checks.
 Automated Rental Management: Manage rental contracts, billing, and customer records
electronically, reducing errors and improving efficiency.
 User-Friendly Interface: Develop a user-friendly website and mobile application for easy access and
navigation, catering to both tech-savvy and less tech-proficient users.
 Improved Communication: Provide a dedicated platform for communication with customers,
enabling efficient query resolution and customer support.

2
  To analyze functional Requirement of the organization.

 To specify system requirement

 To design attractive user interface, develop and deployment for the proposed
system.
 To manage the details of car, payment, customer, supplier, insurance. it manages
all the information about car, booking, insurance, car.
 To test the proposed system
 Develop a system that increase work efficiency

 Give the service to the customer in short period of time.

 Design a system which is secured, efficient and user friendly

1.5 Proposed System

The existing system faces some problems and the problem’s primarily results from the manual
system of running the activities and we try to put an alternative solution to the problem. The best
alternative solution to the existing system is to change the existing manual system and produce a
web-based system. Web based system is one of the mechanisms to solve problems of some
manual activities. Web based application needs internet to work. Anyone can communicate with
each other in different place. As a result, we will develop interactive and user-friendly interface
web-based application that anyone can use anywhere, across the world.

 The new system is to give web-based health information distribution and

computerized the system and simplify the entire work and minimize work load for
that Company
 The system performs activities like:
 Registration
 Login/logout
 Car booking
 Searching
 Remove/add records
 Payment issues
 Time interval for rents
 Security of the system

3
  Validation of the users
 Posting cars
 Notifying the users
 Approve/Disapprove customer requests
 Comments

1.5.1 The actors and their role

 Customer: the one who is interested in our system to rent cars

 Admin: the one who approve, post, delete, update a car and who write and read comment

from the user

 Supplier: a person who can add new car, view car information.
1.5.2 Payment Method
Table 1. Payment method
Payment
Rent cars Daily weekly monthly
Executive /Suzuki 2000 birr 11,200 birr 48,000 birr
Hilux 3000 birr 16,800 birr 72,000 birr
Hyundai 1800 birr 10,080 birr 43,200 birr
Toyota 1500 birr 8,400 birr 36,000 birr

1.6 Literature Review

Car rental management systems are becoming increasingly popular among car rental companies,
as they offer a more efficient and streamlined way to manage reservations, vehicle availability,
and customer information. In this literature review, we will explore the existing research on car
rental management systems and highlight their benefits, limitations, and future prospects. The
car rental company of Bereket and Gezahagn car Rent has one renting branches and 15 cars in
Hossana towns. Cars classified by car group, are available for rental. A branch has a manager
and booking clerks who arrange rentals and reservations for future rentals. Cars rented from
branch of Bereket and Gezahagn car rent and return back to the company. There are about 800
service bookings per year. Bereket and Gezahagn car Rent keeps records of about 5000
customers. Bereket and Gezahagn car Rent company that rents automobiles for short periods of

4
time, generally ranging from a few hours to a few weeks, few months. The user/customer who
wants to rent a car must first contact Bereket and Gezahagn car Rent company for the desired
vehicle done online. At this point, this person has to supply some information such as; dates of
rental, and type of car. After these details are worked out, the individual renting the car must
present a valid Identification card.

1.7 Scope and Limitation

1.7.1 Scope of the project
The system will provide a detail information and profile about car Company and service
provided across different car category in Hosanna
The scope of the system that is going to be designing will cover the following areas:
 The system will display all the necessary information including a descriptive image,
description for the car, price, car brand, car quality, availability
 Renting cars
 Creating and updating customer accounts.
 Administrator can add and remove car category from the system  Accept
customers complain.
 Posting new cars.

1.7.2. Limitation of the project

The services that are needed but not included in our system are

The payment system is restricted on the bank account number only and focuses on the
stored account value or deposit system it does not include the following

 Visa card,
 Smart card
 Internet Banking
The system doesn’t support insurance like Life, Fire and travel.

1.8 Methods and Tools

Methods is the “instrument,” or “tool” that is be used to accomplish the goals of the research. It
deals with a range of ways to make the most out of solving key research problems. Think of the
methodology as the systematic way in which those tools will be employed. There is no use
5
having a tool without having a process to use it most effectively. To develop the new system we
have used different methodology approaches. The following are the different methodology used
in our new system

1.8.1 Methods of Data collection

We have used different data collection methods in our project interview and document analysis
are among the method used.
 Interview:
We have orally discussed and interview with some employees of Bereket and Gezahagn car
rental for necessary information’s. This information helps us to understand the system and also to
identify the problems occur in existing system. So, we analyze information’s of the agency and
obtain some basic concepts on how the customers are become a member in the current system.
 Since we are developing a new system, we have to directly communicate to the
organization officials.
 To understand the system well we choose this method.
 To ask customers filling about the manual system and the limitation they thought it
has.
 Document analysis:
We collect more information by referring different manuals, written files and documents about
the car rental and system.

 To understand very specific information about the organization’s operation.

 To gather information related to our topic.

 Observation:
Assessing and analyzing the overall rental system that has been carried out by personally
observing the current working system. We have gone to Bereket and Gezahagn car rental
organization in order to observe the way their system is working which turned out to be manual,
tiring, time consuming and wasteful system.

1.8.2 Systems Analysis and Design Method

In this system, we designing to use Object Oriented System Analysis and Development
methodology (OOSAD). The reason why we are selected OOSAD (object oriented
system development) is because it has the following advantages. (cali, 2004)

6
  Objects/classes or models are used to represent real world problems in
simplified form.
 Object based models appeal to the working of human cognition and hence the
human input in to the development of a system is likely to be more natural and
less error prone.
 Object oriented systems tend to be based up on stable forms that are more
Resilient to change.
 Allow full exploitation of the power of object based and object-oriented
programming languages. This has two phases.
 Object Oriented Analysis (OOA)
During this phase the team uses to model the function of the system (use case
modeling), find and identify the business objects, organize the objects and identify the
relationship between them and finally model the behavior of the objects in detail.
 Object Oriented Design (OOD)
During this phase our team uses Microsoft Visio software to refine the use case model
and rational rose for designing the sequence, collaboration, activity diagrams, class
diagram, ER diagram and to model object interactions and behavior that support the
use case scenario. (cali, 2004)

1.8.2 System implementation Design method

 For System Development
• Memory: to storing data
• Printer: to print the document.

• Internet cable: used to use internet in which search data

• Computer: to do deferent activities

• Flash: to storing document as a backup

 Development Tool
• Microsoft Visio: to draw unified modeling diagram. Such as sequence diagram,
Activity diagram, use case diagram and class diagram.
• UML: to draw unified modeling diagram

• Microsoft word: to write our system documentation.

7
 • Notepad++: To write the code.

• Xampp Server: - to simulate the server-side activities.

• Microsoft PowerPoint: for presentation.

• HTML, CSS and JAVASCRIPT

 Back End Design Tool

PHP MYSQL (Xampp), apache software data base system will be used in developing and
managing the database at back end
 Front End Design Tool
The user interface will be developing using HTML, CSS, JavaScript integrated development
environment since it easily designing the front end and connected in to data base easily.

1.8.3 Development Environment and programing tools

In this project the following hardware and software system development tools are use
1.8.3.1 Hardware Tools
The hardware tool equipment which are used to our project in consists of following

Table 2. Hardware tools

Hardware tools Function of the tools

Flash To hold files

Laptop To do the project

Pen & Note Book To Write interview responses collecting information

from the organization

Printer Convert to hard copy

1.8.3.2 Software Tools

The software tool program equipment which are used to our project in consists of following:
Table 3. Software tools
Activity of Tools Software tools name used

8
 Client-side UL code HTML and CSS
Client-side scripting JavaScript

Server-side script PHP

Database Server MYSQL IN XAMPP

Web server Apache.

Code text editors Visual studio, sublime

Presentation Microsoft ppt
Documentation Microsoft office
Browser Google chrome
Designing ERT

1.9 Significance of the project

The new web-based car rent system is easy, fast and Consistent and plays a crucial role for the
workers and for the customers.
The proposed system has the following significances:
 For the customers: -
 To minimize time needed to register.
 Customer can check if the needed type of car is available in the company without
being there
 Customers can send their comment to the organization.
 They can get full information about the system through the website and know the
detail how the organization works.
 For the organization: -
 It increases performance of the organization,
 Fast response to customer’s affair making the organization competent.
 Making the organization more profitable than ever by attracting many customers.
 For the Researcher’s
 To get additional knowledge
 Support for next work

9
 1.10 Beneficiaries of the project
The proposed system is will solve the problem of the existing system and give efficient benefits
for that company.
 In addition, that the following are the beneficiaries of the new system
 Customer/user
 Admin
 Supplier

1.11 Feasibility Analysis

Feasibility study is an analysis of the practicality and potential success of proposed project. It
assesses the economic, technical, operational, schedule, political, and legal feasibility of the
project. Here is a breakdown of each aspect of feasibility study for our web based car rental
system project.

1.11.1 Economic feasibility

Economical feasibility is to balance the benefit having new system in place against the expenses of designing and
implement the new system. The senior management has an economic reason for the new system thanks to this
feasibility study. As a result of automation, there may be a variety of concrete and intangible benefit as well as
expenses.

Benefits: - both tangible and intangible benefit can be used to describe the advantage of a system.

A Tangible benefit: - the project that will be computerized, there will be a decrease in the cost of the resource used
for manual operation, such as: pens, paper, human labor, space needed to keep data record, and save data storage.
There will also be a reduction in the amount of time that we are required to include or bring in during manual system.
The team used a method known as the time value of money to compute the corresponding tangible benefits.

Intangible benefits: - The following worksheet lists the intangible benefits associated with the project.

 Increase employee moral

 Increase management flexibility
 Provides more timely information
 Increase performance

 1 Cost reduction and avoidance: to calculate these following things be considered.

10
  Total Number of sale persons in existing system= 4
 Average Salary of each Employee per month = 6000.00Birr
 Total money required for payment per year= 2*6000*12= 144,000Birr
 Average Number of Employee needed when the new system is deployed=1 (one Admin).
 Average salary of each of them per month = 5000.00Birr
 Total money required for payment per year= 1*5000*12= 60,000.00Birr
 Difference between before and after develop the system money required for payment Cost Reduction
and Avoidance= 144,000Birr-60,000.00Birr= 84,000Birr
1.11.2 Operational feasibility
The system to be developed will provide accurate, secured service and decrease the labor work
load. Also, the system will be easily operation after giving short term training or orientation. So,
the system will be operation feasibility.

1.11.3 Technical feasibility

General study in the project area has shown that the current system and ability existing in order
to complete the propose system objectives. Our project can be done with new equipment, new
software technology and available personnel and therefore it can be concluded that the system is
technical feasibility.

1.11.4 Political feasibility

The systems to be developed is not conflict with any government directly or indirectly, because
this new web based car rental system gives service for people effectively and efficiently. And
also, easily communicate

1.12 Project Plan

The feasibility of the project's schedule is the possibility of the project's completion time. If the
project is completed on time, it is considered timetable feasible. We plan to finish the project by
May.

1.12.1 Time Schedule

The plan of the project's schedule is the possibility of the project's completion time. If the Table
Project is completed on time, it is considered timetable feasible.
Table 1: Schedule of the project

Gantt chart project schedule

S. Phase 2016 E.C

11
N
July Aug sep Dec July Aug
1 Project proposal

2 Requirement
analysis
3 Design

4 Implementation

5 Testing

6 Project closure

1.12.2 Team composition

Table 5. Team composition
Project title Web Based Car Rental Management system

Prepared by Name Id no Email/mobile Responsibility

1 Sirgota nasir 5319/10 All activities

2 Tigabu tefese 5334/10 All activities

3 Melkamu 5974310/10 All activities

lambamo
4 Tseganesh 5335/10 All activities
deneke

12
 CHAPTER TWO
2. Description of the Existing System
The organization works cannot be completed in an easy way because it lacks the system that uses
the online way of rent the cars. It needs the customer’s physical appearance in order to go
through the renting system which kills the person’s time and money. Most of the organization’s
work is be performed in a manual form which is a waste. The employees are overloaded because
of the number of customers that comes at the same time it is be too hard to provide the service in
efficient way.

2.1 Introduction of Existing System

Beret and Gezahagn car rental Company has not used Web based car rental system before.
Currently, the company uses manually manage materials, which is necessary for them The
existing system only provides text based interface which is not as user friendly as Graphical user
interface. Since the system is implemented manually, the response is very slow. The system ways
are not secure as papers may get lost or damaged. Hence, there is need of reformation of the

13
system with more advantages and flexibility. The system eliminates most of the limitations of the
existing system. If anybody want to rent a product from a particular city from their own home,
how it is possible? If one person is going to another city, but if he want products for rent before
he reach his destination, then how it possible? So answer to these questions is our web site. The
transactions are not secure as papers may get lost or damaged. Hence, there is need of
reformation of the system with more advantages and flexibility. The system eliminates most of
the limitations of the existing system Draw backs:
 The manual system requires a long time to distribute information for customers.
 Record files of materials may lose if the hard copies document is destroying.
 The store properties are not visible and known for all stakeholders and staff
workers.
 The manager takes long time and complicated to report information to higher
officials.
 It’s difficult to get information from the previous document.
 The work is complicated for specifying type, cost, and quantity of properties.

2.2 Business Rule

It is a rule that restricts or specific a certain feature of a business and always resolve to true or
false. Business rules are designed to uphold or organizational structure, as well as to regulate or
effect how the business system behaves, operations, definitions, and limitation that apply to a
company are described by business rules. Business rule is put in place to help the organization
achieve its objectives. They can apply to people, processes, corporate behavior, and computing
system in an organization
 Customers coming to the company must bring an international license and the license
must be related to road transport
 If a customer rents a car and damages it, unless it is a technical problem, the customer
will ask for it himself.
 When a customer comes to rent a car, he is obliged to make the full payment
 If a customer does not return the rented car on time, he is obliged to pay the rental car
from the due date.
 We would like to remind our customers that if they return the rented car before the last
day, the payment will not be refunded
14
2.3 Function Existing System
The new system helps the organization and the customers in giving service in a more facilitated
and timely manner. The proposed system allows all the renting process to be performed without
being physically appeared in the Company. The organizations task is eased because when new
cars are available the admin will just upload the photo of the car with its full description nothing
much. Data storage and retrieval is faster and easier to maintain because data is stored in a
systematic manner and in a single database. Easier and faster data transfer through the latest
technology associated with computer and communication. These features increase the efficiency,
accuracy, and transparency of the car renting system.
2.4 Document used in Existing system
The existing car rent system in Bereket and Gezahagn car Rent Company uses the following
documents and forms

15
2.5 Strength of existing System
The existing system contains various activities. These activities are most of the time performed
face to face or physically. These activities are
 First user comes to office and contact the manager

16
  The manager announcing the user to admin
 Property owner contact manager by using phone formally

2.6 Weakness of existing System

If anybody want to rent a product from a particular city from their own home, how it is possible?
So answer to these questions is our web site.
 The manual system requires a long time to distribute information for customers.
 Record files of materials may lose if the hard copies document is destroying.
 The store properties are not visible and known for all stakeholders and staff workers
 It’s difficult to retrieve back history of the customer and contract detail if needed for
any legal issue
 This company use internship same body and park-time worker to fill up vacant
potion.
 One of the weaknesses of this company has no website to observe more information
about car rent.
 It’s difficult to retrieves back history of the customer and contact detail if needed for
any legal issue

2.7 Alternative Solution

The new system will generally change this manual system in to computerized system and
simplify the entire work and minimize work load for that Company. Time by giving fast access
to the user but pervious one is time consuming one. Our system can remove this problem by
giving fast access to users. Bereket and Gezahagn car rent management and this project aims to
develop all the record about Customer into computerized system and also the company require
the knowledge of computer in order to change the traditional paper-based way of recording of
Customer data into the computer based from which has low performance to high performance
with the best controlled security and that has backup for the future use.

17
CHAPTER-THREE
Requirement Specification and Analysis (RSA)
3.1 Introduction
This chapter deals about the modeling techniques of proposed system by using Use case
diagrams, Use case documentation, Sequence diagram, Activity Diagram, Analysis level class
diagram, User Interface Prototyping and Supplementary specifications. After identifying the
actors and the use case of our new system, the use cases are developed and textual descriptions
are depicted based on the use case. Next to this the sequence diagram will be depicted based on
the use cases which are developed for the newly proposed system. Activities will be represented
by activity diagram. In this chapter the major activities performed or identified are: modeling the
function of the use case, identifying actors, identifying use case, constructing use case model and
use case scenarios and final designing of user interface.

3.2 Description of Proposed Systems

The new system helps the organization and the customers in giving service in a more facilitated
and timely manner. The proposed system allows all the rent process to be performed without
being physically appeared in the company.
The organizations task is eased because when new cars are available the admin will just upload
the photo of the car with its full description nothing much.
The system provide an effective means for the costumers to rent cars only with required
qualification to have a better car selection and find out the information regarding the current
update information about their dream car .
Data storage and retrieval is faster and easier to maintain because data is stored in a systematic
manner and in a single database. Easier and faster data transfer through the latest technology
associated with computer and communication. These features increase the efficiency, accuracy,
and transparency of the car rental system.
The following are some of the purposes under the proposed system
Improved accessibility of customer data.
 Reduce data redundancy.
 Maintain quality data.
 Avoid inconsistency.
 Maintain integrity.

18
  Enforce security measures.
 Centralized information control.

 No cost is spending on the broker

3.2.1 User Characteristic

The users are the customers who used this system and take the cars on rent for their personal
work. This is to manage their accounts separately in the system and to their data in the system
while managing their accounts. The user can book car on rent from the system and even pay the
charges of the same. There are some other specific features which can be customized by the user
initially. The related attributes of this entity are defined below:
 User ID: The system provides an identity number to eat user which will be helpful in
their interacting with the system
 Name: There are so many users who have created their accounts in the system their
names are saved in this attribute.
 Contact No.: The contact number of each user is saved in this attribute to connect them
if needed by the admin or employees.
 Email Address: The user’s email address saved in the attribute for official purpose while
connecting them.
 Residence: The permanent address of each user is saved in the attribute for verification
and confirmation process and also to send the car on their address.
 Occupation: The system also says the occupation of the user to view whether the user
can afford the rent of the car or not.
 Status: The user can book a car more than one time therefore this attributes what’s the
active or inactive status of the user.

3.2.2 Constraints
When doing this system, the team has faced different challenges. Among the challenges: -
 Lack of better services
 Lack of internet access

3.2.3 Assumptions and Dependencies

 At any one moment, each booking is connected with only one automobile reservation.
 Cars that are part of the system should be available at a certain point.
 Discount codes may or may not be applied to billing.

19
  Due to various cancelled bookings, not all bookings are connected with billing.
 Since the renter may have his own insurance, the rental insurance may or may not be
included in the booking

3.3 Requirement Specifications

3.1 Functional Requirements
This web-based car rental system is designed as a way that enables the ones who participate to
utilize information at all levels of the organization.
Description of requirement
 The system should let the administrator and customers in after authentication.
 Should deny service for unauthorized bodies.
 The system shall enable the customers roles
 The system should give every customer the price of the car
 The system should Advertise or display available cars.
 The system shall accept user’s comment.
 The system should allow admin to login to the system using their username and
password.
 The system should agreement between the car owner and users.
 The system should allow user to login to the system using their username and password.
 The system should allow admin to register new cars.
 The system shall allow admin to update cars in the list.
 The system shall allow customer to select cars in the list.

3.3.2 Non-functional requirements

 Reusability:
 The data and record that are saved shall be reused if needed.
 Security:
 The system shall provide high level of security by blocking unauthorized user
to view secured system page.
 The external security should be provided by giving login authentication.
 Performance:
 The system shall minimize errors and should display clear error message that
guides users.

20
  For login to the software password and user name should be matched to the
password and name.
 The data retrieving process shall take less time.  Usability
 The end user shall be able to access any page fast according to the internet
connection speed.  Availability
 The availability of the software shall be for everyone who has an internet
connection.
 Correctness
 The results of the functions should be correct and accurate.
 Maintainability
 Easily updating the system if there is any new thing needed to be added.
 After the deployment of the project if any error occurs then it should be easily
maintained by the software developer.  Portability
 The applicability of the system in any platform or operating system

3.4 System modeling

In this particular chapter the team members used an object-oriented system development
methodology. The main activities that are performed in this part includes: - identifying main use
cases, constructing a use case model, and documenting the use case course of events.

3.4.1 Actor identifications

Current system encompasses different users to carry out the renting process. Among those
users, the following are:
 Customer: the one who is interested in our system to rent cars
 Admin: the one who approve, post, delete, update a car and who write and read
 Supplier: A person that that can view information of car, and other things

3.4.2 Use Case Identifications

List of actor and Use case
Customer

 View status
 Rent r car
 Send Comment
21
  View car
 Register
Admin
 Log in
 View customer information
 Delete comment and car
 Approve client request
 Add new car
 Edit car information
 View car information

 comment from the user

Supplier
 Log in
 Add new car
 View car
 View status
 View car information

3.4.3 Use Case diagram

The use case model, represented in UML with use case diagrams, describes the functionality of
the system from the user’s point of view. In ours study nonfunctional requirements are features
of the system that has no direct implementation on it, which is be used to judge the operation of
the system. (itsourcecode, 2021)

22
 Figure 1.use case diagram

23
 3.4.4 Use case diagram description

Table 6. Use case description Login

Use case name Login

Admin and customer

Actor
Description The user enters authorized username and password in order to Access the
system.

The user should have username and password

Precondition
User action System action
Basic course
and of action 1. Open login page. 2. Display the login page with Login form.
3. Enter the authorized 5. Check the authorized username and password
. username And password 6. If the username and password is correct login in
in the login form. 4. the system
Click on logout button
8. End use case
7. If the username and password is incorrect back to step 3, 4 and 5 basic
Alternative course action Basic course of action.
.
course of action
Table 7. Use case description View car information
Use case name View car information
Actor Customer

Description Alternative course of action

Precondition The user must open the car web page

User action System action
Basic course
and of action 1.Click on car category
drop down menu and 2. Display the selected car category page
select the car mark like
Toyota, …
3. End use case
Alternative course of
action

Table 8. Use case description upload car

24
Use case name Upload car

Actor Admin

Description The admin upload car.

Precondition The admin must login in the system

Basic course of User action System action

action
1. Login in the system. 3. Display upload page with upload
2. Open upload page. car form.
4. Fill the appropriate 6. If the filled information is valid
Information on upload car the system uploads the car
form. information in the system
5. Click on upload Database
button.
8. End use case.
Alternative course of 7. If the filled information is invalid the system display error message
action and back to step 4, 5 and 6 basic courses of action

Table 9. Use case description view comments

Use case name View comments

Actor Admin

Description The admin view comments that are send by

Customers.

Precondition The admin must login in the system

Basic course of User action System action

action
1. Login in the system. 3.Display the comments page
2. Open comments page.
4. End use case.
Alternative course of
action

Table 10. Use case description delete car

25
Use case name Delete car

Actor Admin

Description The admin deletes a car information

Precondition The admin must login in the system.

Basic course of User action System action

action
1. Login in the system. 3. Display Delete car page with Search
2. Open Delete car page. form.
Enter the car Id number, type 6. Searches the saved car
Or on the form. information from the system
Clicks on search button. Database.
9. Click delete button. 7. If the car information is found
11. Click on yes/no button. the system displays the privies
14. End use case. Car information with delete button.
10. The system asks the admin The
correctible of his/ her action.
12. If the admin answer is yes the
system delete the car information
from the database
and display successful message

Alternative course of 8. If the car information is not found the system displays the error
action Message and back to step 4, 5 and 6 basic course of action.
13. If the admin answer is no the system back to step 5, 6 and 7 Basic
course of action.

Table 11. Use case description logout

Use case name Logout

Actor Costumer and admin

Description When the user logs out when he/she wants to exit from the System.

Precondition The users must login in the system.

Basic course of User action System action

action
1. Click on logout button 3. Display the login page
3. End use case

26
Alternative course of
action

Table 12. Use case description sends comment

Use case name Sends comment

Actor Customer

Description The Customer sends comment or Feedback about the car to the manager.

Precondition The Customer must open the bank web page

Basic course of User action System action

action
1. Open the comment page. 2. Display Comment page.
3. Enter his/her name and email 6. Display the
address.
Acknowledgement message.
4. Enter his/her comment.
7. If the name, email address and
5. Click on send button. comment correctly filled the system
9. End use case. send the comment to the manager

Alternative course 8. If his/her name or email address is invalid format display error
of action message and return to step 3, 4 and 5.
9. If he/she does not write comment display error message and back to
step 4,5and 6 basic course of action.

Table 13. Use case description Order car

27
Use case name Order car

Actor Customer

Description The customer Order the car.

Precondition The customer must view cars.

Basic course of User action System action

action
1. View the car 3. Displays the car Order
information page With the Order form.
2. Click Order Button 6) If the field information is correct
4. File the send the field information to supplier
and Display successful message.
appropriate
Information
in the order
form.
5Click on Order button.

Alternative course 7) If the field information is incorrect display error message and Back
of action to step 3, 4, 5 and 6 basic course of action..

3.5 Requirement Analysis

3.5.1 Activity diagram

The Activity diagram can help to describe the flow of control of the target system, such as
Exploring complex business rule and operations, describing the user case also the business
Process. (freeprojectZ, 2018)

28
Figure2 Log in activity diagram

29
Figure3 Delete car for admin activity diagram

30
Figure 4 Upload car activity diagram

31
 Figure5 Activity diagram of send comments

32
 Figure 6.Activity diagram Order car

3.5.2 Sequence diagram

Sequence diagram is type of interaction diagram that models the flow of messages, events, and
interaction between object and component in a system. It’s used to describe the behavior of a
system and visualize the interaction between object and components over time. A sequence
diagram is made up of object, represented as vertical lifelines, and interactions, represented as
horizontal arrows. The interaction shows the flow of message from one object to another and

33
they can include the call of the methods, the creation of object, and the sending and receiving of
signals. (creately, 2008)

Figure 7. Login sequence diagram

Figure 8. Send comment sequence diagram

34
 Figure 9. View comment sequence diagram

Figure 10. View information sequence diagram

35
 Figure 12.Delete car sequence diagram

36
 CHAPTER-FOUR

SYSTEM DESIGN
4.1. INTRODUCTION
System design is the transformation of the analysis model into a system design model. System
design is the first part to get into the solution domain in a software development. This chapter
focuses on transforming the analysis model into the design model that considers the non-
functional requirements and constraints described in the problem of the statement and
requirement analysis sections discussed earlier. The purpose of designing is to show the direction
how the system is built and to obtain clear and enough information needed to drive the actual
implementation of the system. It is based on understanding of the model the software built on.
The objectives of design are to model the system with high quality. Implementing of highquality
system depend on the nature of design created by the designer. If one wants to change to the
system after it has been put in to operation depends on the quality of the system design. So, if the
system is design clearly, it will be easy to make changes to it

4.1.1 Purpose of the system design document

This application provides a tool to conduct for general car rent automation and to change
manually structured part of the system into a computer-based system
 Easy to use: - With the increasing exposure of people to computer applications in the
home as well as in the office, expectations of computer systems in terms of their ease of
use are also increasing. Therefore, car rental design is result in a system that is “user
friendly” easy to understand, not difficult to learn how to use, and straightforward to
operate.
 Cost-effective: - This includes a number of the other objectives, and is about designing a
system that delivers the required functionality, ease of use, reliability, security, etc., to the
client in the most cost-effective way. This is often more complex than it may appear, as
future system costs may be difficult to estimate and benefits difficult to quantify.

4.1.2 Design Goal

In our system development process system design part is very important so as to
make the implementation of the proposed system very easy. The different types of
the system modeling techniques that are used to make easy the implementation of

37
the system such as deployment and component modeling are show in detail. Not
only the system modeling techniques but also some system design techniques
such as system decomposition design are cover in detail in this phase.
Some of the design goals are: -

 Understandability: - The system capability of being understood by the user.

The proposed system consists of different pages which are easy and
understandable by the user.
 Usability: - the proposed system provides easy user-friendly interface for users
of the systems. It also provides help menu which gives brief description how to
use the system so that user can be able to use it easily.
 Modifiability: - The proposed system can be modified by adding some
additional futures as the clinic want.
 Reliability: - The system should be reliable.
 Fault Tolerance: -The system should be able to give response (error message)
when the user enters incorrect input. This recommends the user to enter correct
input.
 Cost: - The proposed system regarding cost is perfectly reduces the cost of
paper and other materials related to the manual system. There for it is effective
in reducing cost.
 Flexibility: - The proposed system is highly flexible since users can access the
components as they need
 Security: -The system should be secured that unauthorized user cannot access
the system and the data that does not concern with them .

4.2 Class Diagram

Class diagram is a type of UML (unified modeling diagram language) diagram that represent the
structure of classes, objects, and their relationships in an object-oriented system. a class diagram
provides a graphical representation of the classes, their attributes, and their methods, they
contain, as well as the relationships between the classes. a class diagram is used to model the
static structure of system and can be used to defined the data and behavior of objects in real

38
world, with attributes representing the properties of the objects and methods representing the
action they can perform. And are useful in documenting the design of a system and help to
ensure that the system is well-structure and modular. They also provide a visual representation of
the system structure, making it easier to understand and communicate the design to stakeholder
and them members.

Figure 13. Class diagram

4.3 Database Model

Database model diagram is graphical representation of the structure of database, showing the
relationships between the different elements of data that the database will store. It provides a
visual representation of the data and the relationships between data elements, making it easier to
understand and communication the design of database. They include typically entities, which
represent the tables in the database, and relationships, which represent the connections between

39
tables. Attributes, which are the characteristics or properties of the entities, are also shown in the
diagram. (Itsourcecode, 2021)

4.3.1 Database diagram

Figure 14. Database diagram model

4.3.2 Entity Relationship Diagram (ERD)

An ER diagram shows the relationship among entity sets. An entity set is a group of similar
entities and these entities can have attributes. An entity is a table or attribute of a table in
database, so by showing relationship among tables and their attributes, ER diagram shows
the complete logical structure of a database

40
.

Figure 15 Entity Relationship Diagram

4.3.3 Persistence Modeling

Persistence models are used to communicate the design of database, usually relational
database, with the user and other developers. This is basically the entity relation in database
application. Persistence models enable to design the schema of the database. The persistent
classes are used to store most important and permanent information of the system.

4.3.4 Mapping with Normalization

Mapping normalization is a process of designing a relational database to store and manage data.
Mapping involves creating a conceptual model of the data and its relationships, while

41
normalization involves dividing the data in to multiple tables to eliminate redundancy and
improve data integrity.in mapping, data is analyzed and organized into entities, attributes, and
relationships, this is done to ensure that the data is stored in a consistent and organized manner
that support the need of the project. Normalization involves dividing the data into multiple tables
and establishes relationships between them. The goal of normalization is to eliminate redundancy
and ensure that data stored in consistent and reliable manner.

4.4 Subsystem Decomposition

Subsystem decomposition will help reduce the complexity of the system. the subsystem can be
considered as package holding related classes/objects. These subsystems are further decomposed
into other subsystems. The major subsystems identified in car rent management system are
interface subsystem, registration subsystem, account management subsystem, report
management Subsystem, data management, and request management subsystem.

4.5 Deployment Diagram

A deployment diagram models the run-time architecture of a system. It shows the
configuration of the hardware elements (nodes) and shows how software elements and
artifacts are mapped onto those nodes. UML deployment diagrams are used to depict the
relationship among runtime components and hardware nodes. Components are
selfcontained entities that provide services to other components or actors. A Web server, for
example, is a component that provides services to Web browsers. A Web browser such as
Netscape is a component that provides services to a user. A distributed system can be
composed of many interacting run-time components. In UML deployment diagrams, nodes
are represented by boxes containing component icons. Dependencies between components
are represented by dashed arrows the purpose of deployment diagrams can be described as:

• Visualize hardware topology of a system.

• Describe the hardware components used to deploy software components.
• Describe runtime processing nodes.

42
 Figure 16. Deployment diagram

4.6 System Architecture

System architecture refers to overall and design and structure of a system, including the
hardware, software, and network components, as well as the relationship and interaction between
these components. The specific design of system architecture will depend on the requirements
and goals of the project. Some common elements of a system architecture include data storage,
processing, communication and security. The overall design should ensure that the system is
reliable, scalable, and able to meet the performance requirements of the project

43
4.7 User Interface (UI) Design
User Interface (UI) design focuses on anticipating what users might need to do and
ensuring that the interface has elements that are easy to access, understand, and use to
facilitate those actions. The goal of user interface design is to make the user’s interaction as
simple and efficient as possible, in terms of accomplishing user goals.

Figure 17. Home Page

44
Figure 18. Customer page

45
 Figure 19.Admin Page

46
4.8 User Interface flow Diagram

Figure 20.User Interface Flow diagram

47
Recommendation
Even if the company has performed rent, the project is limited to only rent cars mechanical
service. Therefore, the project team suggests these features need to be incorporated in any
further revision and extension attempt and also the payment process still involves the appearance
of customers physically so the project team suggests to make the payment process done online.

48
Conclusion
The project titled Web Based car rental system for Bereket and Gezahagn car Rental Company’s
easy to use and access i.e. no need of detail computer skill to use and access. The project aim is
to build a web-based system which have greater usage on bringing the existing system fully
functional and it have greater functionalities to enhance effectiveness and efficiency related
parameters on the system. The project achieves the objective listed on the document, functional
and nonfunctional requirements, and the problems listed in the first document part, and done with
project scope appropriately.

49
Reference
cali. (2004, march 2). wikipidia. Retrieved fab 29, 2023, from wikipidia.org:
https://www.wikipidia.org
creately. (2008, apr 7). creately.com. Retrieved fab 29, 2023, from creately: https://creately.com
freeprojectZ. (2018, march 13). freeprojectZ. Retrieved fab 29, 2023, from freeprojectZ.com:
https:// freeprojectZ.com
itsourcecode. (2021, july 2). itsourcecode. Retrieved fab 29, 2023, from itsourcecode.com:
https:// itsourcecode.com
Itsourcecode. (2021, dec 1). Itsourcecode. Retrieved fab 29, 2023, from Itsourcecode.com:
https:// Itsourcecode.com

50
Appendix
1. How and when your company established?
2. What is the objective of this Company?
3. What is mission and vision of your company?
4. Who are the users of this company?
5. How does the current system works?
a) Is it manual?
b) Is it computerized?
c) Is semi computerized?
6. What are the procedures or steps involved when customers to rent car?
7. What is rule or qualification that your company expect from the customers?

Appendix A: diagram used during development

Symbol Definition

51
 Compo
t
Name

Actor

Use case

Package

Component

Node

Activate

Message return

52
 Line Connector
Message

Final state

Stop or Terminate

Relationship

Decision

Entity

53
54
55