Rent a Car SRS

University Name
RENT A CAR
Software Requirements Specification
Version <1.0>
Name1 (Roll No.)
Name2 (Roll No.)
Name3 (Roll No.)

RENT A CAR
Table of Contents
1. Introduction 4
1.1 Purpose 4
1.2 Document Conventions 4
1.3 Intended Audience and Reading Suggestions 4
1.4 Scope 5
1.5 References 5
2. Overall Description 6
2.1 Product Perspective 6
2.2 Product Features 7
2.3 User Classes and Characteristics 7
2.4 Operating Envirnment 7
2.5 Design and Implementation Constraints 7
2.6 User Documentation 8
2.7 Assumptions and Dependencies 8
3 System Features 9
3.1 View Cars List 9
3.1.1 Description and priority 9
3.1.2 Stimulus\ Response sequence 9
3.1.3 Functional Requirements 9
7
3.2 Search Car 9
3.3 Assist in car selection 10
3.4 Book a car 10
3.5 Sign Agreement 11
3.6 Pay Rent 11
3.7 Update Car Lists 12
3.8 Give Points to Customer 13
NUML(Software Engineering) <FYP GROUP>, 2021 Page 2

RENT A CAR
3.9 Save condition of car 13

3.10 Assist in future purchase of car 13
3.11 Assist in future purchase of accessories 14
3.12 View customers record 14
3.13 Notify admin 15
3.14 Login 15
3.15 Create Account 15
3.15 Make Reservation 15
4 Interfaces 10
4.1 User Interfaces 10
4.3 Hardware Interfaces 11
4.3 Software Interfaces 11
4.3 Communicaton interfaces 11
5 Other Non-Functional Requirements 10
4.1 Performance Requirements 11
4.3 Safety Requirements 11
4.3 Security Requirements 11
4.3 Software Quality Attributes 11
6. Other Requirements. 12
Appendix A: Glossary 12
Appendix B: Analysis Models 13
Appendix A: Issue List 15

RENT A CAR
1 Introduction
The introduction of the Software Requirements Specification (SRS) provides an overview of the
entire SRS with purpose, scope, document conventions, intended audience, scope, and references
of the SRS.
1.1 Purpose
The purpose of this document is to present a detailed description of the RENT A CAR. It will
explain the purpose and features of the system, the interfaces of the system, what the system will
do, the constraints under which it must operate and how the system will react to external stimuli.
This document is intended for both the stakeholders and the developers of the system and will be
proposed to the FYP committee for its approval.
1.2 Document Conventions

This document follows IEEE Format. Bold-faced text has been used to emphasize sections and
sub-sections headings. Bold italics highlighting is to point out words in the glossary. This
document features some terminology which readers may be unfamiliar with. See Appendix A
(Glossary) for a list of these terms and their definitions.
1.3 Intended Audience and User Classes

This document is intended for all individuals participating in and/or supervising the project.

 External
 FYP Supervisor Committee
 Developer
 Tester
Readers interested in a brief overview of the product should focus on the rest of Part 1
(Introduction), as well as Part 2 of the document (Overall Description), which provide a brief
overview of each aspect of the project as a whole.
Readers who wish to explore the features of System in more detail should read on to Part 3
(System Features), which expands upon the information laid out in the main overview. Part 4
(External Interface Requirements) offers further technical details, including information on the
user interface as well as the hardware and software platforms on which the application will run.
Readers interested in the non-technical aspects of the project should read Part 5, which covers
performance, safety, security, and various other attributes that will be important to users. Readers
who have not found the information they are looking for should check Part 6 (Other
Requirements) and Appendix which includes any additional information which does not fit
logically into the other sections.

RENT A CAR
1.4 Scope
We will develop a system which will help both owner and customers. The software
system will be a combination of Website and Desktop Application for Car rental service. Both
these desktop and web application will be connected to a central database. Web services will be
used to connect these two with database. This system will be designed to minimize the effort and
time for hiring a car by providing service of online booking and payment. Customer will have
access to the website. Using website customer can view the list of available cars and theirs
features (Model, Mileage, rent etc.). Customer will create account to use the main functionality
(Search car, select car, book car, get assistance for vehicle selection) of the system. Customer
will select the car according to his budget and book this car at the given time by paying rent
online (or select manual payment option) and signing agreement. Customer will have to fill a
form on which he will provide details about him like Name, Mobile No, CNIC, Starting date of
hiring a car and ending date, the place to which he will go. In this way customer has no need to
visit to rental car service providers. Customer will be able to get support from system about
which car to select. System will analyze the data by checking the cars hired by other customers
on this route and will tell the customer that which car is best for him. Whenever a customer will
hire a car system will send notification to the admin panel. Admin will check this notification to
see that which car is hired by which of the customer.
Owner will have control on the system using admin panel. For using admin panel admin
has to login first. Using admin panel owner will manage the cars list which is displayed on
customer panel. He will be able to add, delete or update the car record from the system. System
will also save the record of each customer and owner will check this record at any time. System
will give points to customer at each payment. These points will be subtracted from next payment
in the form of money. This will somehow bound the customer to come again to this service.
Admin will save the condition of car before and after giving on rent. This system will use
machine learning techniques to develop decision support system. Decision support system will
help owner in the future purchases of vehicles and other accessories. System will use algorithm
which will analyze that which cars are used by the customers frequently in the past. After
analyzing the data system will assist owner in next purchase of cars. This system will automate
the currently running manual systems of car rentals.
More specifically, this system will be designed to give a 24 hours service which allow a
customer to have a full view of the available cars and he could book a car with in budget on
given time by online payment instead of visiting to car rental service providers.
The software will facilitate in decision support to the owner which will expand business.
The scope of our system can be seen in Feature Tree (which is a scope representation technique)
in Appendix B.
1.5 References
[1] IEEE Software Engineering Standards Committee, “IEEE Std 830-1998, IEEE
Recommended Practice for Software Requirements Specifications”, October 20, 1998.

RENT A CAR
2 Overall Description
This section will give an overview of the whole system. The system will be explained in its
context to show how the system interacts with other systems and introduce the basic
functionality of it. It will also describe what type of stakeholders that will use the system and
what functionality is available for each type. At last, the constraints and assumptions for the
system will be presented.
2.1 Product Prospective
The Rent a Car Project is a complete product for our customer. It will provide the Owner and
Customer a way of doing all the activities regarding car rental service. It will be a mature version
of currently available systems by providing decision support system and online payment. This
system will consist of two parts: one desktop application (admin panel) and one web portal
(customer panel). This can be seen in Diagram given below.
The website application will be used by customer to find the desired car within budget and book
the car by online payment while the admin panel will be used for managing the information
about the cars and the customers as a whole and for supporting decision for next purchase. Both
desktop and web applications will be connected to a central database. Web services will be used
to fetch or insert data in the database.
2.2 Product Features
Rent a Car system will be a fully automated system which will consists of an admin panel and a
customer panel to facilitate both admin and customer. The major features of the system are:
 Admin and Customer can view cars list.
 Customer will create account.
 Customer can Search a car.
 Customer can Book a car.
 Customer will be able to get help from system in the decision of selecting a car.
 System will give points to customer on every purchase.

RENT A CAR
 Customer Can Pay rent online.
 Customer can sign agreement in terms of any damage to car fuel filling and tool taxes.
 Admin will save the condition of vehicle before giving on rent and after receiving back.
 Admin should Login to use admin panel.
 Admin can update cars record.
 Admin can make reservation using admin panel.
 Admin can see the record of customers.
 System will help the owner in decision of next purchase of vehicles.
 System will help the owner in the decision of purchase of accessories like tires, motor
guards etc.
The major features are shown in USE CASE DIAGRAM in Appendix B.
2.3 User Classes

There are two types of users that interact with the system. Users of the desktop application are
owner or administrators. The users of the web application are customers. Each of these two types
of users has different use of the system so each of them has their own requirements.
The web application users (customers) can only use the website to find a car they want. This
means that the user have to be able to search for cars, choose a car from that search and book that
car through online payment. He will also be able to get assistance for vehicle selection.
Admin will manage all the data of the system. Admin will also be able to get help from system
about future purchase of car and accessories.
The users of our System are Owner and Customer.
 Customer
Customer will book the car after selecting the car and rent payment and can get help
from system about vehicle selection.
 Owner /Admin
Admin will manage the cars list and get decision support from system about future
purchase of vehicles and accessories.
Users Classes are shown in Context Diagram in Appendix B.
2.4 Operating Environment

The two components of the project are the website and a desktop application. The desktop
application will be limited to the Windows operating system (specifically Window 7, Window 8,
Window 8.1 and Window 10). The website and application are not resource or graphics-
intensive, so there are no practical hardware constraints. It will run on any browser like chrome,
Firefox etc. The system will rely on several functionalities built into Windows. Beyond that, the
application is a self-contained unit and will not rely on any other software components.
The application will, however, frequently interact with the Bank/Paypal server. The server
operates on a Windows platform with 1GB of RAM and 10GB of allocated storage space. The
System database will be stored on the server using MySQL/SQL
.

RENT A CAR
2.5 Design and Implementation Constraints
The primary design constraint for admin panel is the Desktop platform. Since the customer panel
is designated as website, screen size and resolution will be a major design consideration.
Creating a user interface which is both effective and easily navigable will pose a difficult
challenge. Other constraints such as limited memory and processing power are also worth
considering. Rent a Car is meant to be quick and responsive, even when dealing with large
number of queries. Coding should be done using ASP.NET, C#. So system must be designed and
implemented with efficiency in mind.
 The project should be completed within specified time period including Planning,
Designing, Development, Testing and Deployment.
 The project should be completed within specified budget.
 All the Entry and Exit criteria of all the stages should be met.
 The product should be user-friendly, reliable and should maintain the industry
standards without compromising the quality.
 The system architecture and design should be open and in a standard way such that
additional functionalities can be added later without much effort.
 Hard drive space:
TAG: Hard DriveSpace
GIST: Hard drive space.
SCALE: The application’s need of hard drive space.
METER: MB.
MUST: No more than 30 MB.
PLAN: No more than 20 MB.
WISH: No more than 15 MB
MB: DEFINED: Megabyte
2.6 User Documentation

The user documentation can be found in this SRS.
2.7 Assumptions and Dependencies

We assume that extra documentation beyond this SRS would not be necessary in order for the
user to utilize this product. One assumption about the product is that it will always be used with
internet connection.

RENT A CAR
Our system must be able to communicate with PayPal system for payment.
The following technologies have been identified as technical constraints. The system must
be compatible with:
 Windows Server 2000
 MS IIS 5.0
 MS SQL Server 2000/MYSQL
The system is to be developed as a combination of desktop app and a website using
ASP.NET and C#.
3 System Features
3.1 View Cars
3.1.1 Description and Priority
Rent a car system will allow admin and customer to view cars list. It will have details of all
the cars which are available for rent.
Priority = Very High
3.1.2 Stimulus/Response Sequences
ID EVENT SYSTEM RESPONSE
1 Customer will open website. System will display
Or Admin will open desktop front/home page of website
application. and desktop application.
2 Customer will navigate to System will show all the
available cars page. available cars to customer.
3.1.3 Functional Requirements

o system shall be able to display all the available cars on the website.
o Customer The could be able to check all the available cars on website.
3.2 Search a car.

Rent a car system will allow a customer to search for his desired car whether it is available
or not.
Priority = High
1 Customer will open the System will show front page
website. of website.
2 Customer will go to search bar System will check the car
and enter the name to search. name which customer has
entered from database and

RENT A CAR
show the car details if it is
available.

o Customer will be able to search for a car.
o System should display the desired car of customer.
3.3 Assist for vehicle selection.

Rent a car system will allow a customer to get assistance from the system about car
selection. System will perform an analysis on the past data and will tell the customer that
which cars are hired by others customers on that route on which he is going.
Priority = High
1 Customer will open the System will show front page
website. of website.
2 Customer will click on get System will perform an
assistance button. analysis on the past data and
will tell the customer that
which cars are hired by others
customers on that route (hilly
area or plan area) on which he
is going.

o Customer will be able to get help from system for deciding which car to select.
o System will help the customers in taking decision of which car to hire by performing an
analysis on the past data and will tell the customer that which cars are hired by others
customers on that route (hilly area or plan area) on which he is going.
3.4 Book a car.

System will allow a customer to book a car at given time.
Priority = High.
1 Customer will select the System will show option of
desired car. booking.
2 Customer will click on book System will show a form to
option. fill.

RENT A CAR
3 Customer will fill the form System will show agreement
and terms and conditions to
accept.

o Customer will select the desired car.
o Customer will book the car online and system will reserve this car for customer after the
customer has signed the agreement and has accepted all the terms and conditions.
3.5 Sign agreement/Accept terms and conditions

Customer will sign agreement in terms of any damage to car and accept the terms and
conditions like fuel filling, toll taxes etc. before reserving a car.
Priority = High.

option. fill.
Customer will fill the form System will show agreement
accept.
3 Customer will accept all terms System will show payment
and conditions and sign option customer has signed the
agreement. agreement.
.
o The system shall be able to sign an agreement (in case of any damage to car during the
period of his hiring a car, fuel filling and tool taxes) by customer before reserving a car.
3.6 Pay rent.

Rent a car system will be able to allow customers to pay rent online using PayPal platform.
Priority = High.

RENT A CAR
option. fill.
Customer will fill the form System will show agreement
accept.
3 Customer will sign agreement. System will show other terms
and conditions.
4 Customer will accept terms System will show payment
and conditions option
5 Customer will pay rent using System will confirm the
PayPal payment and reserve that car
for customer and hide this car
form website.

o The system shall able to receive rent payment online using PayPal.
3.7 Manage cars

Rent a car system will allow admin to add or delete a car from customer panel using
desktop application.
Priority =High.
1 Admin will select manage cars System will show add or
button in admin panel delete car options.
2 Customer will select add or If customer will select delete
delete or update car info car option system will take id
option. of car from admin delete that
car from central database
which automatically delete
this from admin panel.
If customer will select add a
new car option system will ask
admin to enter to details of
car.
3 Admin will enter details of car System will add this car to the
central database and it will be
displayed on customer panel.
o The system shall allow admin to add a new car or delete an existing car.

RENT A CAR
3.8 Give points to customer

Rent a Car system will give points to customer at every purchase and these will be added in
next payment.
Priority = High.
1 Customer will Pay rent System will reserve that car
for customer and give points
to customer and save them in
database.
3.8.3 Functional Requirement
o The system shall be able to give points to customer at every purchase and these points
will added as money in the next purchase.
3.9 Save condition of car

Rent a Car system will help admin to save the condition of car (damaged, dent etc.) before
and after giving on rent.
Priority = High.
1 Admin will save the condition System will save these states
of car before and after giving in the database.
on rent. He will enter the
name of damaged parts.

o The system will allow admin to save the conditions of cars before and after giving on rent
whether cars or damage, have dent, or in good condition.
3.10 Assist in future purchase of cars

Rent a Car system will assist admin in future purchase by analyzing the saved data. System

RENT A CAR
will perform analysis on the data to check that which cars are hired by the customers
mostly and predict for future.
Priority = High.
1 Admin will ask system for System will perform analysis
predict future purchase of cars on the saved data and will
or accessories. check which cars are hired by
customers most of the times
and will predict for future
purchase of cars.

o The system shall be able to assist admin in future purchase. System will do this by
performing analysis on the saved data by checking that which cars are hired by the
customers more frequently.
3.11 Assist in future purchase of other accessories
Rent a Car system will assist admin in future purchase by analyzing the saved data. System
will perform analysis on the data and predict for future.
Priority = High.
1 Admin will ask system for System will perform analysis
predict future purchase of cars on the saved data and will
or accessories. check conditions of cars
before and after going to a
route and will check the names
of damaged parts of car and
will predict for future purchase
of accessories.

o The system shall be able to assist admin in future purchase. System will do this by
performing analysis on the saved data by checking that which cars are hired by the
customers more frequently.
3.12 View Customer list or record

Rent a Car system will help admin to have a look at customer record.

RENT A CAR
Priority = High.
1 Admin will check the System will show the details
customer record at any time of each customer to the admin.
by clicking on view customer
record button.

o The system shall be able to show the details of customers to the admin whenever he
wants.
3.13 Notify Admin

Rent a Car system will send notification to the admin panel when a customer will book
a car.
Priority = High.
1 Customer will book a car after System will send notification
payment and signing to the admin panel that a car
agreements. has been reserved.

o The system shall be able to notify admin whenever a customer has booked a car using
customer panel.
3.14 Login
Admin has to login to the admin panel for performing admin activities.
Priority = High.
1 Admin will enter name and System will check the
password for login. validation and if valid system

RENT A CAR
will show admin panel to the
admin.

o The system shall be able to authenticate admin through login before using admin
panel functionalities.
3.15 Create Account

Customer has to create an account for using specific activities of the web
panel like search car, book car, get assistance for vehicle selection. Without creating
account customer can only see list of cars available for booking.
Priority = High.

1 Customer will open website System will show create
account option.
2 Customer will select create System will show a form to
account option. fill for creating account.
3 Customer will fill form and System will save his data in
press ok button. the database and create an
account with his name. System
will show specific
functionalities of the system to
the customer after creating his
account.

o The customer will create an account for using specific functionalities of the system for
customer.
o System will not show specific functionalities like select car, book car, get assistance for
vehicle selection until customer will not create account.

RENT A CAR
3.15 Make Reservation
System will allow an admin to make reservation through desktop application when a
customer comes to his office for hiring a car.
Priority = High
1 Admin will open desktop System will show a form on
application and select 'make which customer details and car
reservation' option. name to fill.
2 Admin will fill form and System will save this car with
confirm reservation. customer name in reservation
table and hide that car from
customer panel.

o The admin will be able to make reservation using desktop application when a customer
comes to his office for hiring a car.
o System will allow an admin to make reservation using desktop application.
4 Interfaces
This section provides a detailed description of all inputs into and outputs from the system. It
also gives a description of the hardware, software and communication interfaces and
provides basic prototypes of the user interface.

RENT A CAR
4.1 User Interfaces
The home screens of both admin and customer's panels offer a menu with a list of functions
that the system performs.
The user can select one of the options. The user can click on any one of the options and is
taken to the screen of their choice. In customer panel home screen option of create account
is also available.
When customer will create account he will be able to use the specific functionalities of the
system like booking, getting assistance etc.
Admin has to login for using admin panel. He has to enter user name and password for
authentication.

RENT A CAR
Customer can view cars and book that car after filling form, signing agreement and paying
rent.
In payment option user have to select whether he wants to pay online or will pay manually at
the time of receiving car.
The system offers easy navigate options. To scroll
Screen contains a text field to enter search terms.

RENT A CAR
4.2 Hardware Interface
Since neither the desktop application nor the web portal have any designated hardware, it
does not have any direct hardware interfaces. Hardware connection to the database server
is managed by the underlying operating system on the computer and the web server.
4.3 Software Interfaces
The web application communicates with the PayPal server for rent payment and its
verification. The communication between the database and the web portal (Customer
Panel) consists of operations concerning both reading and writing the data, while the
communication between the database and the desktop application (Admin Panel) also
consists of both reading and modifying operations. Web services will be used to connect
both admin panel and customer panel to a central database.
Communication Interfaces
System will communicate with PayPal for payment of rent.
5 Other non-functional Requirements

5.1 Performance Requirements
Performance should not be an issue because all of our server queries involve small pieces of
data. Changing screens will require very little computation and thus will occur very quickly. The
system will make use of web services to retrieve data from server to avoid repetitive trips (call
between GUI and Database). Server updates should only take a few seconds. The system shall
free up resources immediately after use for efficient use of memory.
 Response time
TAG: Response Time
GIST: The fastness of the search
SCALE: The response time of a search
METER: Measurements obtained from 1000 searches during testing.
MUST: No more than 2 seconds 100% of the time.
WISH: No more than 1 second 100% of the time.
5.2 Safety Requirements
System will not affect data stored outside of its servers nor will it affect any other applications
installed on the user’s PC. It cannot cause any damage to the computer or its internal
components.
5.3 Security Requirements
Since login is required for admin to perform administrative actions like manage cars, view
customers record, get assistance for future purchase and make reservation there is no need to
worry about security of admin panel because without authentication no one can use admin panel
(desktop application).
For customer creating an account is necessary for booking a car and to get help from system for
vehicle selection. The system is divided into two panels which will be used separately by admin
and customer. The system shall permit customers to view only their own previously placed
orders, not orders placed by other customers.

RENT A CAR
5.4 Quality Attributes
Usability:
The system shall use icons and menu bars. The graphical user interface of RAC is to
be designed with usability as the first priority. The website (Customer panel) will be presented
and organized in a manner that is both visually appealing and easy for the user to navigate. The
admin panel will be simply designed so that the admin doesn't find any difficulty to perform
tasks. There will be feedbacks and visual cues
Availability:
The RAC shall be available to users 99.9% of the day.
Interoperability:
RAC System will be able to communicate with PayPal for payment of rent. It will have ability to
connect with PayPal system.
6 Other Requirements
Correctness:
To ensure reliability and correctness, there will be zero tolerance for errors.

RENT A CAR
Appendix A: Glossary
SRS Software requirements specifications
PayPal Online Payment platform.
RAC RENT A CAR (Our Proposed System)
IEEE Institute of electrical and electronics engineering
Feature Tree Feature Tree is a scope representation technique
Context Diagram Zero level Dataflow diagram which gives the high level detail of system
USE CASE DIAGRAM This Diagram is used to how entities interact with
System.
Appendix C: Issue List

There are no issues regarding Rent a Car System.

RENT A CAR
Appendix B: Analysis Models
Context Diagram

RENT A CAR
Feature Tree

RENT A CAR
Use Case Diagram.

Rent a Car SRS

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Rent a Car SRS

Uploaded by

Copyright:

Available Formats

University Name

Name1 (Roll No.)

Name2 (Roll No.)

Name3 (Roll No.)

NUML(Software Engineering) <FYP GROUP>, 2021 Page 2

3.9 Save condition of car 13

NUML(Software Engineering) <FYP GROUP>, 2021 Page 3

1.2 Document Conventions

1.3 Intended Audience and User Classes

NUML(Software Engineering) <FYP GROUP>, 2021 Page 4

NUML(Software Engineering) <FYP GROUP>, 2021 Page 5

 System will give points to customer on every purchase.

NUML(Software Engineering) <FYP GROUP>, 2021 Page 6

The major features are shown in USE CASE DIAGRAM in Appendix B.

2.3 User Classes

2.4 Operating Environment

NUML(Software Engineering) <FYP GROUP>, 2021 Page 7

2.6 User Documentation

2.7 Assumptions and Dependencies

NUML(Software Engineering) <FYP GROUP>, 2021 Page 8

3.1.3 Functional Requirements

3.2 Search a car.

NUML(Software Engineering) <FYP GROUP>, 2021 Page 9

3.2.3 Functional Requirements

3.3 Assist for vehicle selection.

3.3.3 Functional Requirements

3.4 Book a car.

NUML(Software Engineering) <FYP GROUP>, 2021 Page 10

3.4.3 Functional Requirements

3.5 Sign agreement/Accept terms and conditions

3.5.2 Stimulus/Response Sequences

3.6 Pay rent.

NUML(Software Engineering) <FYP GROUP>, 2021 Page 11

3.6.3 Functional Requirements

3.7 Manage cars

NUML(Software Engineering) <FYP GROUP>, 2021 Page 12

3.8 Give points to customer

3.9 Save condition of car

3.9.3 Functional Requirements

3.10 Assist in future purchase of cars

NUML(Software Engineering) <FYP GROUP>, 2021 Page 13

3.10.3 Functional Requirements

3.11.3 Functional Requirements

3.12 View Customer list or record

NUML(Software Engineering) <FYP GROUP>, 2021 Page 14

3.12.3 Functional Requirement

3.13 Notify Admin

3.13.3 Functional Requirement

NUML(Software Engineering) <FYP GROUP>, 2021 Page 15

3.14.3 Functional Requirement

3.15 Create Account

3.15.2 Stimulus/Response Sequences

3.15.3 Functional Requirement

NUML(Software Engineering) <FYP GROUP>, 2021 Page 16

3.16.3 Functional Requirement

NUML(Software Engineering) <FYP GROUP>, 2021 Page 17

NUML(Software Engineering) <FYP GROUP>, 2021 Page 18

NUML(Software Engineering) <FYP GROUP>, 2021 Page 19

5 Other non-functional Requirements

NUML(Software Engineering) <FYP GROUP>, 2021 Page 20

5.4 Quality Attributes

The RAC shall be available to users 99.9% of the day.

NUML(Software Engineering) <FYP GROUP>, 2021 Page 21