Software Requirements

Specifications

Car Rental System (CRS)

Version 1.0

Date: 4/12/2018

Released by: Bright Innovations

Document Control
Document Name CRS Software Requirement Specifications
Reference Number CRS_SRS
Version 1.0
Project Code CRS_V1
Status Under development
Date Released 30/11/2018

Name Position Signature

Prepared by: Senior Analyst
William Kang Wei Liang
Prepared by: Lead Developer
Kevin
Reviewed by: Human Resource Manager
Khor Zi Heng Byron
Approved by: Project Manager
Foong Ee Fong
Version History
Version Release Date Section Amendments
1.0 30/11/2018 All None; original
document
Table of Contents
Document Control ..................................................................................................................................... 2
Version History ......................................................................................................................................... 3
1.0 Introduction .................................................................................................................................... 5
1.1 Purpose ....................................................................................................................................... 5
1.2 Scope .......................................................................................................................................... 5
1.3 Definitions and Acronyms .......................................................................................................... 5
1.4 References .................................................................................................................................. 5
1.5 Overview .................................................................................................................................... 5
2.0 Overall Description ........................................................................................................................ 6
2.1 Product Perspective .................................................................................................................... 6
2.2 Product Features ......................................................................................................................... 6
2.3 User Characteristics:................................................................................................................... 7
3.0 Specific Requirements ................................................................................................................... 8
3.1 Functional Requirements ............................................................................................................ 8
3.2 Performance Requirements .......................................................................................................11
3.3 General Constraints ...................................................................................................................11
3.4 Software System Attributes .......................................................................................................11
3.4.1 Accuracy..................................................................................................................................11
3.4.2 Security .................................................................................................................................. 12
3.4.3 Usability ................................................................................................................................. 12
1.0 Introduction

1.1 Purpose

The purpose of this document is to specify the details of the software requirements elicited by Bright
Innovation from Rent Now company. It addresses the functionality, performance, interface, quality
attributes, and compliance requirements of the Car Rental System (CRS).

This document is intended for the perusal of the system developer, project manager, configuration
manager and client.

1.2 Scope

The system is divided into two subparts according to the users of the system:

Customer subsystem – System consist of all the functionalities related to customers.

Business subsystem – System consist of all the functionalities related to business end. (Company staff)

This document covers entire system and all its subparts. The functionalities of the system are also
clearly divided into the above-mentioned subparts and explained in simple and understandable way.

1.3 Definitions and Acronyms

Definitions

Customer The person who wants to rent a car.

System Admin Car renting company staff member who is in
charge of the system.

Acronyms

Acronym Full Name

SRS Software Requirement Specifications
CRS Car Rental System

1.4 References

This document is prepared with reference to the following documents:

i. "Tutorialspoint," [Online]. Available: http://tutorialspoint.com.

ii. IEEE Std 830-1998. Recommended Practice for Software Requirement Specifications

1.5 Overview
This document shall consist of 3 sections:
Section 1: Introduction – contains the purpose, scope, definitions, acronyms, and references made.
Section 2: Overall Description – a high-level overview of the system.
Section 3: Specific Requirements – the requirements that are to be implemented in the CRS.

2.0 Overall Description

This purpose of this section is to give details about what user can expect from CRS. This will provide
an overview of requirements gathered.

2.1 Product Perspective

CRMS will automate the manual car reservation process which was carried out by going to the business
place or using a phone call.

The new system will consist of two sub systems. The customer subsystem will handle all the
functionalities related to customers. The business subsystem will handle all the functionalities related
to the car renting company.
The new system will be able to undergo evolution in a much simpler way and will be more adaptable to
the changing systems. The upcoming changes in the near future will be predicted and the system will
be designed in a way to adapt to the changes that will occur over the years.

2.2 Product Features

Feature ID Feature Description Accessible Role

F001 Account Management Allow user to manage User
their account.
F002 Book vehicle To reserve vehicle and User
related functions
F003 Feedback Allow user to provide User
feedback of the system
F004 Edit the web content To edit the layout of the Admin
system content
F005 View booking Allow admin to view Admin
the list of booked cars
 F006 View vehicle Allow the users to view User
and book available cars
F007 Add vehicle Add new vehicle details Admin

2.3 User Characteristics:

There are two types of users in from each subsystem of the system

Role Description Prerequisite Knowledge

Customers Customers are the users who Basic knowledge to access the
uses the system to book vehicle. internet using their smartphone
or computer. Familiar with
online systems.
Admin Admin are the users who High technical expertise and a
manages the CRS database and well experienced person. Has
the content of the system. knowledge of the domain and is
well aware of the functionalities.
3.0 Specific Requirements
3.1 Functional Requirements

Requirement ID REQ_FR1
Version 1.0
Description System should have registration function for new
users
Author Kevin

Requirement ID REQ_FR2
Version 1.0
Description System should have user verification upon each
attempt to log in to the system.
Author Kevin

Requirement ID REQ_FR4
Version 1.0
Description User should be able to view or search for available
cars to rent
Author Kevin

Requirement ID REQ_FR5
Version 1.0
Description User must be able to book cars which are
available only.
Author Byron

Requirement ID REQ_FR6
Version 1.0
Description User should be able to print receipt of the
transaction upon the booking car .
Author Byron

Requirement ID REQ_FR7
Version 1.0
Description System should have registration function for new
users
Author Kevin

Use Case Number 1

Search
Use Case Name Booking
Author/Source Kevin
Date of Creation November 30, 2018
Precondition(s) In the case that the customer lost the booking number, the
receptionist needs to enter the customers name or mobile
number in the required field.
The booking file is
Successful Post Condition viewed.
Actors Admin
Priority Low.
Flow of Events Basic Flow
Step Number Steps
1 The system prompts the user to enter:
Customer’s phone number.
Customer’s driving license
number.
Customer’s name.
2 The user enters the required information.
3 The system displays the profile.
The booking doesn’t exist.
4 The use case ends.
Alternate Flow: A1 (The booking doesn’t exist)
1 The system displays a message that the
booking doesn’t exist.
2 The user confirms the message.
3 The flow goes to the basic flow, step 1.
 Use Case Number 2
Use Case Name View Customer
Author/Source William
Date of Creation November 30, 2018
Precondition(s) When the customer requests to book a car, the user might
want to view the customer’s file to validate specific
information.
Successful Post Condition The customer’s file is displayed to the user.
Actors Receptionist
Priority Low.
Flow of Events Basic Flow
Step Number Steps
1 The use case begins when the user clicks
“View Customer” in the booking screen.
2 The system displays the customer’s file.
3 The user clicks “OK” when he finishes
checking the file.
4 The use case ends.

Requirement ID REQ_FR8
Version 1.0
Description System should allow admin to edit the content of
the webpage
Author Foong

Requirement ID REQ_FR8
Version 1.0
Description Admin should be able to add new vehicle data to
the database
Author Foong

Requirement ID REQ_FR9
Version 1.0
Description Admin should be able to view monthly report of
the users transaction in the system.
Author Byron
3.2 Performance Requirements

Requirement ID Description Priority Author

REQ_PR1 The average time take to Medium Foong
load the web page
should be less than
0.5seconds
REQ_PR2 The system should be Medium William
able to handle network
traffic and up to 500
concurrent users.

3.3 General Constraints

These are some of the constraints that can be faced by the Car Rental System (CRS) –

Schedule and Resource Constraints

a) Time can be listed as a constraint. We are expected to finish this SRS document within 4
months with distractions in between due to the time demanded by the other courses.

b) There may be budget constraints where the allocated amount for implementation might not
be enough.

c) To understand the things that were missing from the previous software, we may need the old
requirements documents to identify the features that are required now. There is a possibility
that the old system documents have been damaged due to improper storage or misplaced.

3.4 Software System Attributes

This section specifies the attributes that are expected from CRS and their implementations.

3.4.1 Accuracy

Requirement ID Description Priority Author

REQ_QA1 The CRS system should High Kevin
display accurate result
from the database when
users search for vehicles
3.4.2 Security

Requirement ID Description Priority Author

REQ_QA2 The CRS system should High William
only allow users to login
with valid credentials

Requirement ID Description Priority Author

REQ_QA3 The CRS system should High Byron
SSL connection secured
and should not be
vulnerable to SQL
injections

3.4.3 Usability

Requirement ID Description Priority Author

REQ_QA4 The CRS system should Medium Foong
be simple and easy to
learn for the users