Software Requirements

Specification
for

Railway Reservation System

Version 1.0 approved

Prepared by

Shubham Gupta

JSSATE NOIDA

28 JAN 2019

SRS DOCUMENT 1
Software Requirements Specification for  Railway Reservation System
Page 2

Table of Contents

Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose.................................................................................................................................1
1.2 Document Conventions........................................................................................................1
1.3 Intended Audience and Reading Suggestions......................................................................1
1.4 Product Scope......................................................................................................................1
1.5 References............................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective..............................................................................................................2
2.2 Product Functions................................................................................................................2
2.3 User Classes and Characteristics.........................................................................................2
2.4 Operating Environment........................................................................................................2
2.5 Design and Implementation Constraints..............................................................................2
2.6 User Documentation............................................................................................................2
2.7 Assumptions and Dependencies..........................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces.....................................................................................................................3
3.2 Hardware Interfaces.............................................................................................................3
3.3 Software Interfaces..............................................................................................................3
3.4 Communications Interfaces.................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1..................................................................................................................4
4.2 System Feature 2 (and so on)...............................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements..................................................................................................4
5.2 Safety Requirements............................................................................................................5
5.3 Security Requirements.........................................................................................................5
5.4 Software Quality Attributes.................................................................................................5
5.5 Business Rules.....................................................................................................................5

SRS DOCUMENT 2
Software Requirements Specification for Railway Reservation System      
Page 1

1. Introduction

1.1 Purpose

The purpose of this source is to describe the railway reservation system which provides the train
timing details,reservation,,billing,cancelaation on various types of reservation namely.
i.  Confirm Reservation for confirm Seat. 
ii.  Reservation against Cancellation 
iii.  Waiting list Reservation. 
iv.  Online Reservation. 
v.  Tatkal Reservation

1.2 Intended Audience and Reading Suggestions

the different types of readers are customer 

i.  Developers 
ii.  Management 
iii.  Passengers 
iv.  Counter clerk

1.3 Product Scope

Freight Revenue enhancement.

i.  Passenger Revenue enhancement. 
ii.  Improved & optimized service. 
iii.  This project designs and implements RRS to fulfill all the vision statements. Supported by a
well designed database, all available air train information is integrated together and can be
accessed easily through a single point. A friendly user interface is provided so that various
combinations of search criteria can be fetched from user and generates corresponding database
search statements. RRS provided both customer and administration interfaces with the latter
used for administration purposes. If time permits, RRS will support frequent user registration
and personal information management.

1.4 References

https://www.ieee.org/
https://www.scribd.com/doc/106534282/SRS-Railway-Reservation-System

2. Overall Description

2.1 Product Perspective

It enables us to maintain the railway train details like their timings, number of seat available and
reservation billing and cancelling the tickets.

SRS DOCUMENT 1
Software Requirements Specification for Railway Reservation System      
Page 2

2.2 Product Functions

OMBS will have two users interface layers,first one is guest interface and the second one is Train
Management Interface.

2.3 Operating Environment

i.  The OS
ii.  Windows NT
iii.  Linux
iv.  Windows XP
v.  Windows 98

2.4 Design and Implementation Constraints

A maximum of 42 laces hits per day have been recorded.

No hardware interface specified for RRS
The RRS should transmit and store the detailed properties (quantities, train number, departure/return
time/date, seat, location) of ticket items for the potential requests from users.
The Train/ticket inventory/database system should keep updated information about the availability
of ticket and train information to determine whether a requested reservation is available or not.
When the RRS make the query about ticket information with constrains, Train/ticket
inventory/database system should provide all the information that satisfy the query.
The Train/ticket inventory/database system should accept information update operation flows
coming from the administrator interface system

2.5 User Documentation

i. To allow a user post various query about ticket information available at present. User can use
any combination available
ii. To show the user the resulting list of query. This should allow users to further sort the list by
sub fields of the ticket information (e.g. price). The view should be friendly and flexible.
iii. To allow a user place a reservation
iv. To detect the conflict if a user placed two incompatible reservations.
v. To allow a user view his/her reservation
vi. To allow user modify his/her reservation
vii. To allow user to manage his/her account in RRS

2.6 Assumptions and Dependencies

i. Users of RRS are assumed to have a computer with internet access.

ii. Credit and debit card authorization services are assumed to be available.

3. External Interface Requirements

3.1 User Interfaces

keyboard,mouse,printer.

SRS DOCUMENT 2
Software Requirements Specification for Railway Reservation System      
Page 3

3.2 Hardware Interfaces

SERVER SIDE
i. Operating System: Windows 7 
ii. Processor:Intel i5 
iii. Memory: 4 GB 
iv. Hard Drive Capacity: 750GB
CLIENT SIDE
v.  Operating System:Windows XP, Windows Vista or Windows7
vi.  Browser:Internet Explorer and above.Mozilla or Google Chrome.
vii.  Memory:512 MB

3.3 Software Interfaces

i. Database
ii. Microsoft office Access 
iii. Web Server 
iv. Programming Languages

3.4 Communications Interfaces

i. Broadband Internet
ii. Broadband Internet

4. System Feature

4.1Description and Priority

The search feature allows the user to search for an rail line train on a variety of dimensions.
4.2Functional Requirements
REQ-1:The user will be able to search for trains through a standardized screen. Advanced options
will be available by clicking appropriate links.
REQ-2:Through the standard trains search method the user shall be able to specify the departure and
return date of their trains.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

PE­1: The system shall accommodate 400 users during the peak usage time window of 8:00am to 
10:00am local time, with estimated average session duration of 45 minutes.
PE­2: All Web pages generated by the system shall be fully downloadable in no more than 10 
seconds over a 40KBps modem connection.
PE­3: Responses to queries shall take no longer than 10 seconds to load onto the screen after the 
user submits the query.

SRS DOCUMENT 3
Software Requirements Specification for Railway Reservation System      
Page 4

5.2 Safety Requirements

No safety requirements have been identified.

5.3 Security Requirements

SE­1: Users shall be required to log in to the RRS for their own reservation information and 
modification with e­mail address and password.
SE­2: The system shall permit only authorized members who are on the list of authorized Menu
Managers to do administrator’s task.
SE­3: The system shall permit customers to view only their own previously placed orders, not 
orders placed by other customers.

5.4 Software Quality Attributes

The system shall be web based system that runs on different type of browsers such as Internet
Explorer,Mozilla,Google chrome.
There are a number of factors in the client’s environment that may restrict the choices of a designer.
Such factors include standards that must be followed, resource limits, operating environment,
reliability and security requirements and policies that may have an impact on the design of
thesystem. An SRS (Software Requirements Analysis and Specification) should identify and specify
all such constraints.

5.5 Business Rules

This specifies the requirements for the standards the system must follow. The standards may include
the report format and accounting properties.

SRS DOCUMENT 4