Project Review 3 –

TEAM MEMBERS:

SIDDHARTH KUMAR – 20MIS0087

MOHAMMED RAYAN- 20MIS0098
M. N. V. NIKITH – 20MIS0113
DEVANGANA V – 20MIS0125
ADITYA SINHA – 20MIS0343

FACULTY INCHARGE: Dr. ASHA N Ma’am

SLOT: G2
 VISION DOCUMENT
ONLINE RAILWAY RESERVATION SYSTEM

1. INTRODUCTION:

This vision document defines the high-level scope and purpose of our project on advanced
railway reservation system. A clear statement of the problem, proposed solution, and the
high-level features of a product helps establish expectations and reduce risks. This topic
provides an outline of potential content for a vision document.

1.1 Purpose of this Vision Document:

The railway reservation system facilitates the passengers to enquire about the trains
available on the basis of source and destination, booking and cancellation of tickets,
enquire about the status of the booked ticket, etc. The aim of case study is to design and
develop a database maintaining the records of different trains, train status, and
passengers. The record of a train includes its number, name, source, destination, and
days on which it is available, whereas record of train status includes dates for which
tickets can be booked, total number of seats available, and number of seats already
booked.

The main purpose of this system is to

Creating reservation
Cancel reservation
View reservation status
View train schedule
Generating reports
Update train schedule
Update reservation details
Advance search options
Disruption management
Profile management

1.2 Product overview:

The Seats of Reservation cannot be more than the seats of Train at that date. This is a
constraint that has to be followed by the Admin when he/she creates the Reservation.
For that purpose he/she wants to check the seats remaining present in the Train. The
scope of this system in creating Reservation is that, from any Railway Station we can
 Create Reservation, which is updated automatically in all the stations. Hence, there is no
confusion to the Reservation admin in all the stations to create the Reservation. This can
be possible by maintaining a Global Database. Admin present at different stations can
access the global database and the admin can easily understand the remaining
reservation seats. It provides the ability to create reservations from different places for a
train. The system is so secured and the admin and manager utilize it. Nobody is able to
access the system without his or her permission because of providing a login facility to
the system. The password is in the form of cipher text by using cryptography
technology, so it cannot be hacked by any person. The global database can pass through
the network in order to be utilized by managers or admin at different places. So, we want
to provide network security because of the data not hacked by the other persons when it
is going through network cables. This network security is provided by the cryptography
technology.

1.3 References:

1.https://www.altexsoft.com/blog/railway-reservation-system/
2.https://www.researchgate.net/publication/271604100_Railway_Online_Booking_Syste
m_Design_and_Implementation
3.http://www.indianrail.gov.in/
4. Microsoft PowerPoint Presentation
5. StarUML

2. USER DESCRIPTION:

2.1 User/Market Demographics :

While IRCTC remains the only government-run ticketing platform for the railways,
private players began entering the online train ticket booking business in India around
the early 2000s. Train ticketing became one of the fastest-growing verticals within the
online ticketing market. Makemytrip was one of the early entrants (founded in 2007) in
the online ticket booking sphere which not only offered services for railways but also
flight, hotel and bus booking catering both domestic and international markets.
Similarly, Goibibo came on the scene in 2007 with flights and hotel bookings, but soon
expanded to train tickets. Another player, RailYatri launched its operations in 2011 as
the India online train ticket booking market grew rapidly in the years between 2006 and
2016. In 2017, Paytm was the first horizontal e commerce major to enter the travel
business, a domain that has hitherto been dominated by vertical players. The company’s
online rail booking platform at one point was doing more bookings than any other
private online B2C player in India. Paytm told Inc42 that its strength lies in keeping
things simple and convenient for customers. “We have closely analyzed user behavior
and researched the key pain points faced by train travellers. Our train booking
experience has been tailor-made to address these pain points and provide a delightful
experience to our customers. This has helped Paytm organically grow its train booking
volume month-on-month since its launch 3 years ago and today we boast of a loyal
customer base of 7 M users that have booked a train ticket on Paytm.”

2.2 User Profile :

a. Passengers
Description Primary end user of
NTES,IVRS,PRS
Type This can be a casual or novice user
and uses the application to book
tickets for their purpose
Responsibilities Uses the application to book tickets
anytime to travel to different places
through trains
Success Criteria The success is defined as the
customers continuing to use our
system.
Involvement We will have sample customers to
evaluate our system which will guide
our vision.
Deliverables None
Comments/Issues None

b. Check-in staff
Description person in the management who
checks for the details of the
passengers
Type This a specific user who would be
experienced in working with the
application
Responsibilities Provides services to the passengers
and verifies the details of the
passengers.
Success Criteria The success is defined as the
customers continuing to use our
system.
Involvement We will have sample customers to
evaluate our system which will guide
our vision.
Deliverables None
Comments/Issues None

c. Travel Agent
Description Primary end user of
NTES,IVRS,PRS
Type This can be a casual user and uses the
application to book bulk tickets for
their customers
Responsibilities Uses the application to book bulk
tickets for train anytime
Success Criteria The success is defined as the
customers continuing to use our
system
Involvement We will have sample customers to
evaluate our system which will guide
our vision.
Deliverables None
Comments/Issues None

d. Railway Operation
Description Individual stations or multi-station
systems, including management
and staff, with responsibility for
building and operating the railway
Type This can be a proficient user who
uses the application to check the
departure and arrival time of trains
and for verification.
Responsibilities Uses the application to feed in the
information about the availability of
time to travel and check passenger
details
Success Criteria The success is defined as the
customers continuing to use our
system
 Involvement We will have sample customers to
evaluate our system which will guide
our vision.
Deliverables None
Comments/Issues None

2.3 User Environment:

Nowadays the passenger can book the railway tickets online more easily than waiting in
long queues to obtain the ticket. This system should include the name of the train,
source, destination, time, date of arrival or departure etc.
A railway system needs to model the following:
Seats availability: The users through the use of this system can check whether the seats
are available in the particular train to travel.
Train tickets: The users can access their train tickets through the online mode through
the use of this application.
Stations: This application can also contain the details of the various stations from the
source to the destination of the passenger.
Trains: The trains will be having the name and the id number.
Train schedules: Even the schedules of different trains can be mentioned through this
application.
Time in and time out: For each train at every station there is a time in or time out time. It
indicates that passengers should get in and get out of the train only within that particular
duration of time. For this we have to maintain many records given below
• Train route
• Departure time
• Arrival time
• Train type(i.e. coach no)
• Fare
When we want to travel we reserve seat, for this we have to fill the reservation form
which includes entries such as train no. , name, departure time, arrival time, route, train
type. So we should gather all the information regarding all these.
2.4 Key user needs:

Need Priority Concerns Current Proposed

solutions Solution
Flexibility High Ability to It is not The ability
and novice or possible to to book or
efficiency casual cancel cancel
of use users to their their
book or tickets and tickets by
cancel has a providing
their complex them
tickets design aesthetic
easily and
minimal
design
Online High Time and Old system Online
payment others is not payment
having options
more consume
features times to be
and slow a greater
time in extent for
payment passengers
Sending High Efficiency Default Correct
automatic and Server in time we
messages reduces notification can send
anxiety is not automatic
effective messages

2.5 Alternatives and competitors:

• Numetric
• Versatrans
• Inrix
• PTV vissim
• Routefounder pro
• Kangrouter
• Ticketsimply
• Simwalk airport
 • Turn It ride
• Expert dispatch system
• Compuweigh
• GIS system
• Rail connect 360
• GTFS manager
• EDU log
• Ridescheduler
• True Delta
• Amadeus Total Rail
• Bus planner

3. Product Overview:

3.1 Product Perspective:

3.2 Product Position Statement:

The railway reservation system facilitates the passengers to enquiry about the trains
available on the basis of source and destination, booking and cancellation of tickets,
enquiry about the status of the booked ticket, etc. The aim of case study is to design and
develop a data base maintaining records of different trains, train status and passengers.
This project contains introduction to the railways reservation system. It is the
computerized system of reserving the seats of train seats in advance. It is mainly used for
a long route. Online reservation has made the process for the reservation of seats very
much easier than ever before. The Target User for this railway reservation system is
those customer how want to book their tickets.
Before making this a real time running online reservation system, old system suffered
from many of the DRAWBACKS, such as:
• The existing system is highly manual involving a lot of paperwork and calculation and
therefore may be erroneous. This has led to inconsistency and inaccuracy in the
maintenance of data.
• The data, which is stored on the paper only, may be lost, stolen or destroyed due to any
natural calamity of fire or water.
• Existing system is sluggish and consumes a lot of time, resources etc. causing
inconvenience to customers and staff.
• Due to manual working, it is difficult to add, delete, update, or view the data.
• Since the number of passengers has increased to an uncertain multiple, it is very
difficult to maintain or retrieve detailed records of passengers.
• A Railway has many offices around the world, an absence of link between them all
causes a lack of miscommunication and incoordination.
Hence, this Railway reservation system is proposed, with following benefits:
• Computerization of the reservation system will reduce a lot of daily paperwork and
hence load on the staff of the admin department.
• Machine does all the calculations. Hence, chances of error are low.
• Reservation, Cancellation or updating lists of Tickets can easily be maintained and
retrieved and any required additions, deletion or updating can easily be performed.
• This system provides User Name-Password validation, hence unauthorized access is
prevented.

3.3 Summary of capabilities:

Customer benefit Supporting features

To create a new user account Login

To check the ticket details Individual database

Regular ticket update Passenger details

To give the idea of the features to be added Feedback

To rate the system Rate

 3.4 Assumptions and Dependencies:
Every system requires some certain parameters to work, to work as per the requirement,
our system also requires some parameters, and we assume them as fulfilled before using
this system, which is as:
• Booking agent/ user will have his/ her own username registered before booking any
ticket; else, they’ll have to register themselves on our website.
• This software needs a booking agent/ user to have complete knowledge of the railway
reservation system and its working.

3.5 Cost and Pricing:

The license for the software is created as soon as the users create their own user id. The
account can be maintained for the period of time based on the package of premium that
the user paid, and for that particular period of time the software is licensed and the
security of each and every activity is maintained perfectly and this software does not
require any money for the installation of this software.

4. Feature Attributes:

DESCRIPTION
Status Proposed Under discussion but have not been reviewed and
accepted by the official channel.
Benefits Important Features are important to the effectiveness and efficiency
of the system. The functions cannot be easily provided in
some other way. Omitting an important feature might
affect customer or user satisfaction, or even revenue.
However, the release will not be delayed because an
important feature is not included.
Priority Critical The priority of the system is to be put at highest level
looking at the complexity as well as demand.
Effort High Some features require more time and resources than
others. Use the estimate in managing scope and
determining development priority.
Risk Low The development team establishes risk levels, based on
the probability that the project will experience
undesirable events, such as cost overruns, schedule
delays, or even cancellation.
Stability High The analyst and development team establish feature
stability based on the probability that the feature will
change or the team's understanding of the feature will
change. Stability is used to help establish development
priorities and determine those items for which additional
elicitation is the appropriate next action.
Target Version 96.0.4664.45 Teams record the earliest intended product version that
release will include the feature. Only features whose status is
set to "incorporated" and whose target release is defined
will be implemented. With scope management, the
target release version number can be increased.
Assigned to M N V Nikith
Team members -
Siddharth Kumar
Md. Rayan
Devangana V
Aditya Sinha ----------------
Reason Customer interview-stating
the high need of the features
mentioned and more
refinement and advancement
of the existing system.

5. PRODUCT FEATURES:
This project is mainly intended for two types of audiences. One is the customer or the end
user and the other is the administrator of the website. Some of the major functions of the
product can be categorized under two different categories that are for the administrator and
the user.

5.1 Customer / End user activities:

Users 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 can be relatively simple
to use. The scope of this project encompasses:
Search:
This function allows the user to search for a train that is available between two travel
cities namely “Departure City” and “Arrival City” as desired by the traveler. The System
initially prompts the agent for these two column values, the date of the journey,
preferred time slot and the number of passengers. It then displays a list of trains
available with different classes.

Selection:
The function allows a particular train to be selected from the displayed list. All the
details of the train are as shown:
• Train Number.
• Date, Time and place of departure.
• Train Duration
• Fair per head
• Number of stoppages – 0, 1, 2…

Review:
If the seats are available, the software prompts for the booking of the train. The train
information is shown. The total fare including taxes is shown and train details are
reviewed before final payment

Travel Information:
This system asks for details of all the passengers before the booking confirmation.
Hence, lesser cases of seat issues.

Payment:
It requires details of credit/ debit card of the person to make payment and reserve the
required seat, Details such as:
• Card Number
• Card Type
• CVV Number
• Expiry Date
• Name on card

Cancellation:
System also allows cancellation of existing reservations, making seats unreserved for
others to book and refunding the money back to the accounts of users cancelling the
tickets.

5.2 Administrator Activities:

Login/Logout:
The administrator has to login first in order to be able to make changes to the Railway
reservation System, by adding, deleting or modifying the data in the passenger
 reservation System database. After making the necessary changes, he then has to logout
of the system, in order to prevent misuse of the data.

Add/Modify Customer Information:

Daily the railway reservation System will have many customers registering with the
website and many of them unsubscribing. Only the administrator will have the sole
rights to modify the database accordingly.

Add/Modify Train Information:

The Administrator also has the sole rights to add, delete or modify the train information.
Sometimes, trains get cancelled for some reason, so such trains would be removed from
the list of trains available to the customer. Similarly, whenever any train information has
to be modified or if any new trains need to be added to the database, these operations are
performed by the administrator.

Cancellation of Reservations:
Sometimes, after making a reservation, a customer might cancel the reservation he has
made. So, the administrator also handles such special situations and sends the customer
an email confirmation after deleting the specific transaction.

Email confirmations:
Whenever a customer makes or cancels a reservation, the administrator is responsible for
sending confirmation emails to the customer, confirming the transaction

6. EXEMPARY USE CASES:

Use Case Name Login

Brief Description This use case allows the user to login into the system
to access relevant functions in according to the user’s
role.
Basic Flow 1. System displays login page.
2. User enter his credentials.
3. System redirect the user into the homepage.
Alternative Flows The user entered login credentials are invalid. The
 user can re-enter the login credentials.
Preconditions User must have an registered account.
Post Conditions System redirect the homepage.

Use Case Name Logout

Brief Description User can logout from the system by using this use
case.
Basic Flow 1. User can logout by clicking the logout button.
2. System redirect the login page.
Alternative Flows If in the basic flow, if the internet connection is lost
user must refresh the page again.
Preconditions The user should have been logged in already.
Post Conditions System display the login page.

Use Case Name Book tickets

Brief Description This use case allows the user to book tickets.
Basic Flow 1. Plan journey by giving from station to to
station.
2. Give preference like window,middle or first
seat.
3. Proceed to pay the amount of ticket.
4. Finally ticket registered.
Alternative Flows If tickets are housefull for that particular train then the
registration process will stopped. We can choose
other train.
Preconditions User must have an account.
Post Conditions E-ticket sent to the passenger mobile number.
7. OTHER PRODUCT REQUIREMENTS:

7.1 Non-Functional Requirements:

7.1.1 External Interface Requirements

• The system should have a customer user interface.
• The system should have an administrator user interface.
• Customer user interface should have a graphical user interface (GUI).
• Administrator user interface should have a GUI.

7.1.2 Performance Requirements

System should be able to handle 1000 transactions per second.

7.1.3 Maintainability Requirements

• User should be displayed acceptance message within 5 seconds, when he/she
submits entered data to the system.
• Warning messages about entrance data out of defined standards must remain on the
screen for 3 seconds. 8.4 Security Requirements
• System should have an Authentication and Authorization System (AAS) for logins.
• System should grant administrative privileges only to the one who logins with
predefined administrative username and password.
• System should allow administrator to change his/her system generated password as
he/she wishes.
• System should allow administrator to login with customized password.
• System should block access to one who fails to login three time in a row.
• System should guarantee the security of communication channel.
• Customized password should be at least 8 characters.
• Customized password should contain both letters and numbers.

7.2 Functional Requirements:

7.2.1 User Accounts

The passenger, who will henceforth be called the ‘user’, will be presented with 3
choices by the Management system, as the first step in the interaction between them.
A user can choose one of these and his choice would be governed by whether he is a
guest or a registered user and whether he wants to check the availability of tickets or
also block/buy them. The terms ‘registered user’ and ‘guest’ are described below.
• A user who has travelled by the railway earlier would have been given a user id
and a password.
• A new user, on the other hand, would either have to register himself with the system
by providing personal information or log into the system as a guest.
• In case of ‘a’, the new user becomes a registered user. In case of ‘b’, the new user
would remain a guest.
• A guest can only check the availability of tickets and cannot block or buy tickets.
• But a registered user can also act as a guest if he only wants to check the
availability of tickets. ‘Availability of tickets’ always refers to viewing the train
schedule for given days, the price of tickets and any discount offers.
• The system shall present the user with an option to exit from the system at any time
during the following processes.

7.2.2 Registration and creation of user profile

The system shall require a user to register, in order to carry out any transactions with
it except for checking the availability of tickets. It will ask the user for the following
information at the least – a user id, a password, first name, last name, address, phone
number, email address, sex, age, preferred credit card number. The system will
automatically create a ‘sky miles’ field and initialize it to zero in the user’s profile.

7.2.3 Checking Availability

After logging in a user (either a registered user or a guest), the system shall request
him to enter the following details – origin city and destination city. “City’ is a generic
term and refers to a city or town as the case may be. The origin and destination cities
would be entered as text.
In case there are more than two cities with same name as entered by the user, the
system shall list all of them and ask the user to select one of them. In case, either the
origin or destination cities are not listed in database as being directly serviced by the
airline, the system shall suggest the nearest city to which service is available,
including the distance of the destination city from this nearest city.

7.2.4 Making Reservations/Blocking/Confirmation

After having taken the user through the step, Checking Availability, The system will
now ask the user if he wishes to block/buy the ticket. If yes, and if the user has been a
guest, he will have to first register and become a registered user and then log onto the
system.
If the user is already a registered user, and if he has logged on already, he can
block/buy the ticket, but if he has been acting as a guest, he will have to log on.
Having ensured that the user is logged on validly, the system compares the departure
date with the system date. If the departure date falls within 2 weeks of the system
date, the system informs the user that he has no option to block the ticket and asks
him if he would like to buy it. If the difference between the departure date and system
date is more than 2 weeks, the system asks the user if he would like to block or buy
the ticket. The system informs the user that he can block the ticket at no cost now. It
also informs him that if he chooses to block the ticket, he should make a final
decision before 2 weeks of the departure date. The system shall send an email to the
user, 3 weeks before the departure date as a reminder, in case he decides to block the
ticket now.

7.2.5 Confirm Ticket

A user who has earlier blocked a ticket after going through registration, checking
availability and booking tickets is required to either confirm the ticket before two
weeks of the departure date or the ticket stands cancelled. To let the user, confirm a
ticket, the system shall first log him on and ask for his blocking number. Then it
accesses reservation schedule and removes the check mark, which so far represented
a blocked seat. The seat is now confirmed and reserved for the user.

7.2.6 Reschedule Ticket

The system shall present the user with an option to re-schedule his travel party’s trip.
In order to do this, the system first logs on the user and requests his confirmation
number. It will not allow a user to reschedule a blocked ticket but only a confirmed
ticket. Using this, it queries reservation database and presents the details of the trip to
the user, including but not limited to origin city, destination city, date of departure
and date of arrival.
The system shall now ask the user to select new dates from the calendar menu. It now
goes through the step of checking availability. In case, there are no available tickets
for the dates entered, it displays a suitable message informing him that rescheduling
to that date is not possible. In case there are tickets available, the system asks the user
to select the flight number for the trip.

7.2.7 Cancellation
The system shall also give the user an option to cancel a confirmed ticket or a
blocked ticket.
The latter case is simpler and will be dealt with first – the system shall first log on the
user and request the blocking number. Then it accesses reservation schedule and
updates it by incrementing the number of available seats by the number of people in
the user’s travel party.
It then lists the applicable rules for cancellation of tickets and depending on the
system date and the departure date, it displays the % of the amount that would be
refunded if the user cancels the ticket.
 • Update Profile
The system shall enable the user to update his profile at any time. Changes can be
made in fields including but not limited to address, phone number and preferred
credit card number.
• View Ticket Status
The system shall allow a user to view all information about his trip. After logging
him on, it asks for his blocking number or his confirmation number. It accesses
reservation database and retrieves the details of the trip and presents them to the user
in a convenient format, including any last minute changes to the train timings etc.
Such changes will be highlighted.
• Query Train Details
The system shall allow any user to access the details about the arrival and departure
times of a train by requesting the user to input the train number and date. The system
accesses book schedule and presents the time of arrival and departure.

8. Document Requirements:

8.1 User Manual

The User Manual explains us the step- by -step procedure to set up and use the Train
Reservation System web application. The instructions on how to book a train will be
provided on the website for inexperienced users.
The User Manual shall include:
• Minimum System Requirements
• Installation of the software in different places
• Logging In
• Logging Off
• All System Features
• Customer Support Information

8.2 Online Help

Online Help shall be available to the user for each system function. Each topic covered
in the User Manual shall also be available through the online help.

8.3 Installation Guides, Configuration and Readme file

This section describes the required software and hardware for the Railway Reservation
System project.
The Installation Guide for the server portion shall include:
• Minimum System Requirements
• Installation Instructions
• Parameters
 • How to initialize the usage
• Database
• How to Retain the Existing data
• Customer Support Information
The Read Me File shall be available for display following installation. The Read Me file
will also reside on disk and be available for viewing at any time by the user.
The Read- Me File shall include:
• New release features
• Known bugs and workarounds.

9. GLOSSARY:

WORD MEANING
NTES National Train Enquiry System
IVRS Interactive Voice Response system
PRS passenger reservation system
Fare Money realized by the railways from
transportation of persons.
Rate Price fixed by the tariff for the conveyance
of a unit of parcels, luggage and goods
End User the person who actually uses the service.
Capital-at-charge Book value of the capital assets of the
Railways.
Gross earnings The true earnings in an accounting period
whether actually realized or not.
On cost Expenditure incurred on jobs which cannot
be charged direct to the cost of articles
manufactured or work done.
Net revenue Difference between the gross earnings and
the working expenses after the payment of
dividend to General Revenues, payment to
worked lines and other net miscellaneous
expenditure.
Revenue earning traffic Traffic conveyed by rail and for which
commercial tariffs are applied i.e., for
transportation of which the railway is paid
by either the consignor or the consignee.
Revenue reserve fund This Fund consists of appropriation out of
the surplus of net revenue receipts of
 railways and is utilized primarily for
maintaining the agreed payments to
general revenues and for making up any
deficit in the working of the railways.
The volume of traffic moving between any
Density two points on the railway system. It is
expressed in terms of passenger kilometres
or net tonne kilometres and train
kilometres per running track kilometre or
route kilometre.
Net load – The weight of passengers, baggage or
goods conveyed by a vehicle (coach,
wagon, etc.,) or by a group of vehicles
(trains).

****************

THANK YOU!
End of Review 3