SYNOPSIS OF SRS

DOCUMENT FOR ONLINE

RAILWAY RESERVATION
WEBSITE: IRCTC
(Indian Railway Catering And Tourism Corporation)

NAME: SHUBHAM AGRAWAL

ROLL NO: 01

SECTION: K17QP

REG NO: 11706977

GROUP 1
 CONTENT OF THE SYNOPSIS:
1. INTRODUCTION
1.1 SCOPE OF PROJECT

2. FUNCTIONAL REQUIREMENTS
2.1 DETAILS OF THE JOURNEY

2.2 PNR STATUS

2.3 CHECK AVAILABILITY AND FARE

2.4 LOGIN

2.5 SIGN UP

2.6 PASSENGER DETAILS AND TRANSACTION

2.7 CANCEL BOOKED TICKET

2.8 e-CATERING

2.9 SERVICE AT STATIONS

3. NON-FUNCTIONAL REQUIEMENTS
3.1 SECUIRTY

3.2 RELIABILITY

3.3 AVAILABILITY

3.4 MAITAINABILITY

3.5 SUPPORTABILITY
INTRODUCTION
The introduction of the Software Requirement Specifications (SRS) provides an overview of the
entire SRS purpose, scope, definitions, acronyms, abbreviations, references and overview of
SRS. A Software Requirement Specification (SRS) – a required specification for a software
system- is complete description of the behavior of the system to be developed. It includes a set of
use cases that describes all the interactions the user will have with the software. Use cases are
also known as Functional Requirements. In addition to the used cases, the SRS also contains
non-functional requirements. Non-Functional Requirements are the requirements which
impose constraints on the design or implementation. The aim of the document is to gather and
analyse and give an in-depth insight of the complete software system in detail. This is
documentation of the project IRCTC (Indian Railway Catering And Tourism Corporation).
The program help us to enter, display or alter the details of different trains. Moreover and most
importantly the program helps us reserve or cancel a train ticket. The program also helps us to
know the present status of a reserved or cancel a train ticket, i.e. whether the ticket is confirmed
or not. The Indian Railways (IR) carries about 5.5 lakhs passengers in reserved accomodation
every day. The Computerised Passenger Reservation System (PRS) facilates the booking and
cancellation of tickets from any of the 4000 terminals (i.e. PRS bookin window all over the
countries). These tickets can be booked or cancelled for journeys commencin in any part of India
and ending in any other part, with travel time as long as 72hours and distance upto several
thousand kilometers. The project of PRS was launched on 15th November 1985, over Northern
Railway with the installation of Integrated Multiple Train Passenger Reservation System
(IMPRESS), an online transaction processing system developed by Indian Railways in
association with Computer Maintenance Corporation Ltd., at New Delhi. The objective was to
provide reserved accomodations on any train from any counter, preparation of train charts and
accounting of the money collected. The application was implemented in 1987 Mumbai, Chennai,
Kolkata, Secunderabad subsequently.
SCOPE OF PROJECT
Online ticketing service introduced by the Indian Railway in 2003 caught the attention of one
and all. But over the years the mobiles communication technology has surpassed the internet in
terms of its availability, penetration and ease of use. Currently Indian Railways do not have a
mobiles railway enquiry and booking system. This software system tries to bridge this gap. It is
designed to supplement the current modes of railway booking namely- over the counter booking
and online booking. The use of SMS to communicate enables all sections of the society to use
this service owing to their simplicity and the availability of the feature in all mobile phones.

This system enables a user/customer to enquire about a given train details (arrival, departure,
timings etc.) and to book, cancel or modify the tickets for their journey. In case of enquiry,
preformatted SMSs would be sent by the users to the mobile number provided and in return they
would receive a SMS with the required details. In case of booking again user would be requested
to fill n preformatted SMSs with the passenger details and other relevant information. On
booking, the money would be deducted from the users Mobile Bill (Postpaid) or the amount of
talk time left (Prepaid). The system updates the same database which the online system or the
counter booking system uses as they all are operational simultaneously.
FUNCTIONAL REQUIREMENTS
 2.1 DETAIL OF THE JOURNEY:
INPUT: The user need to input the station name (From, To), date, class.
OUTPUT: The user gets the related search trains is displayed.
PROCESSING: Related trains are searched.

 2.2 PNR STATUS:

INPUT: The user needs to input his/her PNR number.
OUTPUT: The user gets his/her PNR status of the ticket.
PROCESSING: Fetching details of PNR number.

 2.3 CHECK AVAILABILITY AND FARE:

INPUT: The user need to click on the check availability and fare button of respective
train.
OUTPUT: The user gets the details of the seat availability and fare of the travelling.
PROCESSING: Fetching current seat availability and fare of the train.

 2.4 LOGIN:
INPUT: The needs to provide his/her username and password to login.
OUTPUT: They get logged in.
PROCCESING: The user gets logged in into his/her account.

 2.5 SIGN UP:

INPUT: The needs to provide his/her complete details to create their IRCTC account.
OUTPUT: Their details will be provided and account will created.
PROCESSING: The user gets the facility to join it with his/her new account.

 2.6 PASSENGER DETAILS AND TRANSACTION

INPUT: The user need to input the passenger details and then card details for
transaction.
OUTPUT: The ticket is booked.
PROCESSING: Passenger details is saved and processing the transaction.
 2.7 CANCEL BOOKED TICKET
INPUT: The user needs to select the ticket which he/she wants to cancel.
OUTPUT: The ticket is cancelled.
PROCESSING: Cancelling the booked ticket.

 2.8 e-CATERING
INPUT: The user needs to input his/her PNR number and then select the food.
OUTPUT: The order is booked.
PROCESSING: Checking user’s PNR number and ordering the food.

 2.9 SERVICE AT STATIONS

INPUT: Wi-Fi railway station, battery operated cars, E-bedroll, E-wheelchairs, book a
cab, retiring room can be selected.
OUTPUT: Passenger gets these facilities at the particular stations.
PROCESSING: Services at the particular stations is provided.
NON-FUNCTIONAL REQIREMENTS
3.1 SECURITY:
The system use SSL (secured socket layer) in all transactions that includes any confidential
customer information. The system must automatically logout all customers from IRCTC after a
period of inactivity. The system should not leave any cookies on the customer’s computer
containing the user’s password. The system’s back-end servers shall only be accessible to
authenticated management.

3.2 AVAILABILITY:
The system should be available at all times, meaning the user can access it using a web browser,
only restricted by the down time of the server on which the system runs. A customer friendly
system which is in access of people around the world should work 24 hours. In case of a
hardware failure or database corruption, a replacement page will be shown. Also the backups of
the database should be retrieved from the server and saved by the organizer. Then the service
will be restarted. It means 24x7 availability.

3.3 RELIABILITY:
The reliability of the overall project depends on the reliability of the separate components. The
main pillar of reliability of the system is the backup of the database which is continuously
maintained and updated to reflect the most recent changes. Also the system will be functioning
inside a container. Thus the overall stability of the system depends on the stability of container
and its underlying operation system.

3.4 MAINTAINABILITY:
A commercial database is used for maintaining the database and the application server takes care
of the site. In case of a failure, a re-initialization of the project will be done. Also the software
design is being done with modularity in mind so that maintainability can be done efficiently.

3.5 SUPPORTABILITY:
The code and supporting modules of the system will be well documented and easy to understand.
Online User Documentation and Help System Requirements.