CSE BATCH-A2

–––

RAILWAY RESERVATION
SYSTEM

Submitted To : Submitted By:

Prof. Amreen Khan Himanshu Shekhar (A-49)

Anurag Fulare (A-35)
Mrunal Singh Zire (A-59)
Abhishek Damani (A-33)

1
Table of content
1. Introduction
1.1 Purpose
1.2 DocumentConventions
1.3 Intended Audience and
ReadingSuggestions
1.4 Definitions,Acronyms and
Abbreviations
1.5 Scope
1.6 Reference

2. Overall description
2.1 ProductPerspective
2.2 ProductFunction
2.3 GuestInterface
2.4 Train ManagementInterface
2.5 OperatingEnvironment
2.6 MemoryConstrains
2.7 Operations
2.8 User Interface
2.9 Hardware Interface
2.10Software Interfaces
2.11Assumptions, Dependencies
&Limitations

3. SystemFeatures
3.1 Description &Priority
3.2 FunctionalRequirements
3.1.1 View TrainDetails
3.1.2 SearchTrain
3.1.3 CreateAccount
3.1.4 CustomerLogin
3.1.5 PurchaseTicket
3.1.6 PurchaseHistory
3.1.7 LoginFunction
3.1.8 StaffModule
3.1.9 ReservationModule
3.1.10 TicketModule
3.1.11 Membership
Module
3.1.12 TrainModule

2
 3.1.13 PricingModule
3.1.14 AvailabilityModule
3.1.15 BranchModule
3.1.16 ReportModule
3.1.17 AccessType

4. External InterfaceRequirements
4.1 User Interface
4.2 HardwareInterfaces
4.3 SoftwareInterfaces
4.4 CommunicationInterface

5. Non-functional Requirements
5.1 PerformanceRequirements
5.2 SafetyRequirements
5.3 SecurityRequirements
5.4 DesignConstraint
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 and cancellation on various types of reservation namely.
 Confirm Reservation for confirm Seat.
 Reservation againstCancellation
 Waiting listReservation.
 OnlineReservation.
 TatkalReservation

1.2 DOCUMENTCONVENTIONS:
 main heading: Bold
 notapplicable

1.3 INTENDED AUDIENCE AND READINGSUGGESTIONS:

the different types of readers are
 customer
 Developers
 Management
 Passengers
 Counterclerk

1.4 DEFINATIONS, ACRONYMS AND ABBREVIATIONS

 NTES- National Train EnquirySystem
 IVRS-Interactive Voice ResponseSystem
 PRS-Passenger ReservationSystem
consistof
traindetails
reservation form
billing
cancellation
1.5 SCOPE
 Freight Revenueenhancement.
 Passenger Revenueenhancement.
 Improved & optimizedservice.
 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 informationmanagement.
1.6 REFERNCES

www.scribd.comwww.yatr
a.comwww.google.comw
ww.info.com
http://www.cise.ufl.edu/~mschneid/Teaching/COP5725_Fall2008/project_spec.pdf
2. OVERALLDESCRIPION

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

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

2.3 GUESTINTERFACE:
 View TrainDetails
 SearchTrain
 CreateAccount
 CustomerLogin
 PurchaseTicket
 PurchaseHistory

2.4 TRAIN MANAGEMENTINTERFACE:

 Login Function
 Staff Module
 reservation Module
 TicketModule
 Membership Module
 Train Module
 PricingModule
 Availability Module
 BranchModule
 report module
 AccessType

2.5 OPERATINGENVIRONMENT
 Windows NT
 Linux
 Windows XP
 Windows 98
 MAC OS
 etc
 2.6 MEMORYCONSTRAINTS
A maximum of 42 laces hits per day have been recorded.

2.7 OPERATIONS:
 any reservation counter from 8 am to 8pm.
 prior to 60 days ofjourney.
 One form for 6 personsonly.
 Reserved ticket done through pre-definedLogic.
 To save time and queues agents is othersguides.

2.8 UserInterfaces
The system shall provide a help (explanation) link from each displayed HTML page to
explain how to use that page.
The Web page of RRS shall permit complete navigation, train selection, ticket reservation
and ticket/train information query view using keyboard and mouse combinations.

2.9 HardwareInterfaces
No hardware interface specified for RRS.

2.10 SoftwareInterfaces
Train/ticket inventory/database system:
(1) 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.
(2) 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 ornot.
(3) When the RRS make the query about ticket information with constrains, Train/ticket
inventory/database system should provide all the information that satisfy thequery.
(4) The Train/ticket inventory/database system should accept information update operation
flows
coming from the administrator interface system.

User query/view system:

The user query/view system should communicate with Train/ticket inventory/database
system through a programming interface for the following operations.

(1) To allow a user post various query about ticket information available at present. User can use
any combinationavailable
(2) To show the user the resulting list of queries. This should allow users to further sort the list
by subfields of the ticket information (e.g. price). The view should be friendly andflexible.
(3) To allow a user place areservation
(4) To detect the conflict if a user placed two incompatiblereservations.
(5) To allow a user view his/herreservation
(6) To allow user modify his/herreservation
(7) To allow user to manage his/her account in RRS
2.11 ASSUMPTIONS, DEPENDENCIES ANDLIMITATIONS
AS-1: Users of RRS are assumed to have a computer with internet access.
AS-2: Credit and debit card authorization services are assumed to be
available.
DE-1: RRS has collaboration with every airline’s databases thus it must be able to communicate
with these systems. Also, it has to obey airline’s business rules.
3. SYSTEMFEATURES

3.1 DESCRIPTION ANDPRIORITY

The search feature allows the user to search for anrail line train on a variety of dimensions.

3.2 FUNCTIONALREQUIREMENTS
Req # Description Priority

The user will be able to search for trainsthrough a

REQ-S1 [Priority = High]
standardized screen. Advanced options will be
available
by clicking appropriate links.
Through the standard trains search method, the user
REQ-S2 will [Priority = Medium]
be
able to search one-way, round-trip, or multi-destination
trains. The screen by default will displayoptions
for
searching round trip trains. The search criteriacan
be
modified by the user by selecting one-way and
multi-
destination options which would be displayed on a new
window.
Through the standard trains search method, the
REQ-S3 user shall be [Priority = High]
able to specify the departure and return date of them
trains.

Through an advanced train search method, the

REQ-S4 user shall be [Priority = Medium]
able to specify the arrival train times.
The standard train search method will enable the user
to
 REQ-S5 search both precise dates as well as a range of arrival [Priority = Medium]
and
departure dates.
REQ-S6 The standard train search method will allow the user to [Priority = Low]
specify a preferred rail line. This is optional, i.e. the
user
may or may not specify the rail line of preference.

REQ-S7 The user will have the option to express a preference of [Priority = Low]
non-stop train; otherwise both non-stop trains and trains

with stopovers will be treated equally.

User can only search for a train in the future and within one
REQ-S8 [Priority =
year of the current date. (The cutoff time can be High]
applied,
i.e. user cannot make the reservation for the train
which
will take off in 2 hours.)
The user to select any hour on the hour (i.e. trains at 12am,
REQ-S9 [Priority =
11am, 2pm etc.). High]
When the user is searching for a train he may select one of
REQ-S10 [Priority =
the following preset time ranges:Morning, Medium]
Afternoon,
Evening, Night, or Anytime.
User should be able to search by Train number and rail
REQ-S11 line. [Priority =
This will allow him to see the particular train for the Low]
particular rail line.
REQ-S12 The user may specify anywhere from 1 (one) to 6 (six) [Priority =
passengers. Passengers will not be treated separately as High]
minors or seniors.
REQ-S13 Any error in entry of the system will stop the system from [Priority = High]
processing the search. An error message will be presented
to the user.

GUEST INTERFACE:
 View TrainDetails
The system shall enable customer or visitor to view list of trains.
 SearchTrain
the system shall have search function. Customer can search train based on source and
destination station details with date and time.
 CreateAccount
the system shall function to create an account. The system shall record all the
following data from the customer.
a. Username
b. password
c. passwordconfirmation
d. first name
e. last name
f. identify cardnumber
g. address
h. zip code
i. city
j. state
k. country
l. mobile no.
 CustomerLogin
the system shall have customer login functions, onceactivated, customer can login using
username and password.
the system shall have username and password recovery function.
 PurchaseTicket
the system shall enable customer to purchase the train ticket from guest
interface. the system shall display all the train details.
the system shall display the date time and price of the ticket.
the system shall have book now button. when book now button is pressed, the system
shall prompt customer to login or registeraccount.
the system shall allow customer who have login only to continue to purchase ticket. If
customer haven’t login, prompt customer to login and create account.
 PurchaseHistory
the customer can watch all the purchase history from this module.

TRAIN MANAGEMENT INTERFACE:

 Login Function
The system should allow only staff username and passwd to access the
system. access to the module determined by acc type and branchoffice
Location.
 Staff Module
the system shallallowsystem administration only to access the module. System
administration shall login first to access thismodule.
the system shall aalow the system administration to add staff, update staff and delete
staff. the system shall record all the following details:
 a. StaffUsername
b. password
c. Account
d. FirstName
e. LastName
f. Address
g. City
h. State
 Reservation Module
the system shall allow counter clerk, station manager and station supervisor of the particular
station to access this module. They should login first.
the system shall limit the access to branch level only.
the system shall display the seating arrangements for
customers. the system shall display the total amount of
ticket. The system shall allow station manager or clerk to
check the details.

 Ticket Module

Ticketbooking:
The Ticket Booking is user (Employee of Railway Dept.) side module. The user can book
the ticket using this module. The user should follow the steps for the ticket booking.
First you should select the Source and Destination.
Next, you should select the Date. While the date textbox got focus, the calendar will display.
By clicking the calendar, the date will be selected. And you can’t select the yesterday and
before date.
a) Select the Quota (General orTatkal).
b) Click the Find button to find the trains which are available.
Note:
If you select the Tatkal Quota and the date is day after tomorrow in the sense, you can’t book the
ticket for Tatkal Quota for that day. The Tatkal Quota will enable only today and tomorrow only.
e) After clicking the find button, the available train list will be displayed in theflex grid.
f) By clicking the train number or train name in the flex grid, the “Route” button enabled. By
clicking the route button, the corresponding train route, timings, andkms.
g) By clicking the class column to the corresponding train whichever you want to travel,then
“Book” button willenable.
h) Click the “Book” button to enter the Name, Age, Sex andBerth.
i) After Enter the details, Click the ProceedButton.
j) The frame will display the overall details like Source, Destination, Travel Date, Booked
Date, Total Members, Quota and TotalFare.
k) Click the “Confirm” Button to confirm the details. Then only the Booking details will
be stored and PNR Number will begenerated

Ticket cancellation:
The Ticket Canceling is also user (Employee of Railway Dept.) side module. The user can
cancel the ticket using this module. The user should follow the steps for the ticketCancel.
 a) Enter the PNR Number in the Textbox and ClickFind.
b) It will show the details like Train No., Train Name, Booked Date, Travel Date,Source,
Destination, Class, Quota, Total Fare, Kms in theFrame.
c) It also shows the passenger names, Age, Sex, Berth, Class, Fare and status in the flexgrid.
d) Click the Name in the flex grid which you want to cancel and where the status is“Booked”.
e) Click the “Cancel” Button to cancel theticket.

 Membership Module

the system shall allow station master and branch manager and branch supervisor of the
particular station to access this module.
the system shall record the following data for the customer:
a. first name
b. last name
c. addresscity
d. state
e. country

 Train Module

the system shall allow head office personnel only to add and update new train timing details
in the system. Head office personnel shall login first to access this module.
the system shall record the following details of each train
f. TrainName
b. Traintimings
c. Train description, duration on eachstation
d. Trainstations

 Pricing Module

the system shall allow branch manager and branch supervisor of the branch only to access
this module.
the system shall limit access to branch level only.
the system shall allow branch manager to add pricing tables and deleting pricing
tables. the prising is based on adult or children or senior citizen parameters.

 Availability Module

the system shall allow branch manager and branch supervisor of the branch only to access
this module.
the system shall limit access to branch level only.
the system shall allow branch manager to add availability tables and deleting availability
tables.
the availability is based on adult or children or senior citizen parameters.

 Report Module

The system shall generate report based on account type.
a. BranchReport
b. Head OfficeReport
 c. Customer Refund List

 Access Type

access to the modules is determine by staff account type and branch office
location. types of account are as follow:
 CounterClerk
 Station Master
 Station supervisor
 Headoffice
 PersonnelTicket
 CheckerSystem
4. Administrator
5. EXTERNAL INTERFACEREQUIREMENT

5.1 USERINTERFACES
keyboard,mouse,printer

5.2 HARDWAREINTERFACES
SERVER SIDE
 Operating System: Windows7
 Processor:Inteli5
 Memory: 4GB
 Hard Drive Capacity:750GB

CLIENT SIDE
 Operating System: Windows XP, Windows Vista orWindows7
 Browser: Internet Explorer and above. Mozilla or GoogleChrome.
 Memory:512MB

5.3 SOFTWAREINTERFACES
Database
Microsoft office Access
Web Server
Apache server version 2.2.6
Programing Languages
.net
Java
5.4 COMMUNICATIONINTERFACES
Dial Up Modem
Broadband Internet
6. NON-FUNCTIONALREQUIREMENTS

6.1 PERFORMANCEREQUIREMENTS
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.
PE-4: The system shall display confirmation messages to users within 4 seconds after the user submits
information to the system.
variety of compartments based on comfort:
1. AC firstclass
2. ACsleeper
3. First class
4. AC threetier
5. sleeper class
6. Ordinary chaircar
types of concerns and complexities:
1. 44 types ofquotas
2. 8 types oftrains
3. 9 types of classes
4. 162 types of concessions
5. 127 types ofbogies

6.2 SAFETYREQUIREMENTS
No safety requirements have beenidentified.

6.3 SECURITYREQUIREMENTS
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.

6.4 DESIGNCONSTRAINT
The system shall be web based system that runs on different type of browsers such asInternet
Explorer,Mozilla,Googlechrome.
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. An SRS (Software Requirements Analysis and Specification) should identify and specify all
such constraints.
Standard Compliance: - This specifies the requirements for the standards the system must follow.
The standards may include the report format and accounting properties.
Hardware Limitations :- The software may have to operate on some existing or predetermined
hardware, thus imposing restrictions on the design. Hardware limitations can include the types of
machines to be used, operating system available on the system, languages supported and limits on
primary and secondary storage.
Reliability and Fault Tolerance: - Fault tolerance requirements can place a major constraint on
how the system is to be designed. Fault tolerance requirements often make the system more complex
and expensive. Requirements about system behavior in the face of certain kinds of faults are
specified. Recovery requirements are often an integral part here, detailing what the system should do
I some failure occurs to ensure certain properties. Reliability requirements are very important for
criticalapplications.
Security: - Security requirements are particularly significant in defence systems and database
systems. They place restrictions on the use of certain commands, control access to data, provide
different kinds of access requirements for different people, require the use of passwords and
cryptography techniques and maintain a log of activities in the system.