Software Requirements Specification for Railway Reservation System Page ii

Contents
CONTENTS...................................................................................................................................................................I
1 INTRODUCTION................................................................................................................................................1
1.1 SYSTEM INTRODUCTION..............................................................................................................................1
1.2 BACKGROUND OF THE SYSTEM..................................................................................................................1
1.3 OBJECTIVES OF THE SYSTEM.....................................................................................................................1
1.4 SIGNIFICANCE OF THE SYSTEM..................................................................................................................1
2 SUBMITTED BY
OVERALL DESCRIPTION...............................................................................................................................2
2.1 PRODUCT PERSPECTIVE.............................................................................................................................2
2.2  Maryam Safdar SP21-BSE-074
PRODUCT SCOPE........................................................................................................................................2

RAILWAY
2.3 PRODUCT FUNCTIONALITY..........................................................................................................................2
2.4
 Quratullain Javed SP21-BSE-067
USERS AND CHARACTERISTICS..................................................................................................................2
2.5  Romaisa Bibi SP21-BSE-056
OPERATING ENVIRONMENT.........................................................................................................................2
3 SPECIFIC REQUIREMENTS...........................................................................................................................3
3.1
3.2
3.3
RESERVATION
FUNCTIONAL REQUIREMENTS.....................................................................................................................3
Course
BEHAVIOUR REQUIREMENTS......................................................................................................................3
EXTERNAL INTERFACE REQUIREMENTS.....................................................................................................3
4
Object Oriented Software Engineering
OTHER NON-FUNCTIONAL REQUIREMENTS..........................................................................................5
4.1
4.2
4.3
SYSTEM
PERFORMANCE REQUIREMENTS................................................................................................................5
SAFETY AND SECURITY REQUIREMENTS...................................................................................................5
SOFTWARE QUALITY ATTRIBUTES..............................................................................................................5
5 DESIGN DESCRIPTION...................................................................................................................................6
System Requirement And Design Specification
5.1 COMPOSITE VIEWPOINT...............................................................................................................................6
5.2 LOGICAL VIEWPOINT...................................................................................................................................6
5.3 INFORMATION VIEWPOINT...........................................................................................................................6
5.4 INTERACTION VIEWPOINT............................................................................................................................6
5.5 STATE DYNAMICS VIEWPOINT.....................................................................................................................6
5.6 ALGORITHM VIEWPOINT..............................................................................................................................6
Software Requirements Specification for Railway Reservation System Page 3

1 Introduction
1.1 System Introduction

This system is basically concerned with the reservation and cancellation of

railway tickets to the passenger. The need of this system arouse as it is not possible
to handle such a large system manually. By computerizing it, it became possible to
overcome the limitations and make the system operations more efficient. The
complexity in handling data and records of such a vast system got reduced and
became easier by computerizing the system.

Being more specific, this online railway reservation system can perform the basic
functions like reservation and cancellation. The users are required to register on
the server for getting access to the database and query result retrieval. Upon
registration completion, each user has an account which is essentially referred to as
the view level of the customer. The account contains comprehensive information of
the user entered during the registration and allows the user to access their past
reservations, cancellations, enquire about trains and train schedule, seat availability
and make afresh reservations. The user will also be able to update their account
details etc.

The master user of this system is the Railway Administrator who can login using a
master password and once a user is authenticated as the admin, he/she can access and
modify information stored in the database of this system. This includes adding and
updating of train, station, train routes and also managing the user and the passenger
details.

1.2 Background of the System

The railway reservation system facilitates the passengers to enquire about the trains
available on the basis of source and destination, booking and cancellation of tickets,
enquire about the status of the booked ticket, etc. The purpose is to design and develop a
database maintaining the records of different trains, train status, and passengers. The
record of train includes its number, name, source, destination, and days on which it is
available, whereas record of train status includes dates for which tickets can be booked,
total number of seats available, and number of seats already booked.

1.3 Objectives of the System

The origin of most software systems is in the need of a client, who either wants to
automate the existing manual system or desires a new software system. The software
system is itself created by the developer. Finally, the end user will use the completed
system. Thus, there are three major parties interested in a new system: the client, the
user, and the developer. Somehow the requirements for the system that will satisfy
Software Requirements Specification for Railway Reservation System Page 4
the needs of the clients and the concerns of the users have to be communicated to the
developer. The problem is that the client doesn't usually design the software or the
software development process and the developer does not understand the client's
problem and the application area. This causes a communication gap between the
parties involved in the development of the project.
The basic purpose of Software Requirement Design Specification (SRDS) is to
bridge this communication gap. SRDS is the medium through which the client's and
the user's needs are accurately specified; indeed, SRDS forms the basis of software
development.

Another important purpose of developing an SRDS is helping the clients

understanding their own needs. An SRDS establishes the basis for agreement
between the client and the supplier on what the software product will do.

An SRDS provides a reference for validation of the final product. A high quality
SRDS is a prerequisite to high quality software and it also reduces the development
cost.

A few factors that direct us to develop a new system are given below -:
1. Faster System
2. Accuracy
3. Reliability
4. Informative
5. Reservation and cancellation from anywhere to any place.

1.4 Significance of the System

Here the railway reservation system is proposed with the following

 The computerization of the reservation system will reduce a lot of paperwork
and hence the load on administrative staff.
 The machine performs all calculations. Hence the chances of error are nil.
 The passenger, reservation and cancellation list can easily be retrieved and
any required addition, deletion or updation can be performed.
 The system provides for user-ID validation; hence the unauthorized access is
prevented.

2 Overall Description
2.1 Product Perspective

Before the automation, the system suffered from the following DRAWBACKS:
Software Requirements Specification for Railway Reservation System Page 5

 The existing system is highly manual involving a lot of paper work and
calculation and therefore may be erroneous. This has led to inconsistency and
inaccuracy in the maintenance of data.
 The data, which is stored on the paper only, may be lost, stolen or destroyed
due to natural calamity like fire and water.
 The existing system is sluggish and consumes a lot of time causing
inconvenience to customers and staff.
 Due to manual nature, it is difficult to update, delete, add or view the data.
 Since the number of passengers has drastically increased before maintaining
and retrieving detailed record of passengers is extremely difficult.
 A railway has many offices around the world, an absence of link between
these offices lead to lack of coordination and communication.
Here the railway reservation system is proposed with the following
 The computerization of the reservation system will reduce a lot of paperwork
and hence the load on administrative staff.
 The machine performs all calculations. Hence the chances of error are nil.
 The passenger, reservation and cancellation list can easily be retrieved and
any required addition, deletion or updation can be performed.
 The system provides for user-ID validation; hence the unauthorized access is
prevented.

2.2 Product Scope

Railway Reservation System is an attempt to simulate the online reservation

system. The system enables to perform the following functions:
 Search for a train
 Booking of a selected flight
 Payment
 Cancellation
 Improved and optimized service

2.3 Product Functionality

Booking agents with varying level of familiarity with computers will mostly use this
system. With this in mind, an important feature of this software is that be relatively
simple to use. The scope of this project encompasses:
 Search: This function allows the booking agent to search for train that are available
between the two travel cities, namely the Departure city" and "Arrival city" as desired by
the traveler. The system initially prompts the agent for the departure and arrival city, the
date of departure, preferred time slot and the number of passengers. It then displays a list
Software Requirements Specification for Railway Reservation System Page 6
of train available with different airlines between the designated cities on the specified
date and time.
 Selection: This function allows a particular train to be selected from the displayed list.
All the details of the train are shown:
I. Train Number Date
II. Time and place of departure Date
III. time and place of arrival
IV. Train Duration
V. Fare per head

 Review: If the seats are available, then the software prompts for the booking of train. The
train information is shown. The total fare including taxes is shown and flight details are
reviewed. Traveler Information: It asks for the details of all the passengers supposed to
travel including name, address, telephone number and e-mail id. Payment: It asks the
agent to enter the various credit card details of the person making the reservation.
 Credit card type
 Credit card number
 CVC number of the card
 Expiration date of the card
 The name on the card
Cancellation: The system also allows the passenger to cancel an existing
reservation. This function registers the information regarding a passenger who has
requested for a cancellation of his/her ticket. It includes entries pertaining to the train
No., Confirmation No., Name, Date of Journey, Fare deducted.

2.4 Users and Characteristics

 Educational level: At least the user of the system should be comfortable with the English
language. He/she should have knowledge of online transaction.
 Technical level: User should be comfortable with using purpose application on the
computer system.
 Knowledgeable user 
 No voice user 
 Expert user 

2.5 Operating Environment

Operating environments are:
 Windows NT2
 Windows XP
 Windows 98
 Linux
Operations:
 Any Reservation counter from 8 am to 8 pm.
 Prior to 60 days of Journey.
Software Requirements Specification for Railway Reservation System Page 7
 One form for 6 persons only.
 Reserved ticket done through pre-defined Logic.
 To save time & queues Agent is others guides
 Overview is a database system made on SQL and Java. As you open the system it will firstly
take your information and in return the user will get his train schedule and timing details
immediately after entering the data, the system has also a backup source if by chance the system
gets technical problem or failed due to some reasons it will immediately provide us the backed-up
file or data.

3 Specific Requirements
3.1 Functional Requirements

 User Satisfaction: - The system is such that it stands up to the user expectations.

 Response Time: -The response of all the operation is good. This has been made possible by
careful programming.

 Error Handling: - Response to user errors and undesired situations has been taken care of to
ensure that the system operates without halting.

 Safety and Robustness: - The system is able to avoid or tackle disastrous action. In other words,
it should be foul proof. The system safeguards against undesired events, without human
intervention.

 Portable: -The software should not be architecture specific. It should be easily transferable to
other platforms if needed.
Software Requirements Specification for Railway Reservation System Page 8

3.2 Behaviour Requirements

 Use Case Model:

 Use case 2: User Registration:

Use Case ID XYZ-001

Use Case Name Registration
Actors Traveler, Railway station, Ticketing system,
Railway admin, database, Bank
Purpose For User Registration
Pre-condition User select the registration form to fill
Post-condition Information is valid. Save in database,
invalid information. Error message
displayed.
Success scenario All provided information is valid. User
Action System Response.
User fill the required fields The system will save the data in database.

4 Other Non-functional Requirements

4.1 Performance Requirements

 User Satisfaction: - The system is such that it stands up to the user expectations.
 Response Time: -The response of all the operation is good. This has been made possible
by careful programming.
Software Requirements Specification for Railway Reservation System Page 9

 User friendliness: - The system is easy to learn and understand. A native user can also
use the system effectively, without any difficulties.

4.2 Safety and Security Requirements

The system is able to avoid any avoid or tackle any disastrous actions. In other words, it
should be fool proof. The system safeguards any undesired events, without any human
intentions.

The system use SSL in all requirements in all transactions that may include any
confidential customer information. The system must automatically log out all customers
after a period of inactivity. The system should not leave any cookies on the customer
computers containing passwords. The systems back-end servers shall only be accessible by
authentic management.

4.3 Software Quality Attributes

 Usability: Manage user and store their data.

 Reliability: Only registered members are allowed to view content.
 Maintainability: Content will be provided individually so system doesn’t slow down.
 Flexibility: Will keep the user up to date with content.
 Adaptability: To create a user friendly interface with minimum information to access it.
The content will be provided when a specific course will be picked.
Software Requirements Specification for Railway Reservation System Page 10

5 Design Description
5.1 Composite Viewpoint
Software Requirements Specification for Railway Reservation System Page 11

5.2 Logical Viewpoint

Software Requirements Specification for Railway Reservation System Page 12

5.3 Information Viewpoint

Software Requirements Specification for Railway Reservation System Page 13

5.4 Interaction viewpoint

5.5 State Dynamic Viewpoint

Software Requirements Specification for Railway Reservation System Page 14

5.6 Algorithm Viewpoint

Here is an outline of an algorithm that you could use to implement a railway reservation system:
a) Begin by creating a database of trains, with information such as the train number, the
source station, the destination station, and the timetable.
b) Create a user interface that allows the user to enter their travel details, such as the source
station, the destination station, and the date of travel.
c) Query the database to find all the trains that operate between the source and destination
stations on the given date.
d) Display the list of trains to the user, along with the available classes (e.g. first class,
second class) and the fare for each class.
e) Allow the user to select a train and a class, and then check if there are any seats available
in the chosen class on the selected train.
f) If seats are available, reserve a seat for the user and issue a ticket. If the seats are not
available, display a message to the user indicating that the booking could not be
completed.