Software Requirements

Specification
for

<Car Rental Management

System>

Prepared by <Muhammad Bilal Mubarak (SP20-BSE-024), Muhammad Hassan

Niaz (SP20-BSE-017), Haseeb Amjad Kashmiri (SP20-BSE-005), Raees-Ud-Din
(SP20-BSE-033)>

Version 1.0 approved

< Comsats University, Wah campus >

<19 April 2021 >

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii

Contents
Prepared by <Muhammad Bilal Mubarak (SP20-BSE-024), Muhammad Hassan Niaz (SP20-BSE-
017), Haseeb Amjad Kashmiri (SP20-BSE-005), Raees-Ud-Din (SP20-BSE-033)>...............................i
1. Introduction..............................................................................................................................1
1.1 Purpose:......................................................................................................................................1
1.2 Product Scope:............................................................................................................................1
1.3 Document Conventions..............................................................................................................1
1.4 Intended Audience and Reading Suggestions.............................................................................2
1.5 References:.................................................................................................................................2
2. Overall Description..................................................................................................................2
2.1 Product Perspective:...................................................................................................................2
2.1.1 1: Existing system function:...................................................................................................2
2.2 Product Functions:......................................................................................................................3
2.2.1 Car Rental Management:........................................................................................................3
2.2.2 Checking For Availability:.....................................................................................................3
2.2.3 Payment system:....................................................................................................................3
2.2.4 Maintenance Manager:...........................................................................................................3
2.3 User Classes and Characteristics:...............................................................................................3
2.4 Operating Environment:.............................................................................................................3
2.5 Design and Implementation Constraints:....................................................................................3
2.6 User Documentation:..................................................................................................................4
2.7 Assumptions and Dependencies:................................................................................................4
2.7.1 Regularity Policies:................................................................................................................4
2.7.2 Hardware Limitations:............................................................................................................4
3. External Interface Requirements...........................................................................................4
3.1 User Interfaces:...........................................................................................................................4
3.2 Hardware Interfaces:...................................................................................................................4
3.3 Communications Interfaces:.......................................................................................................5
3.4 System Features:........................................................................................................................5
3.5 System Feature 1........................................................................................................................5
3.5.1 Description and Priority.........................................................................................................5
3.5.2 Stimulus/Response Sequences...............................................................................................5
3.5.3 Functional Requirements.......................................................................................................5
3.6 System Feature 2 (and so on).....................................................................................................6
4. Other Nonfunctional Requirements.......................................................................................6
4.1 Performance Requirements:........................................................................................................6
4.2 Safety Requirements...................................................................................................................6
4.3 Security Requirements:..............................................................................................................6
4.4 Business Rules:..........................................................................................................................6
4.5 Software Quality Attributes........................................................................................................6
4.5.1 Adaptability:..........................................................................................................................6
4.5.2 Availability:...........................................................................................................................7
4.5.3 Correctness:............................................................................................................................7
4.5.4 Flexibility:..............................................................................................................................7
4.5.5 Testability:.............................................................................................................................7
4.6 Other Requirements....................................................................................................................7
5. Cases:........................................................................................................................................7
5.1 Activity Diagram:.......................................................................................................................8
5.1.1 Member Registration:.............................................................................................................8
................................................................9
5.1.2 Profile Modification:..............................................................................................................9
5.1.3 Customer Feedback:.............................................................................................................10
5.1.4 Use case diagram:................................................................................................................10
Software Requirements Specification for <Project> Page iii

6. Appendix A: Glossary...........................................................................................................11
6.1 Appendix B: Analysis Models..................................................................................................11
6.2 Appendix C: To Be Determined List........................................................................................12

Revision History
Name Date Reason For Changes Version
None None None 1.0
None None None 1.0
Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose:
The advancement in Information Technology and internet penetration has greatly enhanced
various business processes and communication between companies (services provider) and
their customers of which car rental industry is not left out. This E-Car Rental System is
developed to provide the following services:
 Enhance Business Processes: To be able to use internet technology to project the rental
company to the global world instead of limiting their services to their local domain alone,
thus increase their return on investment (ROI).
 Online Vehicle Reservation: A tools through which customers can reserve available cars
online prior to their expected pick-up date or time.
 Customer’s registration: A registration portal to hold customer’s details, monitor their
transaction and used same to offer better and improve services to them.
 Group bookings: Allows the customer to book space for a group in the case of weddings
or corporate meetings (Event management).

1.2 Product Scope:

This project traverses a lot of areas ranging from business concept to computing field, and
required to perform several researches to be able to achieve the project objectives. The area
covers include:
 Car rental industry: This includes study on how the car rental business is being done,
process involved and opportunity that exist for improvement.
 PHP Technology used for the development of the application.
 General customers as well as the company’s staff will be able to use the system
effectively.
 Web-platform means that the system will be available for access 24/7 except when there is
a temporary server issue which is expected to be minimal.

1.3 Document Conventions.

In this complete document, we will mention priority as “low”
or “high” throughout the document. Secondly, priorities are only mentioned in section 4 and section
5 along with detailed description of the requirements. Throughout this document, all the user
entities are written in capitalizations i.e. first letter as capital. Also, any significant term which has
been described in the glossary is made bold and italic in the text. Intended Audience and Reading
Suggestions
Software Requirements Specification for <Project> Page 2

1.4 Intended Audience and Reading Suggestions.

The purpose of this document is to give a
detailed description of the requirements for the car rental management system software. It will
illustrate the purpose, scope and complete description for the development of system. It will also
explain external interface requirements and system requirements as well as non-functional
requirements. This document is primarily intended to be proposed to a customer for its approval
and also for further processing such as additions to be developed in later releases.

1.5 References:
 http://www.carrentingsolutions.com/
 http://www.flashvortex.com/
 http://www.imscart.com/car_rental_software.html
 Wikipedia.org

2. Overall Description

2.1 Product Perspective:

2.1.1 1: Existing system function:

A car rental is a vehicle that can be used temporarily for a period of time with a fee. Renting
a car assists people to get around even when they do not have access to their own personal
vehicle or don't own a vehicle at all. The individual who want to rent a car must first contact
the car rental company for the desire vehicle. This can be done online. At this point, this
person has to supply some information such as; dates of rental, and type of car. After these
details are worked out, the individual renting the car must present a valid Identification
Card.
Car Rental System gives car rental service for both foreign and local customers. This
organization carries out its daily work by providing; their service to the customers using
manually system. The organization uses a manual system for reserving, renting, register and
to keep record of all the rental activities and customer information. The detailed existing
system functions are listed as follows –
 During car reservation the customers reserve a vehicle by making a phone call to the
organization; otherwise he/she is expected to go to the organization to make reservation.
 During renting a car the customer personal information, payments status and rent
agreements are filled in the car rent agreement form in order to hold legal contract between
the customer and organization for renting the vehicle.
 The organization normal work time schedule is from 1:30am – 6:00pm; therefore the
organization gives services for ten and half hours a day.
 The organization makes a general report about the rented cars once at the end of the
month and generates a report.
Software Requirements Specification for <Project> Page 3

2.2 Product Functions:

Car Rental System provides the features for booking a car online. It includes several
functionalities describes as below:
2.2.1 Car Rental Management:

It provides car reservation facility online. Customer can visit the website and check for
various cars. If they are feasible with requirement, then booking can be done.
2.2.2 Checking For Availability:

Employee can check for the availability of the car. He/she maintains the database of car. If
no any car is available it is the responsibility of the employee to provide alternative options.
2.2.3 Payment system:
Administrator/owner of the applications responsible for payment to the employee. Order
cancellation, order finalize, these all activities are done by the administrator of the
application.
2.2.4 Maintenance Manager:

If any car requires maintain ace like repair or replacement of any parts, then maintenance
manager maintain the data about that. Payment of maintenance are done by the
administrator of the application.

2.3 User Classes and Characteristics:

Customer’s registration:
The system should allow new users to register online and generate membership card.
b. Online reservation of cars: Customers should be able to use the system to make booking
and online reservation.
c. Automatic update to database once reservation is made or new customer registered:
Whenever there’s new reservation or new registration, the system should be able update the
database without any additional efforts from the admin.

2.4 Operating Environment:

Since Car Rental system is a web-based application, internet connection must be
established.

2.5 Design and Implementation Constraints:

 The application will use php, Ajax, JavaScript, iquery and css as main web technologies.
 HTTP and FTP protocols are used as communication protocols. FTP is used to upload the
web application in live domain and the client can access it via HTTP protocol.
 Several types of validations make this web application a secured one and SQL Injections
can also be prevented.
Software Requirements Specification for <Project> Page 4

 Since Car Rental system is a web-based application, internet connection must be

established.
 The Car Rental System will be used on PCs and will function via internet or intranet in
any web browser.

2.6 User Documentation:

There will be no user manuals, online helps or tutorials as it is made as simple as web
beginners can also use it easily with best web GUI functionality.

2.7 Assumptions and Dependencies:

2.7.1 Regularity Policies:

Each center user has account created and authenticated by admin. This Website can be
accessible within company’s intranet and other user can see the all details about the
franchisee. Each user has to first login itself to present him/her after entry in franchisee.
This will be done automatically.no user can share their username and password to each
other.
2.7.2 Hardware Limitations:

There is no limitation in the operating system in which Car Rental System will work.
However, the Car Rental System and the database will work on a server that needs to be
always online. Users can access the system with any internet browser.

3. External Interface Requirements

3.1 User Interfaces:

 All the users will see the same page when they enter in this website. This page asks the
users a username and a password.
 After being authenticated by correct username and password, user will be redirect to their
corresponding profile where they can do various activities.
 The user interface will be simple and consistence, using terminology commonly
understood by intended users of the system. The system will have simple interface,
consistence with standard interface, to eliminate need for user training of infrequent users.

3.2 Hardware Interfaces:

 No extra hardware interfaces are needed.
 The system will use the standard hardware and data communication resources.
 This includes, but not limited to, general network connection at the server/hosting site,
network server and network management tools.
Software Requirements Specification for <Project> Page 5

3.3 Communications Interfaces:

 This system use communication resources which includes but not limited to, HTTP
protocol for communication with the web browser and web server and TCP/IP network
protocol with HTTP protocol.
 This application will communicate with the database that holds all the booking
information. Users can contact with server side through HTTP protocol by means of a
function that is called HTTP Service. This function allows the application to use the data
retrieved by server to fulfill the request fired by the user.

3.4 System Features:

 This online car rental solution is fully functional and flexible.
 It is very easy to use.
 This online car rental system helps in back office administration by streamlining and
standardizing the procedures.
 It saves a lot of time, money and labour.
 Eco-friendly: The monitoring of the vehicle activity and the overall business becomes easy
and includes the least of paper work.
 The software acts as an office that is open 24/7.
 It increases the efficiency of the management at offering quality services to the customers.
 It provides custom features development and support with the software.

3.5 System Feature 1

<Don’t really say “System Feature 1.” State the feature name in just a few words.>
3.5.1 Description and Priority
<Provide a short description of the feature and indicate whether it is of High,
Medium, or Low priority. You could also include specific priority component
ratings, such as benefit, penalty, cost, and risk (each rated on a relative scale
from a low of 1 to a high of 9).>
3.5.2 Stimulus/Response Sequences
<List the sequences of user actions and system responses that stimulate the
behavior defined for this feature. These will correspond to the dialog elements
associated with use cases.>
3.5.3 Functional Requirements
<Itemize the detailed functional requirements associated with this feature.
These are the software capabilities that must be present in order for the user to
carry out the services provided by the feature, or to execute the use case.
Include how the product should respond to anticipated error conditions or
invalid inputs. Requirements should be concise, complete, unambiguous,
verifiable, and necessary. Use “TBD” as a placeholder to indicate when
necessary information is not yet available.>
<Each requirement should be uniquely identified with a sequence number or a
meaningful tag of some kind.>
Software Requirements Specification for <Project> Page 6

REQ-1:
REQ-2:

3.6 System Feature 2 (and so on)

4. Other Nonfunctional Requirements

4.1 Performance Requirements:

The system response time for every instruction conducted by the user must not exceed more
than a minimum of 10 seconds. The system should have high performance rate when
executing user’s input and should be able to provide response within a short time span
usually 50 second for highly complicated task and 20 to 25 seconds for less complicated
task.

4.2 Safety Requirements

The software is completely environmentally friendly and does not cause any safety violations. The
menu will have a flexible font that can be zoomed so as to not over constrain the eyes.

4.3 Security Requirements:

The system provides username and password to prevent the system from unauthorized
access. The staffs’ password must be greater than eight characters. The subsystem should
provide a high level of security and integrity of the data held by the system, only authorized
personnel of the company can gain access to the company’s secured page on the system; and
only users with valid password and username can login to view user’s page.

4.4 Business Rules:

1: The system should always be available for access at 24 hours, 7 days a week. Also in the
occurrence of any major system malfunctioning, the system should be available in 1 to 2
working days, so that business process is not severely affected.
2: Each and every individual who need to book a vehicle they will get completely examine
and they need to give there Cnic and driving permit duplicate.

4.5 Software Quality Attributes

4.5.1 Adaptability:

There can be a change in the menu and information stored in the database about employees and
inventory.
Software Requirements Specification for <Project> Page 7

4.5.2 Availability:

The system is up and running for most of the time and server is not down for more than a few
minutes to avoid inconvenience of the customers.

4.5.3 Correctness:

The bill generated by the application must be accurate and the orders placed should exactly be the
same which the user has selected.

4.5.4 Flexibility:

If need arises in the future, software can be modified to change the requirements.

4.5.5 Testability:

All the requirements are fulfilled, response time is low, and all functions are working perfectly.

4.6 Other Requirements

<Define any other requirements not covered elsewhere in the SRS. This might include
database requirements, internationalization requirements, legal requirements, reuse
objectives for the project, and so on. Add any new sections that are pertinent to the
project.>

5. Cases:
Actor and use case description show the detail description of interaction
between the actors and their use cases. The description enables to have a proper
understanding of how actor interacts with the system through their use cases.

Actor Use Case Use Case Description

This use case describes the activities of the customer

to register online and become a member. Customer's
Register as
details are required as part of the registration. Login
member
detail is automatically sent to the customer after
successful registration.
Software Requirements Specification for <Project> Page 8

This use case enable customer to search and make

reservation. Non-register customer will be directed
Make
to register before their reservation can be
reservation
Customer confirmed. Notification is automatically sent to the
customer after the task is completed.
This use case describes the event of customer
returning the car borrowed, the use case extends
Return car
"process rental" use case from the staff actor.
Give feedback This use case is used by the customer to provide
feedbacks/comment to the company; a
confirmation notification will be send to the
customer once a feedback has been submitted.
This use case is used by the staff to add new car to
the company's fleet database. Staff will need to login
Add new car
to activate this use case.
Staff Update car This use case is used by the staff to edit and modify
details car details whenever there is new renewal
(insurance, road tax). It allows the company to keep
up-to-date record of their fleet.
Reply to This use case describes the event by which staff
customer’s sends reply to customer's earlier feedback. It
feedback depends on `give feedback' use case from the

5.1 Activity Diagram:

5.1.1 Member Registration:

Software Requirements Specification for <Project> Page 9

5.1.2 Profile Modification:

Software Requirements Specification for <Project> Page 10

Customer E-Car Rental System

Start

[No]

Login Valid?

Navigate to Edit [Yes]

Profile

Modify your profile

Confirm and submit

Update database

Send confirmation
notification

Log out

End

5.1.3 Customer Feedback:

Customer E-Car Rental System

Start

Enter your details

Enter your message/remark

Submit feedback

Send notification

End
Software Requirements Specification for <Project> Page 11

5.1.4 Use case diagram:

Software Requirements Specification for <Project> Page 12

6. Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the
entire organization, and just include terms specific to a single project in each SRS.>

6.1 Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class
diagrams, state-transition diagrams, or entity-relationship diagrams.>

6.2 Appendix C: To Be Determined List

<Collect a numbered list of the TBD (to be determined) references that remain in the SRS
so they cans be tracked to closure.>