NEW GENERATION UNIVERSITY COLLEGE

DEPARTEMENT OF COMPUTER SCIENCE

TITLE: Web Based Car Rental Management System

Student’s Name ID No.

1. Tigist Yohannes 05932/10

2. Sara Kassahun 05708/10
3. Kalab Gizaw 05862/10
4. Dawit Tolla 05817/10

A PROJECT SUBMITTED TO THE DEPARTMENT OF COMPUTER SCIENCE IN

PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF
BACHELOR OF SCIENCE IN COMPUTER SCIENCE

March 2022
Addis Ababa, Ehiopia
Table of Contents
List of Acronyms ......................................................................................................................... IV

Acknowledgment .......................................................................................................................... V

List of Tables ............................................................................................................................... VI

List of Figures ............................................................................................................................. VII

Chapter 1: Introduction ............................................................................................................... 1

1.1 Introduction .................................................................................................................... 1

1.2 Background of the project ............................................................................................. 1

1.3 Statement of the Project ................................................................................................ 2

1.4 Objectives ........................................................................................................................ 2

1.4.1 General Objective ................................................................................................... 2

1.4.2 Specific Objective .................................................................................................... 2

1.5 Feasibility Study ............................................................................................................. 3

1.5.1 Operational Feasibility ........................................................................................... 3

1.5.2 Technical Feasibility ............................................................................................... 3

1.5.3 Economic Feasibility ............................................................................................... 3

1.5.4 Schedule Feasibility ................................................................................................ 3

1.6 Scope and Limitation of the Project ............................................................................. 3

1.7 Beneficiaries .................................................................................................................... 4

1.8 Methodology and Tools.................................................................................................. 5

1.8.1 Data Gathering Techniques ................................................................................... 5

1.8.2 System Development Tools..................................................................................... 5

1.9 Estimated Budget ........................................................................................................... 7

1.10 Tasks and Schedule ........................................................................................................ 8

1.11 Organization of the Project ........................................................................................... 8

I
Chapter 2 ....................................................................................................................................... 9

2. Description of Existing System ............................................................................................. 9

2.1 Introduction to Existing System ................................................................................... 9

2.2 Players in Existing System ............................................................................................. 9

2.3 Major Functions in Existing System............................................................................. 9

2.4 Business Rule ................................................................................................................ 10

2.5 Forms and Documents used in Existing System ........................................................ 10

2.6 Bottleneck of Existing System ..................................................................................... 10

2.6.1 Performance .......................................................................................................... 11

2.6.2 Input and Output .................................................................................................. 11

2.6.3 Security .................................................................................................................. 11

2.6.4 Efficiency ............................................................................................................... 11

2.7 Practice to be Preserved .............................................................................................. 11

2.8 Proposed Solution for new System that Address Problems of Existing System ..... 12

2.8.1 Alternative Solution .............................................................................................. 12

2.8.2 Overview of the Proposed System ....................................................................... 12

2.9 Requirements of the Proposed System ....................................................................... 13

2.9.1 Functional Requirements ..................................................................................... 13

2.9.2 Non-Functional Requirements ............................................................................. 13

Chapter 3: System Analysis ....................................................................................................... 15

3.1 Introduction .................................................................................................................. 15

3.2 System Requirement Specification (SRS) .................................................................. 15

3.2.1 Use Case Diagram ................................................................................................. 15

3.2.2 Use Case Documentation ...................................................................................... 16

3.2.3 Sequence Diagram ................................................................................................ 21

II
 3.2.4 Activity Diagram ................................................................................................... 24

3.2.5 Analysis Level Class Diagram.............................................................................. 26

3.2.6 Supplementary Specification ............................................................................... 27

Reference ..................................................................................................................................... 28

III
 List of Acronyms
Abbreviations Expanded

HTML Hypertext Markup language

CSS Cascade Stylesheet

UML Unified Modeling Language

ID Identification Number

DB Database

CD Compact disc

IV
 Acknowledgment
First and foremost, and above all our biggest thanks would be to Almighty God because nothing
could be possible without his free will and the completion of this project is supported by him.
Secondly, we would like to thank our Advisor Instructor Yonas for his restless edition of our
documentation, input to the quality of this document, heart full guidance, valuable advice, and
providing to execute this project. Finally, the last but not the least, we would like to thank even if
it is usual the group members would like to thank each other. The main contributors to do this
document project are teamwork, friendship and the belief that we may achieve something we set
out to do. We also hope that this project and documentation may be testaments to our continued
friendship and better work. Without helps of the particular that mentioned above, we would face
many difficulties while doing this.

V
List of Tables
Table 1. 1 Estimated project cost .................................................................................................... 7
Table 1. 2 Project Schedule ............................................................................................................ 8
Table 3. 1 Login Use Case Documentation .................................................................................. 17
Table 3. 2 Search car use case documentation .............................................................................. 18
Table 3. 3 Add car use case documentation .................................................................................. 18
Table 3. 4 Update car use case documentation ............................................................................. 19
Table 3. 5 Generate report use case documentation ..................................................................... 19
Table 3. 6 Rent car use case documentation ................................................................................. 20
Table 3. 7 Manage Booking use case documentation ................................................................... 21
Table 3. 8 Cancel booking use case documentation ..................................................................... 21

VI
List of Figures
Figure 3. 1 Web-based Car Rental Management System Use Case Diagram .............................. 16
Figure 3. 2 Login sequence Diagram ............................................................................................ 22
Figure 3. 3 Register car sequence diagram ................................................................................... 22
Figure 3. 4 car rent sequence diagram .......................................................................................... 23
Figure 3. 5 Search car sequence diagram...................................................................................... 23
Figure 3. 6 Login activity diagram ............................................................................................... 24
Figure 3. 7 Add car activity diagram ............................................................................................ 25
Figure 3. 8 Search car activity diagram ........................................................................................ 26
Figure 3. 9 class diagram .............................................................................................................. 27

VII
Chapter 1: Introduction
1.1 Introduction
People travel from one place to another for many reasons, some due to their jobs or business
and few for holidays and vacations. As a traveler they cannot own a car in every place or country
they go, they always prefer other options like public transports, cabs, busses, trains and rent cars.
Getting a car on rent has become very famous due to the cost as it is much cheaper than using cabs
for a whole day and because it is much more secure and convenient

House & car sale/ rent sector remains a day-to-day activity of most of the society of the capital
city of Ethiopia. Someone needs to buy or rent a car/house. The customers need different kinds of
cars for different purposes. And also, they need house for living, for trade, for events, for
organization and many more. Not only for different kinds of purposes but also, they need different
kinds of house like villa, 2 bed rooms, 1 bedroom, G+1/+2., building, and even a compound.
Renting of a car may be for single day, a couple of days, for a week, for a month and may be for a
year depend on the interest of the customer. The same is true for house renting. The payment for
the service varies according to the number of days the user rent car/house.

However, some House & car rental agencies still use a manual system to manage rental
operations by spreading of their available House and car to local resident. This method cost wasting
of money and time for both rental person and owner. Therefore, Online House and Car rental has
been developed to tackle the existing system drawbacks.

1.2 Background of the project

In coping with the globalization of information technology, computer had played an important
role in an organization or company. Most of the organization used computerized system in
handling all their activities regarding with data processing in order to make the organization
operation more efficient. All the manual activities are now can be done using computerized system.
Although computerized system had been implemented within an organization, the manual system
can still be used as guidance.
Online car and house rental system is a web-based application that is developed for existing
system in order to replace the current manual way used by the organization. Using the manual
way, there are: a lot problems arise that can cause difficulty to the car and house renter and also

1
lot the, management team of the organization. Hopefully. By developing this system. It will help
the entire user to overcome the problem faced by them and make the car and house rental operation
easier.
Online car and house rental system is the most known system in developed countries. Its main
goal is to serve customers in many activities. From this the renter can rent the house for weeding,
for vacation, for trip and some other activities.

1.3 Statement of the Project

The current system has the following problems: -

➢ Resource consumption: -it needs resources like man power, cost, and time, documents to
fill users or customer’s information and others.
➢ Data redundancy: -some data are duplicated because of the system is manual.
➢ It is not user friendly: -the manual system is difficult to users. The user must go physically
or make a phone call to rent.
➢ Difficulty in checking car and house: -without checking the document the organization can
not differentiate the car and house reserved.
➢ No more customer satisfaction: -customers cannot reserve the car and house by their wish
➢ Security issues: - the existing manual system is data is recorded on paper therefore it is
exposed to damage and data loss.
Due to those problems, we have proposed to develop online car and house rental management
system. The developed system allows users to rent car and house online. It saves users time and
money.

1.4 Objectives
1.4.1 General Objective
The general objective of the project is to design and implement a web-based car and house
rental management system.

1.4.2 Specific Objective

The specific objectives of our project are:

▪ To elicit or gather the requirements of the system

▪ To analyze these requirements of the system
▪ To design the system
2
 ▪ To implement the system
▪ To test the system

1.5 Feasibility Study

1.5.1 Operational Feasibility
Most of the current car and house rent users are educated and able to using the developed
system: mostly they are easily adaptable to computer system. Hence, our system is operationally
feasible. From other point of view operational feasibility ask, does the system solve the existing
problem after the proposed system is implemented? Yes, because it is simple to access and all
operations will be performed easily. The proposed system solves the current manual system of the
car and house rental management system.
1.5.2 Technical Feasibility
The team members have sufficient knowledge to design and implement the system using
current software technologies like PHP, MYSQL, Java script, CSS and so on; from this point of
view our system is technically feasible. As the current car and house renting organizations has
clear vision to be the best for their customers, they have a plan to purchase required number of
desktops computers required for the system.
1.5.3 Economic Feasibility
To design and implement the system, we use a limited budget and it address basic problem
in the case of economic way after automating it, particularly reduces manual resources to record
information and it reduces man power; so, it prevents the existing system from expenses of salary
for more workers. Therefore, from this point of view our system is economically feasible.
1.5.4 Schedule Feasibility
Though the time that would be used for this project partly as an academic practice for
designing and developing information systems is within a very tight and short academic schedule,
we the group members tried to divide and share the tasks and focus on the main functionalities of
the system so as to complete with in the academic schedule.

1.6 Scope and Limitation of the Project

Our proposed system web-based car and house rental management system mainly concerns about
information related with renters and customers by covering the following functionalities:

Login

3
 Car and House management (add, update, delete, search)
User management (add, update, delete, search)
Customer management (add, delete, update, search)
View the available cars and houses
Rent car and houses
Check the rented car and house status
Generate report for number of cars and house rented per week, month, etc.

The scope of this project is developing web-based system that is able to recommend car and
house to be rent by the user based on requirements, provide car catalog for users and it allows the
organization to view user information from the database if they registered or not and updating
database. Customers as well as the organization’s staff will be able to use the system effectively.

The limitation of the project is there is no online payment system. The payment still needs to
be performed using other methodology.

1.7 Beneficiaries
Our proposed system aimed to change the current system in to computerized system in order
to make many operations related to customers and renters on the way of easy, fast, duplication
controlled and organized manner. This application enables registering car and house, recording
customers information and recording car and house information.

In general, the application helps the renters and customers to enhance quality of renting service.
For customers it saves time by providing the following benefits:
❖ Maximizing of performance and quality of service.
❖ It gives efficient and error free work
❖ Minimize wastage of resources such as human labor, paper, pen and others
❖ It will improve monitoring capacities of the renting and returning activities
❖ It saves time

Our proposed system targets the following users:

➢ Admin: can easily register car and house to the system without wastage of time.
➢ Customers: get services without wasting their time.
➢ Property Owners: Follow the status of the car and house easily

4
1.8 Methodology and Tools
1.8.1 Data Gathering Techniques
To collect all necessary data and information we use the following techniques
a. Interviewing: We have gathered information by face to face interviewing the current
renting service organization. We choose this method to get detailed information about the
system.
b. On job Observation: We observed the activities of the renting service physically that the
workers were processing activities like renting house and car, searching cars and houses,
adding cars and houses and we also observed how they generate report related to cars and
house rented. We choose this method to get information how the activities are
implemented. It enables us to list out the existing system problems, since it is what we see
or observe in reality.
c. Discussion: We discussed that how the customers get serve from the current system and
rent. We choose this method to get necessary information from our feeling.
d. Document analysis: We referred some previously done rent management projects from
different websites. We choose this method to have detailed awareness about our project.

1.8.2 System Development Tools

1.8.2.1 Software tools
➢ Apache webserver
➢ Web browsers
➢ PHP: The main reasons why we selected PHP programming to develop our system
described as follows:

✓ Simple and easy to learn

✓ Support
✓ Free
✓ Easier to fix problems
✓ Scalability
✓ Object Oriented
✓ Speed

5
➢ Java Script: We choose this language to make so many validations included in our project.
We have the following reasons that we used it to develop our project:
✓ Dynamic Computer Programming
✓ It is a multi-paradigm language, supporting object-oriented, imperative,
and functional programming styles.
✓ The application of JavaScript to use outside of web pages
✓ We only knew java script programming language to validate forms and
other interfaces
➢ HTML5 and CSS: Reasons why we selected them are:
✓ cost effective Multiplatform Development
✓ better user experience
✓ Offline browsing

➢ MYSQL: It has the following main features caused as to select it:

✓ Performance

✓ Open Source

✓ Reliability

✓ Portability

➢ Microsoft office: word 2019, PowerPoint, Visio 2019.

➢ Notepad++ and VS code: to write the source code of this project implementation

➢ Operating System: windows 10 platform.

1.8.2.2 Hardware Tools
✓ Laptop Computer
✓ CD
✓ Flash disk

6
1.9 Estimated Budget
The estimated cost of the project is summarized in the below table
Types of costs Tool name Quantity Unit price (in Total price (in
Birr) Birr)
Flash (4 GB) 1 300 300
Pen 6 3 18
Paper 1 packet 100 100
Printer 1 7,000.00 7,000.00
Notebook 1 30 30
Laptop Computer 1 30,000.00 30,000.00
32 GB Hard disk 1 200.00 200.00
Memory
PHP (XAMPP) server 1 Free Free
Microsoft office 2019 1 Free Free
Software costs Notepad++, VSCode 1 Free Free
Adobe Photoshop 1 Free Free
Windows 10 OS 1 Free Free
Micro soft Visio 2019 1 Free Free

Miscellaneous cost - - 150

Total cost - - - 37,648.00

Table 1. 1 Estimated project cost

7
1.10 Tasks and Schedule
The project over all activity and their time frame is ser in next table.

Tasks Months
No Steps Nov1- Nov De Dec F M App May June
16 17- 03-18 19- e ar
Dec Jan b
02 12
1 Proposal
preparation
and
Presentation
2 Data collection
and
Requirement
specification
3 System
analysis
4 System design Table 1. 2 Project Schedule
5 Implementatio
n
6 Testing
7 Documentatio
n
Total Overall project
time

1.11 Organization of the Project

In this document we are discussing system details through each chapter, in chapter one
includes introduction, background, objective of the project, scope, and also include specific of the
project. Chapter two deal about features of the system that includes over view of the existing
system, proposed system, functional requirement, non-functional requirement, analysis model
which includes use case diagram with corresponding documentation and actor, sequence diagram
and finally contains class diagram, chapter three contains system design that includes software
Architecture of the system, sub system decomposition, deployment diagram ,class type
architecture, documenting classes and persistent data management of the system. Chapter four
discus the implementation of the proposed system, sample code and conclusion.

8
Chapter 2
2. Description of Existing System
In this phase, we try to list the Background of the existing system, Problem of the existing
system, Constraint (business rule) of existing system and proposed solution for the problem of
existing system.

2.1 Introduction to Existing System

Car and house rental system is a daily activity. It provides different types of services such as
rent different types of cars to different types of purpose, house, building and other services to the
community. It works together with the property owners and other external organizations in order
to make renting process much suit by sharing different experiences, habits.

The current renting organization gives the following services: -:

✓ Acquisition services of cars & house from the owners
✓ Organizing and classification of cars and house by service and type
✓ Renting service for users

2.2 Players in Existing System

➢ Customers: customers can rent either car or house.
➢ Brokers: the brokers do arrange cars and houses, classify houses based on type or brand,
give help for the customer’s, manage car and house renting activity.
➢ Property Owner: follow the status of their property alongside with the broker.

2.3 Major Functions in Existing System

Out target area give services to its customers in different ways. The organization has
participants like customers, owners, broker, and other staffs. The broker has a great role and
responsibility to manage the overall functionality of the current system. The broker has the
responsibility to manage the overall activities of the renting service to the users.

Generally, the main functionalities the existing system perform includes the following

✓ Car and House management (add new car and house, manual controlling)
✓ Rent management (rent cars and house, check return with the form)
✓ Help user to get the required service by the broker

9
 ✓ Add new cars and house to the rent list.

2.4 Business Rule

A business rule is an operating principle or policy that must be fulfilled in order the system
function properly and effectively. It often relates to access control issue, business calculation,
operating policy and principle of the organization. These business rules include: -

Rule1: only appropriate users can rent the car or house.

Rule2: user can rent 1 car or house at a time.

Rule3: the customer must have renewed kebele ID or passport to rent car or house.

Rule4: the customer must return the with in specified dates in the agreement.

Rule5: customers can’t rent car or house who didn’t fulfill the required information.

Rule6: Service charge is applied on every service given by the system.

Rule7: Normally the owner expects customers to make payment before they rent the vehicle.

2.5 Forms and Documents used in Existing System

One of the main forms currently used by the brokers is the form used for renting cars.

The form contains the following user information: -

▪ Customer full name

▪ Copy of Kebele ID or passport
▪ Rented date
▪ Price per date
▪ Total price
▪ Car type, model, number of seats
▪ Signature of both broker and customer
▪ Remark (returned or not)

2.6 Bottleneck of Existing System

The existing system accomplish its task using manual approach; hence it has a lot of problems. Some of
the major problems are discussed below: -

10
 2.6.1 Performance
In terms of the performance or response time of the existing system take more waiting time for
the customers and renter to rent a car or house, for brokers to get newly cars and house for rent
and also to manage the rented car status books of the library. Thus, the existing system has more
computational time.
2.6.2 Input and Output
The existing system needs more manpower since a lot of paper work and forms were filled by
users to rent a car. The broker also performs a lot of searching and phone call to get information
about cars those have been rented.
2.6.3 Security
The existing system is not secured since lots of essential users’ information are not placed in
secured place and they are exposed easily if there is fire and theft etc.
2.6.4 Efficiency
The existing system is not efficient.
✓ Manual usage: require wastage of resources like time, paper, pen and all stationary
materials used.
✓ Lack of centralized source of information: because the information store in different
places manually.

2.7 Practice to be Preserved

In the existing system uses manual way. That is not to mean that the existing system has only
weakness but also there are strong sides that are not replaced by existing system such as when user
sign to take the car. From the existing system we will add the following things to our proposed
system

➢ For individual customer there is a unique customer ID card.

➢ All forms and documents mentioned above must be preserved.
➢ Using of Vehicle ID, which makes renting of vehicles simple and easy.

11
2.8 Proposed Solution for new System that Address Problems of Existing
System
2.8.1 Alternative Solution
As we have described before the current system faces a lot of problems like availability,
performance, customer satisfaction and security due to manual system. The best alternative
solution to the existing system is to change manual system to web-based online system that
simplifies the problems listed above.

2.8.2 Overview of the Proposed System

The system that we are going to develop can solve problems that we have mentioned in the
existing system. The proposed system is web-based online system. This system is deployed on a
server with proper security measures. Clients (users) can connect through the internet with a web
browser (example: - google chrome, internet explorer, Mozilla Firefox etc.) to access the system.

The proposed system has the following functionalities: -

• Customers can search for available cars and get the result easily
• Only authorized users can access the system due to this we can maintain security
• The system administrator can add, update, and manage users and cars
• The proposed system is used to store cars and users’ information

Advantage of the Proposed System

• Performance: - it can give result for user queries with short period of time
• Availability: - the proposed system is available 24/7
• Maintainability: - the proposed system is easily maintainable

Disadvantage of the Proposed system

• The proposed system does not include online payment

• The system only works online

12
2.9 Requirements of the Proposed System
2.9.1 Functional Requirements
Functional requirements are the intended behaviors of the system. This behavior may be
expressed as services, tasks or functions that the system is required to perform. Since we are going
to develop a web-based application for online vehicle rental system the system will have different
functions some of the function are:

➢ Login: - to identify the authorized person to use the system

➢ Reserve Vehicle: - The system shall allow staff to display customers, who rent cars.
➢ View Reservation: -the system allows the staff to view reservations of cars/house those
are reserved and which are available for customers.
➢ Car Registration: -the system allows the manager to add new cars/house to the system
for customers to choose from and increase their satisfaction.
➢ Rent registration: - the system allows customer to register for renting cars/house.
➢ Update Rent: -the system should allow the staff/employee or manager to update rent
where customer wants to add days for use cars more than rent registration agreements and
to cancel their registration.
➢ View car: -the system should allow customers, staff and others to view cars available
for rent and which are reserved by customers.
➢ Update car: -the system shall allow the manager to drop or deleted cars that have already
rented from the database.
➢ Cancel Reservation: -the system allows the customer to cancel the renting agreement
online.
➢ Generate report: -the system allows manager to generate reports about rented, reserved or
free cars.
2.9.2 Non-Functional Requirements

Non-functional requirement is a requirement that specifies criteria that can be used to judge the
operation of a system, rather than specific behaviors. Non-functional requirements are often called
qualities of a system. Other terms for non-functional requirements are "constraints", "quality
attributes", "quality goals" and "quality of service requirements". Qualities, that is, non-functional
requirements, can be divided into two main categories:

13
➢ Performance: The System should quickly respond for user request that is system must
immediately display the needed service along with their allocation details after he/she
insert needed information to view.
➢ Attractive user interfaces: The system interface must be interactive and easily
understandable.
➢ Security: There must be authorization; unauthorized person does not use the system; the
system users work their duty according to their privileges by using their username and
password.
➢ Portability: Our system should portable on any window operating system and work
properly on any browsers.
➢ Robustness: The system should announce when the user enters invalid data; this can be
done it displays an error message when a user fills inappropriate entry.

14
Chapter 3: System Analysis

3.1 Introduction
This chapter deals with analyzing the proposed system by using different UML analysis
modeling techniques such as use case diagrams, the use case descriptions (scenarios), sequence
diagrams, activity diagrams, analysis class diagram, and user interface prototype.

After identifying the actors and use cases, the use cases are developed and textual
descriptions (scenarios) are stated. The Sequence diagram id depicted based on the use cases which
are developed for the proposed system. Activities will be represented by the activity diagrams.

3.2 System Requirement Specification (SRS)

3.2.1 Use Case Diagram
The use case is the most essential diagram for overall activities. It is the most required for
paved the way from the beginning to the end. Use cases are designed to model a systems behavior
without defining the core value of the application. An actor typically initiates a use case and derives
some benefit from its use. This benefit may be realized by the actor who initiated the use case, but
it could also be a different actor. An actor may be an actual person, another system, or even a
hardware device, but it always represents a set of roles that will be interacting with the system
from the outside.

The following are the use cases identified for developing use case diagram of the web-
based library management system: -
➢ Login
➢ Car management (adding, searching, deleting, updating)
➢ User account management (adding, searching, deleting, updating)
➢ Customer management (adding, searching, deleting, updating)
➢ View the whole cars
➢ Rent cars
➢ View rented cars
➢ View returned cars
➢ Generate report

15
 Figure 3. 1 Web-based Car Rental Management System Use Case Diagram

3.2.2 Use Case Documentation

Use case name Login
Actor Admin, Customer
Description It allows the user to log in to the system

Precondition the user must have correct user name and password

16
Basic flow of events 1. User clicks the login button
2. System displays login window
3. User fills his/her username and password[A]
4. User submits the form
5. System authenticates the user
6. System displays application main window with the form
Alternative condition A: if user name or password is incorrect
Alt A-1: The system verifies that the username and password is
incorrect
Alt A-2: The system shows an error message that shows the
username or password is incorrect
Alt A-3: Resume use case to step 3
Post condition System user logged in to the system

Table 3. 1 Login Use Case Documentation

Use case name search books

Actors Admin, customer

Description Allow the admin and the borrower to search for books

Precondition The admin or the user must know at least one book information

Basic flow of events 1. The admin or the user clicks the search button
2. The system displays the search form
3. The user enters the search keyword
4. The user click search button
5. The system displays the information needed [A]
6. The use case ends
Alternative course of action A: Step 4. If the item that is going to
be searched for is not available, system displays no item is match
Alt A-1: The system verifies that the item is not match

17
 Alt A-2: The system shows an error message that shows the item is
not match
Alt A-3: Resume use case to step 3
Post condition The user will get the requested information
Table 3. 2 Search car use case documentation

Use case name Register cars

Actor Admin
Description Allow the admin to register cars to the system

Precondition the admin must login to the system

Basic flow of events 1. The admin selects the information he/she want to add
2. The system displays the selected menu
3. The admin clicks the add button
4. The system displays the add form
5. The admin fills the form
6. The admin submits the form
7. The system checks the validity of the information inserted
8. The system adds the information in to the database
9. The use case ends
Alternative course of action A: Step 5. If the admin misses the
information the system displays fill the required field message
Alt A-1: The system verifies that the validity of information
Alt A-2: The system shows an error message that shows the detail
is missed
Alt A-3: Resume use case to step 5
Post condition the required information will be added
Table 3. 3 Add car use case documentation

18
Use case name Update car
Actor Admin
Description Allow admin to modify the detail from the database
Precondition the admin must log in to the system
Basic flow of events 1. The admin selects the menu he/she want to update
2. The system displays the selected menu
3. The admin searches the required information to edit
4. The system displays the information with the edit button
5. The admin clicks the edit button
6. The system displays the update form
7. The admin edits the information
8. The admin submits the form
9. The use case ends
Post condition the information or detail will be updated
Table 3. 4 Update car use case documentation

Use case name Generate report

Actor Admin
Description Allow the admin to generate report

Precondition The admin must log into the system

Basic flow of events 1. The admin clicks the report button from the menus
2. The system displays all operation for which report to be
generated
3. The admin selects the required operation for which report
to be generated[A]
4. The system displays the needed information
5. The admin informs the system to generate a report
6. The system generates the report
7. The use case ends
Post condition report will be generated
Table 3. 5 Generate report use case documentation

19
Use case name Rent car
Actor Customer
Description Allow the customer to rent car

Precondition The customer must login to the system

Basic flow of events 1. The customer searches a car to rent
2. The system displays the available cars
3. The customer selects a car to rent
4. The system displays the rent form
5. The customer fills the form and submit
6. The system verifies the information and save to database
[A]
7. The use case ends
Alternative course of action A: step 6 If the customer information
is not valid, the system displays an error massage
Alt A-1: The system verifies that the user misses the rent form
Alt A-2: Resume use case to step 5
Post condition The user can rent car
Table 3. 6 Rent car use case documentation

Use case name Manage booking

Actor Admin
Description Allow the admin to manage customer bookings

Precondition the admin should login to the system

Basic flow of events 1. The admin clicks the manage menu
2. The admin selects the record to be managed
3. The system displays the information with edit button
4. The admin selects the approve/delete record
5. The system display confirmation window
1. The system displays that “are you sure to
approve/delete the booking”
2. The admin clicks “yes” button

20
 3. The use case ends
Post condition The user booking will be approved or deleted
Table 3. 7 Manage Booking use case documentation

Use case name Cancel booking

Actor Customer
Description Allow the customer to cancel customer booking

Precondition the customer should login to the system

Basic flow of events 1. The customer clicks the cancel booking button
2. The system displays the information to be canceled
3. The customer click cancel
4. The system display confirmation window
1. The system displays that “are you sure to delete
the booking”
2. The customer clicks “yes” button
3. The use case ends
Post condition The user booking will be deleted
Table 3. 8 Cancel booking use case documentation

3.2.3 Sequence Diagram

Sequence diagrams show the interaction between participating objects in a given use case.
They are helpful to identify the missing objects that are not identified in the analysis object model.

21
 Figure 3. 2 Login sequence Diagram

Figure 3. 3 Register car sequence diagram

22
 Figure 3. 4 car rent sequence diagram

Figure 3. 5 Search car sequence diagram

23
 3.2.4 Activity Diagram
Activity diagram used to emphasize the flow of control from activity to activity or to model
the flow of an object as it moves from state at different points in the flow of control.

Figure 3. 6 Login activity diagram

24
Figure 3. 7 Add car activity diagram

25
 Figure 3. 8 Search car activity diagram

3.2.5 Analysis Level Class Diagram

• It represents the properties of entities, their operations and relationships. Also, it drives use
case diagrams from use case.
• The class diagram is the main building block in our project modeling.
• It is used both for general conceptual modeling of the systematic of the application and for
detailed modeling translating the models into programming code.
• The classes in a class diagram represent both the main objects and or interactions in the
application and the objects to be programmed.
• Generally, the project is including the following class in the class diagram the over view
of the class diagram is: -

26
 Figure 3. 9 class diagram

3.2.6 Supplementary Specification

➢ All the buttons used in the program should be consistent throughout the program.
➢ The GUI should be easily customized.
➢ The GUI should be easily understandable.
➢ The systems in general have a good graphical user interface that enables the users to
use it easily.

27
Reference
1. The web (Internet) particularly
➢ www.w3c schools.com
➢ www.google.com
➢ www.youtube.com

2. M.Jackson, Software Requirement and Specifications: A Lexicon of Practice, Principles

and Prejudices. Addison -Wesely, Reading, MA, 1995.

28