Specifications
Version 1.0
Date: 4/12/2018
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:
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.
Definitions
Acronyms
1.4 References
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.
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.
There are two types of users in from each subsystem of the system
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
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
These are some of the constraints that can be faced by the Car Rental System (CRS) –
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.1 Accuracy
3.4.3 Usability