Software Requirement

Specification
Car Rental System
Prepared by
Bhisma Nambiar A/L Janar Danan 187826

Lee Jin Wee 186995

Muhamad Naqib Bin Yahya Bazlan 187432

Tan Yong Lin 186933

Lecturer: Dr. Jamilah Binti Din

Table of Contents Page

1. Introduction
1.1 Purpose 1
1.2 Document Conventions 1
1.3 Intended Audience and Reading Suggestions 1
1.4 Project Scope 1
1.5 References 1

2. Overall Description
2.1 Product Perspective 2
2.2 Product Features 2
2.3 User Classes and Characteristic 2
2.4 Operating Environment 3
2.5 Design and Implementation Constraints 3
2.6 Assumptions and Dependencies 3

3. External Interface Requirement

3.1 User Interfaces 4
3.2 Hardware Interfaces 4
3.3 Software Interfaces 4
3.4 Communications Interfaces 4

4. System Features
4.1 Functional Requirements 5

5. Nonfunctional Requirements
5.1 Performance Requirements 6
5.2 Security Requirements 6
5.3 Software Quality Attributes 6

6. Appendices
6.1 Appendix A-Use Case Diagram 7
6.2 Appendix B-Flow of Events 8

i
1. Introduction

1.1 Purpose
The aim of this document is to identify and specify the user and software requirements
for car rental system.

1.2 Document Conventions

UPM – Universiti Putra Malaysia
RDB – Relational database
Font used – Times New Roman size 12

1.3 Intended Audience and Reading Suggestions

This project is a prototype for car rental system and it’s restricted nearby UPM premises.
This implementation of the system is done under the supervision of UPM lecturer. This
system is intended for agencies which run car rental business.

1.4 Project Scope

This project is built mainly to ease car rental agency to manage their business as well
as providing a convenient interface for end-user to interact and enjoy the car rent
services. The system will be based on RDB with its car rent management and booking
functions. We strive to provide a perfect solution for car rental agency to manage their
business efficiently along with reasonable price.

1.5 References
 Sommerville, I. (2011). Software Engineering. 9th Ed. England: Pearson Addison
Wesley.
 https://krazytech.com/projects

1
2. Overall Description

2.1 Product perspective

A distributed car rental system stores the following information
 Customer details:
It includes customer first name, last name, ID, password and email.
 Vehicle details:
It includes the vehicle number, number of seats and transmission type.
 Reservation details:
It includes customer details, booking date and vehicle number

2.2 Product Features

A general flow on how the system will benefit the company is:

 Customer books desired car

 Employee able to assist in operations
 Ensures a smooth transaction to rent a car

2.3 User Classes and Characteristics

Customers are labeled as top priority as they come from a variety of backgrounds with different
computer literacy capabilities, followed by employees whom should come from basic
computer literacy background in order to perform day to day tasks using the system. The
customer should also be able to do the following functions:

 Make a new booking

 Confirm booking of desired car
 View booking details

2
Employee should have the following functionalities:

Customer functions.

 Get customer information

 View bookings done

Administrative functions.

 Add/remove car from inventory

 Update pricing
 View transactions

2.4 Operating Environment

Operating environment for the car rental management is as follows:

 Operating system: Windows

 Database: MySQL/Postgresql

2.5 Design and Implementation Constraints

Not relevant

2.6 User Documentation

A simple how-to guide is delivered along with the software to aid customers as well as
employees to teach and guide respective users.

2.7 Assumptions and Dependencies

Not relevant

3
3. External interface Requirements

3.1 User Interface

The system will have Four (4) modules namely, Customer portal website, employee portal,
inventory management and bookings management.

3.2 Hardware Interfaces

 Any computer that supports Windows as its operating system

 A browser that supports HTML

3.3 Software Interfaces

The system will interact with a database in order to keep track of bookings and inventory. The
system will also run on most current Windows platform (i.e: Windows 7, 8 and 10). The system
will also be available to customers through an online portal to make renting a car easier.

3.4 Communications Interfaces

This project supports all types of web browsers. We are using simple electronic forms for the
bookings, signing up, etc.

4
4. System Features

4.1 Functional Requirements

1. The customer shall allow to sign up an account.

2. The customer shall allow to book for their desired vehicle.

3. The employee shall allow to login with admin accounts.

4. The employee shall allow to manage the inventory.

5. The employee shall allow to view customer information.

6. The system shall display vehicles available for rent according to customers’ input.

7. The system shall accept payment in term of cash or credit card.

8. The system shall be able to issue a receipt after the payment is made.

5
5. Non-Functional Requirements

5.1 Performance Requirements

System should perform well in day to day operations with a refresh rate of 10 seconds. System
should also be able to respond to user actions with a maximum delay of 5 seconds on load
times with a targeted response time of 1.0 seconds, to keep up with transactions provided that
the internet speed is at least 5 Mbps and above.

5.2 Security Requirements

A secure login method is used by both employees as well as customers to access their specified
accounts to perform required tasks such as bookings. Employees have the right to view details
of customers, to process car rental agreements.

5.3 Software Quality Attributes

System will be user friendly with most basic tasks such as booking a car made as simple as
possible. A simple how-to guide will be done to guide customers and employees without the
need of training.

6
 6. Appendices

6.1 Appendix A- Use Case Diagram

Sign up account

Place booking

<<Include>> <<Include>>

Make payment Pay by credit card

View customer information

Manage inventory
Store
Employee

7
6.2 Appendix B- Flow of Event

Use Case 1: Sign up account

Actors: Customer
1. The customer will select sign up on the main menu.
2. The system will load up a sign up page.
3. The customer will need to fill in their first name, last name, email and password.
4. The customer will click on the sign up button to register their account.

Use Case 2: Place booking

Actors: Customer

1. The customer will type in location, date and time.

2. The system will display a list of vehicles available for rent.
3. The customer will click on the desired vehicle to rent.
4. The system will display the price according to the rental duration.
5. The customer will click on the book now button to proceed to the payment
section.

Use Case 3: Make payment

Actors: Customer

1. The system will load up the payment interface.

2. The customer will select the type of payment to be made.
3. The system will generate a receipt for printing after the payment is done.

8
Use Case 4: Pay by credit card

Actors: Customer

1. The customer will fill in their name, credit card number, expiration date and
security code to proceed.

Use Case 5: View customer information

Actors: Employee

1. The employee will select the customer information button once logged in.
2. The system will load up a list of customer details.
3. The employee can look up for customer details.
4. The employee can check the reservations made for each customer.

Use Case 6: Manage Inventory

Actors: Employee
1. The employee will select the manage inventory button once logged in.
2. The system will load up a list of registered vehicles.
3. The employee will select the new button to register a new vehicle to rent.
4. The employee will select the remove button to delete the selected vehicle from the
inventory