1

Software Requirements Specification Document

For Travel Agency Car Management Software
1. Introduction
1.1. Purpose
The purpose of this document is to describe the external requirements for an automated book-keeping
system that keep track of various operations of a travel agency. It also describes the interfaces for the
system.

1.2. Scope
This document describes the requirements of the above-mentioned system. It is meant to be used by
the developers and will be the basis for validating the final delivered system. Any changes made to the
requirements in the future will be made with the permission of the client. The developer is
responsible for asking for clarifications, where necessary.

1.3 Definitions, Acronyms, Abbreviations

DFD Data Flow Diagram
IEEE Institute of Electrical and Electronics Engineers

1.4. Document Overview

This document contains the functional and non-functional requirements of the system and the
Data Flow Diagram (DFD) of the system in the following pages.

1.5. References
IEEE standard -830-1998 ,Pankaj Jalote Software Engineering book.

1.6. Intended Audience

This document will be used for design purposes by the developers and the design team. It will be the
basis for validating the final delivered system.

1.7. SRS team members

This document is written by Srayan Datta(09CS1003).

2. Functional Requirements
2.1. Register Customers
2.1.1. Collect Detail about Customer
Input:
Customer name, customer address, phone number.
Output:
Request for deposit money (Rs. 5000).
Updating entered data in customer database as temporary.
Description:
Only for valid information Request is generated.
New set of information given must not match completely with an existing entry in customer
database.

2.1.2. Gather Deposit Money

Input:
Confirmation of receiving deposit money,
Previously entered customer data stored temporarily in customer database.
Output:
User name and password for the corresponding customer.
Converting of temporary customer data to permanent.
Description:
The employees of the organization permanently store the relevant data on confirmation of
receiving deposit money.

2.2. Process Online Request

2.2.1. Display car information
Input:
Online car request by the customer containing the date for which travel is required, the
destination, and duration for which the vehicle is required

Output:
List of all types of available cars with hourly charge and per kilometre charge.
Description:
This information is automatically generated on pressing a button by accessing the car database.

2.2.2. Display Hired car information and estimated charge

Input:
Customer choice for a particular choice from the list generated.
Output:
The number of the allotted vehicle and the drivers mobile numbers.
Estimated charge for the vehicle.
Updated the car status (as rented).
After the journey completes change status again to available.
Description:
Estimated charge for the vehicle is calculated as per rules mentioned in part 2.3.
The car status is updated as per rules mentioned in part 2.5.
The cars are allotted such that no two customers are allotted same car for same time interval.

2.3. Calculate and Collect Payment

Input:
Duty slip containing necessary information such as duration of hire and the kilometres covered
validated by customer at the end of journey, submitted by the driver of the car hired.
Confirmation of receiving payment.
Output:
Bill for the completed journey.
Updated database on confirmation of receiving payment.
Updated car status (as available).
Description:
The amount chargeable to a customer is the maximum of per hour charge for the car times
the number of hours used, plus the per kilometre charge times the number of kilometres run,
subject to a minimum amount decided by the charge for 4 hours use of the car.
An AC vehicle of a particular category is charged 25% more than a non-AC vehicle of the
same category.
There is a charge of Rs. 500/- for every night halt regardless of the type of the vehicle.
The car status is updated as per rules mentioned in part 2.5.

On confirmation of receiving payment updating will be done in customer database against the
particular customers name.

2.4. Edit car information

Input:
New car information.
Car statistics
Output:
Updated new car information.
Deleted old irreparable car information.
Updated car rent.
Description:
At arrival of new car, its information will be updated by the manager.
Old irreparable car information will be deleted by the manager and the car is declared
unusable.
Car rent can be increased or decreased based on car statistics.

2.5. Update Car Status

Input:
Car status (rented, gone to repair, available).
Output:
Updated car status.
Description:
The default car status is available. When a car is rented or gone to repair its status is updated.
When the car comes back, its status is again changed back to available.

2.6. Handle Statistics

Input:
Various car rent statistics stored in car database.
Output:
Car-wise statistics.
Description:
This functionality sorts the type of cars in order of their demand and net profit derived from a
type, which helps in predicting more profitable new car order.

3. External interface Requirements

3.1. User Interfaces
This software needs the following user interfaces:
i)
Registration Window:
User: The customer
Properties:
This window is used for entry of customer details and registering a new customer
for the online booking system.
This window has various text fields to take the information name, address, phone
number.
There will be a register button upon pressing which deposit money is asked for.
ii)
Log in Window:
User: The customer, the employees of the organisation using the software, the manager.
Properties:
This window has two fields for username and password, two buttons to log in and
register.
For correct user name and password it opens an appropriate window.

iii)

iv)

v)

It has register button to let new customer register by redirecting to registration

window.
Customer Homepage:
User: Registered customer
Properties:
This window opens when a customer logs in.
This window is used for online booking for a car of customers choice for a
particular time span and it has provision to display all available cars and let the
customer choose.
The billing information of a completed journey will be viewed using this window.
Employee Homepage:
User: The employees of the organisation using the software when logged in.
Properties:
This window opens when an employee logs in.
This window takes all necessary input from the duty slip and displays the
calculated net bill to be paid by the customer.
This window lets the user update a cars status (available, rented or gone to
repair).
When deposit money is collected the user updates the corresponding customer
info into customer database using this window.
When a payment is made ,it is updated in customer database using this window.
Manager Homepage :
User: The managers of the organisation using the software
Properties:
This window opens when one of the managers logs in.
This window lets the user add a new car and its specifications to the car database
and delete information of an old irreparable car from the database.
Car statistics will be viewed using this window.
Car rents can be changed according to car statistics.

3.2. Software Interfaces

The software runs under Linux or Windows operating system. This software uses two different
databases for cars and customers. Internet using facility is must.

3.3. Hardware Interfaces

The system will run on a computer with at least 256 MB RAM and with internet connection. The
machine is connected to a printer for printing bills etc.

3.4. Communication Interfaces

The software must be web browser enabled and HTTP protocol is used to transfer data.

4. Other Non-functional Requirements

4.1 Performance
In every case the response time will be less than 1 second except for the cases where internet
connection is used.

4.2 Security
This software offers password protection so that only regular customers can book cars, only authorized
personnel can edit data corresponding t0 booking, billing and car information.

5. Data Flow Diagrams

5.1. Diagrams

Car Database

car
details
Car statistics

changed
car
informa
tion

Customer information
Deposit money
Travel
Agency car
Manageme
nt Software
0

Deposit money request

Customer

car
status

User id and password

travel details
Full payment
Available car details
Hired car detail and
estimated charge
bill

Customer
information
(Temporary)

Car Dealer

Customer
information
validation
message

New car
information

Customer
Database
booking
information

Driver

Duty slip

Garage

'gone to repair'
car status

Manager

Changed car
information

Figure 1: Context diagram

billing
informa
tion

Deposit money

Customer
Database

*
Customer
Registrati
on
0.1

Customer
information

Customer
information
(Temporary)
Customer
information
validation
message

User id
and
password

Customer

Booking
information

Deposit
money
request

*
Car choice

Billing
information

Travel details
Process
online
request
0.2

Available car details

Hired car detail
and
estimated charge
'gone to
repair'
status

Garage

bill

'available'
status
Calculate
and collect
payment
0.3
Full payment

Figure 2: Level 1 DFD

Update
car
status
0.4

Car
details
Car
status

Car details

*
Duty
slip

Driver

Car Dealer

'rented'
status

New car
information

Edit car
information
0.5

Changed
car
information

Car Database

Car statistics
Changed
car
information

Manager

Collect
detail
about
Customer
0.1.1

Customer
Customer information
Deposit money request
Deposit
money

User id
and
password

Receive
deposit
and Update
0.1.2

Figure 3: level 2 DFD for registration

Customer
information
(Temporary)
Customer
information
validation
message

Customer
Database

Customer
Database

Booking
information
Travel details

Customer

Available
car
details

Car choice

Car Database

Car
details

Check
Available
Cars
0.2.1

Show
Hired
car
information
0.2.2

Hired car information

Car choice
*
Estimated charge

Calculate
estimated
charge
0.2.3

To Update car status

0.4
Figure 4: Level 2 DFD for processing online request

Driver
Duty slip

Car Database

Car details

Calculate
payment
0.3.1

bill
To Update car status
0.4

Customer

payment

Receive
payment
and Update
0.3.2
billing information
D

Customer
Database

Figure 5: Level 2 DFD for payment receive and update

5.2. Data Dictionary

Customer_information= Customer_name + Customer_address + Customer_phone_number
Travel_details = date + destination + duration
Available_car_details= Model + AC_status + hourly_charge + per_kilometre_charge
AC_status= AC | Non-AC
Car_status= Available |Rented | Gone to repair
Hired_car_details= Car_number + Driver_mobile_number
Duty_slip= Car_number + hourly_charge + per_kilometre_charge + hours_rented +
kilometres_traveled + Number_of_nighthalts
Bill= Customer_name + Model + AC_status +Calculated_charge
Booking_information= Customer_name +Travel_details + Estimated_ charge
Billing_information= Customer_name + Bill
Car_details= Car_number+ Model + AC_status + hourly_charge + per_kilometre_charge +
Driver_name + Driver_mobile_number
Car_statistics= Price + Average_repair_cost + Average_demand + revenue + fuel_consumption
Changed_car_information= Car_details + Car_statistics
New_car_information= Car_details + Car_statistics