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

SRS DOCUMENT 2