AIM: Do requirement analysis and develop Software Requirement

Specification Sheet (SRS) for “Railway Reservation System”.

Software Requirements
Specification
For

Railway Reservation System

Version 1.0 approved
Prepared by:
Name: S.KiranSai

Reg.No: Y20AIT508

Bapatla Engineering College

Date:16/09/2022
Table of Contents
Table of Contents ......................................................................................................... i
1. Introduction ............................................................................................................. ii
1.1 Purpose ...........................................................................................................................1
1.2 Document Conventions ................................................................ …………………….1
1.3 Scope of Development Project .......................................................................................1
1.4 Definitions, Acronyms and Abbreviations .................................... ……………………1
1.5 References……………………………………………………………………………...2
2. Overall Description ................................................................................................ .2
2.1 Product Perspective ....................................................................................................... 2
2.2 Product Functions............................................................................................................3
2.3 User Classes and Characteristics.....................................................................................5
2.4 Operating Environment......................................................................... ……………….5
2.5 Assumptions and Dependencies......................................................................................5
2.6 Requirements..................................................................................... ………………….6
2.7 Data Requirements……………………………………………………………………..6
3. External Interface Requirements .......................................................................... .6

3.1 GUI……………………………………………………………………………………..6
4. System Features ..................................................................................................... ..7
5. Other Nonfunctional Requirements ...................................................................... .7
5.1 Performance Requirements ............................................................................................ 7
5.2 Safety Requirements...................................................................................................... .8
5.3 Security Requirements ....................................................................................................8
5.4 Requirements Attributes ..................................................................................................8
5.5 Business Rules…………………………………………………………………………..8
5.6 User Requirements………………………………………………………………………9
6. Other Requirements……………………………………………………………….....9
6.1 Data and Category Requirement………………………………………………………....9
6.2 Appendix………………………………………………………………………………....9
6.3 Glossary………………………………………………………………………………….9
6.4 Class Diagram…………………………………………………………………………...10

Revision History

Name Date Reason For Changes Version

1. Introduction
1.1 Purpose
The purpose of this source is to describe the railway reservation system which provides train
timing details, reservation, billing and cancellation on various types of reservation namely.
• Confirm Reservation for confirm Seat.
• Reservation against Cancellation.
• Waiting list Reservation.
• Online Reservation.

1.2Document Conventions
 Entire document should be justified.
 Convention for the Main title
 Font face: Times New Roman
 Font style: Bold
 Font Size: 14
 Convention for Subtitle
 Font face: Times New Roman
 Font style: Bold
 Font Size: 12
 Convention for body
 Font face: Times New Roman
Font Size: 12

1.3 Scope of Development Project:

“Railways Reservation System” is an attempt to simulate the basic concept of an online
Reservation system. The system enables to perform the following functions:
 Search for Train
 Booking of the selected Train
 Payment
 Cancellation
 Passenger Revenue enhancement
 Improved & Optimized Service.

1.4Definitions, Acronyms and Abbreviations
JAVA➫platform independence
 SQL➫Structured query Language
 ER➫Entity Relationship
UML ➫ Unified Modeling Language
 IDE➫Integrated Development Environment
1.5References
 Books
 Software Requirements and Specifications: A Lexicon of Practice, Principles
and Prejudices (ACM Press) by Michael Jackson
 Software Requirements (Microsoft) Second Edition by Karl E
 Software Engineering: A Practitioner’s Approach Fifth Edition by Roger S
 Websites
www.yatra.com

2. Overall Descriptions
2.1 Product Perspective:
Use Case Diagram of Railway Reservation System

 Use Case Diagram are central to modeling the behavior of a system ,a subsystem or a
class.
 Each one shows a set of UseCase and actors and their relationships.
2.2 Product Function: -
Entity Relationship Diagram of Railway Reservation System

ER diagram provides entities (ie data object), properties, and associated methods, in order to
describing the conceptual model of the real world. The basic elements of ER diagram are
constituted by entities, attributes and links.
The representation is as following:
Entity type: It is expressed by rectangle. The entity name is written in the rectangle.
Attribute: It is expressed by oval and linked with the corresponding entity by line;
multi-valued attributes is connected by the two-lane;
line is added under the name of the main attribute.
Contact: It is expressed by the diamond and linked with the corresponding entity by line. The
contact name is written in the diamond box. The contact type is written near by the line.
2.3 User Classes and Characteristics
 The features that are available to the users are:-
 A user can book Ticket
 A user can cancel Ticket
 A user can know ticket status by a query
 A user can know train status by a query

2.4 Operating Environment

The OS types are:
 Windows NT
 Windows XP
 Windows 98
 Linux

2.5 Assumptions and Dependencies

The assumptions are:-
 The coding should error-free
 The system should be user-friendly so that it is easy to use for the users
 The information of all user accounts must be stored in a database that is
accessible by the software
 The system should support quick booking
 The Railway Reservation System is running 24 hours a day
The dependencies are: -
 The end users should have a proper understanding of the product
 The information of all the users must be stored in a database that is accessible by
the Railway Reservation System
 Any Booking is to be recorded in the database and the data entered should be
correct.

2.6 Requirement
Software Configuration: -
 Front end -> Visual Basic
 Back end -> MS-Access
Hardware Configuration: -
 Printer
 Normal PC

2.7 Data Requirement

The inputs consist of the booking to the database and the output consists of the output for the
reservation. The output also includes the user receiving the details of their reservation. In this
project the inputs will be the booking as fired by the users like starting location, Destination
location. Now the output will be visible when the user requests the server to get details of
their reservation.

3. External Interface Requirement

3.1 GUI :
 The software provides good graphical interface for the user and performing the required
task such as login,create, update, viewing the details of the account.
 Error text will appear preceding with cross sign ‘×’.
 All the modules provided with the software must fit into this graphical user interface and
accomplish to the standard defined .
TRAIN DETAILS:-
Customers may view the train timing at a date their name and number of tickets.
RESERVATION:-
After checking the number of seats available the customers reserve the tickets.
BILLING:-
After reserving the required amount of tickets, the customer paid the amount.
CANCELLATION:-
If the customers want to cancel the ticket, then half of theamount paid by the
customer will be refunded to him.

4. System Features
 It is available during all 24 hours.
Offered through Mail express, super fast , Rajdhani & Shatabdi Trains.
 It enables us to maintain the railway train details like their timings, number of seat
available and reservation billing and cancelling the tickets

5. Other Non-functional Requirements

5.1 Performance Requirements
 It is available during all 24 hours.
Offered through Mail express, super fast , Rajdhani & Shatabdi Trains.
Variety of compartments based on comfort :
 AC first class.
 AC sleeper
 First class
 AC three tier
 Sleeper class
 Ordinary chair car.

5.2 Safety Requirements

 Inside the train there will be a safety precautions:
 Electricity damage precautions
 Fire alerts
5.3 Security Requirements
 user have to carry and show one of following identity card of any of the passengers in
original while travelling.
 A three digit security helpline number 182 a user can use for help.

5.4 Requirement attributes

 Availability-1: The Railway Reservation System server will be available to users on the
99.9% of the time between 12:00AM To 11:50 PM .
 The bill passed on any proposals related to railway management needs approval of
Ministry of railway department.(Indian government).

5.5 Business Rules

 Users can not book the ticket at 11:50 PM to 12:00 AM,Railway Reservation
Server will update on 11:50PM.
 Same constraint will be applied on booking ticket.

5.6 User Requirements

The users are assumed to have basic knowledge of reading and writing in English. The
administrators of the system should have more knowledge of the internals of the system and
is able to rectify the small problems that may arise due to network issuse to maintain the
system. The proper user interface and instructions must be sufficient to educate the users on
how to use the system without any problems.
The admin provides certain facilities to the users in the form of:-
 Forgot Password
 Data replication i.e. if the data is lost in one branch, it is still stored with the server
 The server must be maintained regularly and it has to be updated from time to time.

6. Other Requirements
6.1 Data and Category Requirement
There are two categories of users namely user and admin. Depending upon the category of
user the access rights are decided. It means if the user is an administrator then he can be able
to modify the train details.

6.2 Appendix
A: Admin, Abbreviation, Acronym, Assumptions; B: Books, Business rules; C: Class,
Client, Conventions; D: Data requirement, Dependencies; G: GUI; K: Key; N: Non-
functional Requirement; O: Operating environment; P: Performance,Perspective,Purpose;
R: Requirement, Requirement attributes; S: Safety, Scope, Security, System features;
U: User, User class and characteristics, User requirement.

6.3 Glossary
The following are the list of conventions and acronyms used in this document and the project
as well:
 NTES – National Train Enquiry System.
 IVRS – Interactive Voice Response system.
  PRS – passenger reservation system.
 Maintainer: Group of experts maintain the system with time.
 Project Managers: Look over complete progress of project.

6.4 Class Diagram

A class is an abstract, user-defined description of a type of data. It identifies the attributes of
the data and the operations that can be performed on instances (i.e. objects) of the data. A
class of data has a name, a set of attributes that describes its characteristics, and a set of
operations that can be performed on the objects of that class. The classes’ structure and their
relationships to each other frozen in time represent the static model. In this project there are
certain main classes which are related to other classes required for their working. There are
different kinds of relationships between the classes as shown in the diagram like association.
The relationships are depicted using a role name and multiplicities. Here ‘booking’,
‘cancellation’ and ‘payment’ are the most important classes which are related to other classes .