SOFTWARE ENGINEERING DEPARTMENT

Project PLAN (SWE 205)

PROJECT NAME:

Car Rental Management System

Submitted By:
STUDENT NAME ID
 Rafa almutairy
 Kanood aljmily
 Shahad almutairy
 Shahad alshamry
 Aisha alanzy
 Randa alharthy
 Nora Shaalan alshamry

Supervised By:

2022-1443
 LIST OF CONTENTS

CHAPTER I:
1.1Project overview. ........................................................................................................... 2
1.2 Problem Statement. ....................................................................................................... 2
1.3 project objective ............................................................................................................ 2
1.4 software process model ................................................................................................. 3
1.5 Team organization ........................................................................................................ 4
1.6 Risk analysis ................................................................................................................. 4
1.7 Hardware and software resource requirements ............................................................. 6
1.9 Project schedule ............................................................................................................ 6
CHAPTER II requirements and UML diagrams
2.1 Overall system requirements......................................................................................... 8
2.2 Specific system requirements ....................................................................................... 8
2.3 Non-functional requirements ...................................................................................... 10
2.5 Use Case: .................................................................................................................... 11
CHAPTER III: Design
3.1 The context and modes of use of the system .............................................................. 15
3.2 The system architecture design ................................................................................... 15
3.3 The principal system architecture .............................................................................. 16
3.4 Design models ............................................................................................................. 16
3.4.1 Activity Diagram: .................................................................................................... 16
3.4.2 Sequence Diagram1 (Generic Scenario): ................................................................. 18
3.4.3 State Diagram: ......................................................................................................... 20
3.4.4 Class Diagram: ......................................................................................................... 21
CHAPTER IV :Prototyping
4.1 explain the interfaces for your project ........................................................................ 23
4.2 Teamwork ................................................................................................................... 26
Conclusions ....................................................................................................................... 27
refernces ............................................................................................................................ 28
CHAPTER 1

1
1.1 Project Background:

The car rental system appears to be a software-based car rental system. Technology allows
an organization to make items available to the general public across the web even if they
are tracked [1]. Together, the world has grown into an area of rapid technical progress,
where practically everything is being converted into a digital form. Person occupations
have actually been transformed into computer-assisted jobs in recent years. Another goal
was the primary goal of the project, an online car rental scheme Most people’s plans for
commuting and moving from one area to another for business, tours, visits or vacations
entail the use of a car, and for certain factors, car rental becomes very beneficial [2]. Car
rental packages are available everywhere around the world, especially in developed and
emerging economies. To make the services increasingly prominent as well as accessible to
the public, this has been transformed into a web-based system that is interconnected and
available to anyone online. After making the rental, customers will book a car online based
on their needs and preferences.

1.2 Problem Statement:

Car rental is a vehicle that can be rented for a price and used for a specified period of
time. Having a rental car makes it easier for people to move around when they don't
have access to their own car or don't own one at all. A person who needs transportation
must contact the car rental company and sign a contract. This method improves
customer retention while making vehicle and employee management more
straightforward.

1.2.1 Proposed Solution:

Create a web-based system that allows consumers to register and reserve cars online
while also allowing the company to efficiently manage its car rental business. To
facilitate the process of renting a car for consumers.

1.3 PROJECT OBJECTIVES:

1. Automated car rental management.

2. Reducing the suffering of searching for a means of transportation.
3. Easy to communicate and search for a taxi at any time.
4. Solve the problem of wasting effort and time while people search for a suitable taxi
5. Customers and corporate employees will be able to make good use of the system.
6. The web platform means that the system will be available 24 hours a day, seven days a
week, except for minor server outages.

2
1.4 SOFTWARE PROCESS MODEL
We used the waterfall model because it is the most popular model and it is very simple and
easy to understand. It is also called a linear model. Here each stage begins only after the
end of the previous stage and there is no overlap in these stages. This model can be applied
to projects where: The requirements are known and clearly defined. The technology and
development tools are familiar. For short and simple projects. For example, a car rental and
reservation system

CAR RENTAL
MANAGEMENT SYSTEM

1.1 Initiation
1.1.1 Project overview
1.1.2 Problem Statement
1.1.3project objective
1.1.4 software process model
1.1.5 Team organization
1.1.6 Risk analysis
1.1.7 Hardware and software resource requirements
1.1.8 Project schedule
1.2 requirements and UML
1.2.1 Overall system requirements
1.2.2 Specific system requirements
1.2.3 Non-functional requirements
1.2.4 System UML diagram

1.3 Design
1.3.1 context and modes
1.3.2 system architecture
1.3.3 system architecture
1.3.4 Design models

1.4 Prototyping
•1.4.1 prototype for the
•1.4.2 projectTeamwork

3
 1.5 TEAM ORGANIZATION
1 List of student members’ names, IDs, and roles. Each of the following roles must be assigned to
one student (a student can have multiple roles):

id Name Roles
1 Rafa almutairy Risk analysis& system architecture design

2 Kanood aljmily Hardware and software requirements& principal system architecture&

context and modes of use of the system
4 Shahad almutairy Risk analysis & Design models& context and modes of use of the system

5 Shahad alshamry Risk analysis& system architecture design & Prototype

6 Aisha alanzy Project overview& Overall system requirements& Prototype

7 Randa alharthy Problem Statement& Specific system requirements &Prototype

8 Nora alshamry project objective& Non-functional requirements& Prototype

1.6 RISK ANALYSIS

(Table)Risk identification, risk estimation

IDENTIFICATION, RISK - Risk Category Probability Impact (1-

4)
1 Poor quality of documentation - Project risks 20% 2

2 Deviation of software engineering standards - Technical risks 30% 1

3 Computers malfunctioning - Business risks 30% 2

4 Technology that does not meet expectations - Technical 40% 4

5 Late delivery time - Project risks 10% 3

6 The ultimate system resistance for users - Technical Issues 20% 4

7 Change In Car Rental Management System - External 10% 3
Requirements
Impact Values: (1 – Catastrophic(1) ,2 – Critical (2) 3 – Marginal (3) 4 – Negligible(4)

4
 - Risk Mitigation Strategies

Poor Quality of In order to prevent this from happening, the members responsible for the
Documentation preparation of the documents will remain in contact with each developer
in the Group. Meetings will be held routinely to make proposals on
documents and topics. Any subject considered missing by a particular
Mitigation developer will be discussed and whether or not you want to add this
specific subject to the documents. In addition, my home lab will be
questioned about their opinion on the documents.
Deviation of software That it is possible to deviate from software engineering standards, this is
Mitigation

engineering standards unlikely to happen. All team members have a complete understanding of
the software process and how we plan to implement it in the process.
Add software engineering standards review
Computers The cost associated with computer failure resulting in data loss is critical.
Mitigation

malfunctioning As a result, the organization takes steps to make multiple backup copies
of the program in a file. Formula development and all associated
documentation, in multiple locations.
Technology will not When the technology will not meet expectations with the client working
Mitigation

Meet Expectations routinely to mitigate this, the technology specifications must be

commensurate with the client's requirements.

Late delivery time Steps have been taken to ensure timely delivery by measuring project
Mitigation

scope based on the delivery date. So that there is no difference between

delivery time and order completion

End Users Resist End users resist the system in order to prevent this from happening, the
Mitigation

System software will be developed using the end user

Change In Car Rental Requirements In order to prevent this from happening, meetings (formal
Mitigation

Management System and informal) with the client will be held as a routine task. This ensures
Requirements that the product we produce with customers' requirements are equivalent.

5
1.7 HARDWARE AND SOFTWARE RESOURCE REQUIREMENTS
 Database: SQL Server 2014 (SQL14)
 Application: XAAMP, phpMyAdmin
 Client side (minimum requirements):
 Processor: Intel Dual Core
 HDD: At least 80GB disk space
 RAM: 1 GB minimum
 Operating System: Windows 8-11

Design and Implementation Constraints

 The system will use PHP, Ajax, JavaScript, jQuery and CSS as the main web technologies.
 HTTP and FTP are used as communication protocols. FTP is used to load the web
application into the live domain and the client can access it via HTTP protocol.
 Several types of validations make this web application a secure application and SQL entries
can also be prevented.
 Since the car rental system is a web-based application, an internet connection must be
established.
1.8 PROJECT SCHEDULE

Task Name Duration Start Finish

1.1 INITIATION 7. days S 10/16/22 S 10/22/22
1.1.1 Project overview 2 days S 10/16/22 M 10/17/22
1.1.2 Problem Statement. 1 day S 10/16/22 S 10/16/22
1.1.3 project objective 1 day M 10/17/22 T 10/18/22
1.1.4 software process model 1 day T 10/18/22 W 10/19/22
1.1.5 Team organization 1 day W 10/19/22 T 10/20/22
1.1.6 Risk analysis 1 day T 10/20/22 T 10/20/22
1.1.7 Hardware and software resource 2 days T 10/20/22 S 10/23/22
requirements
1.1.8 Project schedule 1 day S 10/23/22 M 10/24/22
1.2 requirements and UML diagrams 5 days S 10/23/22 W 10/26/22
1.2.1 Overall system requirements 1 day S 10/23/22 M 10/24/22
1.2.2 Specific system requirements 1 day T 10/25/22 W 10/26/22
1.2.3 Non-functional requirements 2 days W 10/26/22 T 10/27/22
1.2.4 System UML diagram 1 day T 10/27/22 S 10/30/22
1.3 Design 5 days T 10/27/22 T 11/1/22
1.3.1 context and modes of use of the system 2 days M 10/31/22 T 11/1/22
1.3.1 system architecture design 1 day S 10/30/22 M 10/31/22
1.3.2 principal system architecture 1 day M 10/31/22 T 11/1/22
1.3.3 Design models 3 days T 11/1/22 T 11/3/22
1.4 Prototyping 4 days W 11/2/22 S 11/6/22
1.4.1 prototype for the project 2 days W 11/2/22 T 11/3/22
1.4.2 Teamwork 2 days W 11/2/22 T 11/3/22

6
CHAPTER II

7
2.1 OVERALL SYSTEM REQUIREMENTS
 Car Rental Department: It provides online car booking facility. Customer can visit
the website and check various cars. If possible, with requirements, reservation can be
made.
 Check availability: The employee can check the availability of the vehicle. Maintains
vehicle database. If no vehicle is available, it is the employee's responsibility to
provide alternative options
 Payment system: the administrator / owner of the applications who is responsible for
paying the employee. Cancel the order, the final command, all these activities are
performed by the application administrator.
 Maintenance Manager: If any vehicle requires maintenance such as repairing or
replacing any parts, the data related to that is maintained by the Maintenance Manager.
Maintenance costs are paid by the application manager.
 Customer Registration: New users must be able to register online and print
membership cards.
 Online Car Reservation - Customers must be able to use the system to reserve and
reserve cars online.
 Automatic update of the database as soon as a reservation is made or a new customer is
registered - the system must be. Able to update the database without any extra effort
from the administrator whenever a new reservation or registration is made

2.2 SPECIFIC SYSTEM REQUIREMENTS

This is the data of the services that the system must provide, how the system should
react to certain inputs, and how the system should behave in certain situations.
Specifies the functionality of an application that developers must integrate into the
product to enable users to accomplish their tasks.
 Reservation:
1. The system must allow the customer to register for reservation.
2. The system must allow the customer to view the detailed description of a particular
vehicle.
3. The system should notify when selecting cars that are not available during booking.
4. The system should offer an advanced search option to limit the vehicle search to
certain vehicle search categories.
5. The system should allow customers to select a specific vehicle using a different
search category while booking.
6. The system should display the list of cars available during booking.
7. The system allows customers to cancel the reservation using the reservation
confirmation number.
8. The system allows the employee to update the reservation information.

8
9. The system allows the employee to view the reservations made by customers.
10. The system provides information on protection products and their daily costs, and
asks the customer to accept or reject the organization's conditions during booking.
11. The system must be able to provide a unique reservation formation number for all
reservations that have been successfully committed.
12. The system should be able to display the reservation summary for the reservation
that has been successfully committed
 Log in:
1. The system must allow the administrator to log into the system using the
username and password.
2. The system must allow the employee to log into the system using the username
and password.
3. The system must allow the administrator to create a new user account.
4. The system must allow the administrator to change the account password.
5. The system must allow employees to change the account password.
6. The system should allow employees to log out.
7. The system must allow the administrator to log out.
 Car:
1. The system should allow employees to register new cars.
2. The system should allow employees to choose cars on the list.
3. The system allows the customer to choose cars in the list.
4. The system allows employees to search for cars with a specific record.
5. The system allows the customer's employees to search for cars with a specific
record
6. The system should allow employees to update vehicle information that needs to be
modified.
7. The system allows employees to view all vehicle listings.
8. The system should allow employees to view all available vehicles.
9. The system should allow the customer to view all available cars.
10. The system should allow employees to view all rental cars.
11. The system should allow employees to view all vehicles outside of work hours.

9
  Rent:
1. The system allows employees to register customers in the rental list.
2. The system should allow employees to update the customer's rental history details
in the rental list.
3. The system should be able to save all changes made to the clients' rent list.
4. The system should allow employees to select a client's rental history by the
specified search category.
5. The system should allow employees to search the rental history of customers using
specific categories.
6. The system allows employees to view customers who rent cars.
7. The system should allow employees to view the rental history of all customers.
8. The system must provide a printable summary of the successful committed lease.

2.3 NON-FUNCTIONAL REQUIREMENTS

Non-functional requirements, as the name implies, are requirements that are not directly
related to the specific services that the system provides to its users. It may relate to
emerging system characteristics such as reliability, response time, and store occupancy.
Alternatively, they may specify system implementation limitations such as capabilities of
input/output devices or data representations used in interfaces with other systems. They
typically specify functional requirements, such as performance, security, or availability, or
constrain the characteristics of the system as a whole
Usability:
The system provides a help and support menu in all interfaces for the user to interact with
the system. The user can use the system by reading the help and support.
protection:
The system provides the username and password to prevent the system from unauthorized
access.
Staff password must be greater than eight characters. The subsystem must provide a high
level of security and integrity of the data held by the system, only authorized.
performance:
The system response time for each instruction made by the user must not exceed at least 10
seconds. The system should have a high rate of performance when user input is executed
and should be able to provide a response within a short period of time typically 50 seconds
for the highly complex task and 20 to 25 seconds for the least complex task.

10
 Availability:
The system shall always be accessible 24 hours a day, 7 days a week. Also, in case of any
major malfunction of the system, the system should be available within 1-2 working days,
so that the working process is not severely affected.
Error handling
The error should be reduced to a great extent and an appropriate error message should be
presented that instructs the user to recover from the error. Validating user input is
absolutely essential. The standard time it takes to recover from the error should also be 15-
20 seconds.
Ease of use:
Due to the level of knowledge possessed by the users of this system, a simple but high-
quality user interface should be developed to facilitate understanding and require less
training.
2.4 USE CASE:
Car Rental Management System

Sign in include Account Verification

include Authenticate Password

login

Inquiry forOrder

User Check for availabiliy

Admin

Payment

ReceiptGeneration

MaintenanceChecking

Employee Deliver Car

Cancel Order

11
2.4.1 Use-case description:
A description of the actor and use case provides a detailed description of the interaction
between the actors and their use cases. The description allows for a sound understanding of
how the actor interacts with the system through its use cases
1- User
Actor User
Function Name Register as member
Description This use case describes the activities of the user to register online
and become a member. User details are required as part of
registration. Login details are automatically sent to the user after
successful registration.

Actor User
Function Name Make reservation
Description This use case enables the user to search and make a reservation.
User who are not registered will be directed to register before their
reservation is confirmed. The notification is automatically sent to
the client after the task is completed.

Actor User
Function Name Return car
Description This use case describes the customer's return of the borrowed car,
and the use case extends the "rent process" use case from the staff
representative

Actor User
Function Name Give feedback
Description This use case is used by the user to provide feedback/feedback to
the Company; A confirmation notification will be sent to the user
once feedback has been submitted.

12
 2- Employee
Actor Employee
Function Name Add new car
Description This use case is used by employees to add a new vehicle to the
company's fleet database. Employees will need to be logged in to
activate this use case.

Actor Employee
Function Name Update car details
Description This use case is used by employees to modify and modify vehicle
details whenever there is a new renewal (insurance, road tax). The
company is allowed to keep an up-to-date record of its fleet.

Actor Employee
Function Name Reply customer feedback
Description This use case describes the event by which employees send a
response to previous customer feedback. It depends on the use
case of "Give Feedback" from the customer

Actor Employee
Function Name Process rental
Description This use case described the event by which staff updates the
system when customer pick up or when returning car

3- Admin
Actor Admin
Function Name Add new staff
Description This use case describes the event by which an administrator adds
details of new employees to the company's employee database. It
is called when a new employee joins the company

Actor Admin
Function Name View report
Description This use case is used by the administrator to view the transaction
report

13
CHAPTER III
Design

14
 3.1 THE CONTEXT AND MODES OF USE OF THE SYSTEM

The client (source of information) sends a request.

Then the system sends the invoice data flow.
The staff updates the car records and gives the details to the car rental system.
Car Maintenance Manager gets information about cars from the system, and updates the
renewed records.
The owner checks the order and generates a report.
This is a higher-level view of the flow of information in and out of the system.

3.2 THE SYSTEM ARCHITECTURE DESIGN

15
3.3 THE PRINCIPAL SYSTEM ARCHITECTURE

3.4 DESIGN MODELS

3.4.1 Activity Diagram for placing the order

Activity Diagram for placing the order

plece the order

give altermantives give detailes car

not feasible
feasible

finalize the order

pyment

Recipt Generation

Deliver the Car

Return the car

16
3.4.2 Activity Diagram (Member Registration)
Member Registration

start

enter detail

no

enter username&
password

Accept terms&
Yes
condtion

display customer
confirm &submit
welcom screen

end send emaile

3.4.3 Activity Diagram (Reservation of Car )

choose location

choose date&time

return location

vehicle class availble cars

display Available cars

choose form
available cars

no yes
member

Register login

no
valid

confirm

redirect to payment
send confirmation
gataway

17
3.4.2 SEQUENCE DIAGRAMS

Sequence diagrams are used to illustrate the behavior of objects in a use case by describing
the objects and the messages they convey. It provides a graphical representation of object
interactions over time. Sequence diagrams show the actor and the objects and components
that they interact with in implementing a use case. A single sequence diagram represents
one "scenario" or events for one use case. Sequence diagrams show the flow of messages
from one object to another, and thus correspond to the methods and events that an object
supports.

3.4.2 car rental Management System

Car Rental Management System

Customer Employee Car Record Owner

Inquiry for car

Check for availability

Car available
Give details
Check for feasibilityGive order

Give payment
Receipt generation
Deliver car
Return car

18
[Link] Sequence diagrams Login

LOGIN

Usre homepage login:controller Database

enter login detailes

request login

check authentaction
validate

log in wellcome
return valid

19
[Link] Sequence diagrams Reservation
Reservation

customer

customer homepage check avilable Database

reserve car

request reseve

enter care detailes and select car

send detalies

enter personal detailes

detailes saved
car is reserved

20
21
CHAPTER IV:
Prototyping

22
4.1 PROTOTYPE FOR THE PROJECT
4.1.1Register:
The registration page for the user (customer) appears. The customer must first register as a
user before using this system. The system will ask for user details like full name, email,
username, IC number, phone number and password.

4.1.2 Login
Show the login form to the user. The user must enter the username and password correctly
to use this system.

23
4.1.3 Profile Detail
Shows user profile details. From here the user can update files Name, IC number, phone
number, email and password.

4.1.4 Display Car

This page shows the user the vehicle available in the system.

4.1.5 Car Details:

It displays the details of a particular car and the user needs to enter the start date and end
date for the rental car.

Car rav

Type .Toyota

Star date 5/11/2022

End date 10/11/2022

Total days 5 days

24
4.1.6 Booking Details
Displays the reservation details that the user has booked. Shows all booking details,
payment details and customer details.

4.1.7 Profile Details: Owner

Shows owner profile details. The owner can update his name, phone number and password.

4.1.8 Register New Car

A new vehicle registration page appears. The system will ask for vehicle details such as
vehicle type, price, number of seats and brand.

25
1.6 TEAM ORGANIZATION
2 List of student members’ names, IDs, and roles. Each of the following roles must be assigned to
one student (a student can have multiple roles):

id Name Roles
1 Rafa almutairy Risk analysis& system architecture design

2 Kanood aljmily Hardware and software requirements& principal system architecture&

context and modes of use of the system
4 Shahad almutairy Risk analysis & Design models& context and modes of use of the system

5 Shahad alshamry Risk analysis& system architecture design & Prototype

6 Aisha alanzy Project overview& Overall system requirements& Prototype

7 Randa alharthy Problem Statement& Specific system requirements &Prototype

8 Nora alshamry project objective& Non-functional requirements& Prototype

26
CONCLUSIONS

What has been learned

We learned a lot in implementing this report dedicated to the topic of Software
Engineering, which is how we work in a one-team system and how we can present an
integrated model of a system, in terms of goal formulation, problem analysis, identification
of functional and non-functional requirements and then how to represent system diagrams
using UML drawings. Yes, we have benefited a lot in this software engineering report.
Your own conclusions as a result of working on this project
Expected Result of Development The car rental system has been developed to be able to
solve the user's car rental problem and also help the car rental owner in advertising and
running their car rental business without wasting time. The user needs to contact the owner
to inquire about the availability of car rental and needs to inform and fill out the form
manually to rent a car and it will take a long time and waste time. It also takes management
time to generate the monthly report one by one. Developing this system is just to avoid that
problem. Using Demand Preference by Similarity to Perfect Solution (TOPSIS)
technology, this system allows the user to find the vehicle they provide in the system based
on their preferred criteria and to rent the vehicle easier. The owner also has the advantage
of using this system and saves time and money to advertise their car rental

27
References
1. Waspodo, Bayu, Qurrotul Aini, and Syamsuri Nur. "Development of a car rental
management information system". at the international conference On Information
Systems for Business Competitiveness (ICISBC), pp. 101-105. 2011.
2. Othman, Muhammad Nizam, Noorzaid Muhammad Zain, Dhu al-Faqari Beidi,
Khair Anwar Siddik, Muhammad Najm al-Din Yusuf, and Shaha’a Maghribi. car
online Rental system using web-based SMS technology. Computing Research and
Innovation (CRIN) 2 (2017): 277.

28