Software Requirements

Specification

Railway Reservation System

Version 1.0 approved

Prepared by Ajith Kumar B

Alan B

Arun Pandi S

PSNA College of Engineering and Technology

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

Revision History
Name Date Reason For Changes Version
1 Introduction
1.1 Purpose
The purpose of this document is to present a detailed description of the Railway Reservation
software. It will explain the purpose and features of the software, the interfaces of the software, what
the software will do and the constraints under which it must operate. This document is intended for
users of the software and also potential developers .

1.2 Document Conventions

This Document was created based on the IEEE template for System Requirement Specification
Documents.

1.3 Intended Audience and Reading Suggestions

Typical Users, such as students, who want to use Gephi for analyzing networks (Social
networks, Social Media networks, Semantic networks etc.)

Advanced/Professional Users, such as engineers or researchers, who want to use Gephi

for more demanding graph analysis.

Programmers who are interested in working on the project by further developing it or

fix existing bugs.

1.4 Product Scope

“Railways Reservation System” is an attempt to simulate the basic concepts of an
online Reservation system. The system enables to perform the following functions:
 SEARCH FOR TRAIN
 BOOKING OF A SELECTED FLIGHT
 PAYMENT
 CANCELLATION
 Freight Revenue enhancement
 Passenger Revenue enhancement
 Improved & optimized service

1.5 Reference
IEEE Template for System Requirement Specification
Documents: https://goo.gl/nsUFwy
2 Overall Description
2.1 Product perspective

The system will allow access to only authorized personnel. Depending on

user’s role, he/she will be able to excess only specific modules of the system. A
summary of the major functions hat the software will perform are:
(i) A login facility for enabling only authorized person to the system.
(ii) User (with role of DBA) will be able to add/modify/delete information
about different passengers that can  have name in reservation
list, waiting list, train schedule.
(iii) User (with role of a operator) will be able to access passengers details, fine details
and view monthly reports.

2.2 Product Functions

Booking agents with varying levels of familiarity with computers will mostly use this
system. With this in mind, an important feature of this software is that it 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
traveller. 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 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 :-

1. train Number
2. Date, time and place of departure
3. Date, time and place of arrival
4. TRAIN Duration
5. Fare per head
6. Number of stoppages – 0, 1, 2…

    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.

   Traveller 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.

1. Credit card type

2. Credit card number
3. CVC number of the card
4. Expiration date of the card
5. 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.3 User classes and Characteristics

EDUCATIONAL LEVEL: At least user of the system should be comfortable with

English language.

TECHNICAL EXPERTISE: User should be comfortable using general purpose

applications on the computer system.

2.4 Operating Environment

 Windows 2000
 Windows XP
 Windows Vista
 Windows 7
 Windows 8
 Windows 10
 Mac OS X
 Linux

2.5 Design and Implementation Constraints

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 the system.

Software constraints:

The system will run under windows98 or higher platforms of operating system.
2.6 User Documentation

2.7 Assumptions and Depndencies

 Booking Agents will be having a valid user name an password to access the software

 The software needs booking agent to have complete knowledge of railways reservation
system.

 Software is dependent on access to internet.

3 External Interface Requirements

3.1 User Interface