E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

E-TICKETING
AIM: To create an automated system to perform E-ticketing.

PROBLEM STATEMENT: Our project is carried out to develop software for online
Railway Reservation System. This system has various options like reservation, cancellation
and to view details about available seats. Our project mainly simulates the role of a Railway
ticket booking officer, in a computerized way. The reservation option enables a person to
reserve for a ticket at their home itself. All he/ she has to do is to just login and enter the
required details. After this the reservation database is updated with the person details, train
name and also the source and destination place. The cancellation option enables the
passenger to cancel the tickets that has been already booked by him/her. The availability
option prompts the person to enter train number, train name and date of travel. After this
the availability database is accessed and available positions are produced

SOFTWARE REQUIREMENT SPECIFICATION

1.0 INTRODUCTION
The manual system of ticket reservation takes more time and the number of reservations
per day is limited. To increase the efficiency of the process, we go for online ticket
reservation system. This system supports online ticket booking.

1.1 PURPOSE
If the entire process of reservation is done in a manual manner then it would takes several
months for reservation to reach the applicant. Considering the fact that the number of
passenger is increasing every year, an Automated System becomes essential to meet the
demand. So this system uses several programming and database techniques to elucidate the
work involved in this process. As this is a matter of National Security, the system has been
carefully verified and validated in order to satisfy it.

1.2 SCOPE
• The System provides an online interface to the user where they can fill in their
personal details and submit the necessary documents (may be by scanning).
• The authority concerned with the issue of railway can use this system to reduce his
workload and process the application in a speedy manner.
• Provide a communication platform between the passenger and the administrator.
• Passenger will come to know their status of application and the date in which they
must subject themselves for manual document verification.

1
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

Product Functions

2.1 Administrators
 Admin should be able to add or delete shows from the site.
 Admin can reject the user if he/she does not accept terms and conditions.

2..2 Users
 Account: Members are given a provision to check their account’s information and change it.
 Availability: User can search presently available shows or upcoming shows in different theatres.
 Booking: User can book required number of seats by selecting empty seats and then pay for
them.
 Transaction: To book the seats they user must pay the total amount including taxes and other
charges through online transactions like net banking, or debit/credit cards, or through UPIs. A
transaction id is created and given to the user for future purposes.
 Ticketing: A ticket is produced with seat numbers, time and place of show on it and also a QR
code.

 Cancellation: User also may unbook the seats and get a 50% cashback excluding taxes.

2.3 User Characteristics

There are different kinds of users that will be interacting with the system. The intended
users of the software are as follows:
 User 1: An inexperienced customer. This user has little or no experience with electronic means of
booking a ticket or not a frequent user of the product. The user will find a friendly portal to use and
an easy way to book tickets.
 User 2: An experienced customer. The user has used the portal several times and does most of
his/her bookings though online platform. There is only little help session that too at the beginning of
the session thus making the booking procedure easy and faster.
 Maintenance Personnel: An administrator of the system should have more knowledge of internal
modules of the system and are able to rectify small problems that may arise due to disk crashes,
power failures and other catastrophes. Friendly user interface, online help and user guide must be
sufficient to educate the users on how to use this product without any problems or difficulties.

2.4 Constraint
The major constraints that the project has are as follows:
 The information of all users and shows must be stored in a database that is accessible by the
website.
 The number of invalid pin entries attempted must not exceed five. After five unsuccessful login
attempts, the user can create a new password by clicking on ‘Forgot password’ and confirm the mail
sent to their respected e-mail id.
 The transaction must be successful for the seats to be booked.
 User can access the portal from any device which has good internet connection and internet
browsing capacities.

2
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

 SQL used will be Oracle 11g.

System Features

3.1 Functional requirements

 Registration: If customer wants to book some seats, then he/she must be registered,
unregistered user can’t book the seats.
 Login: Customer logins to the system by entering valid email id and password for the seats to be
booked.
 Search: The user can search their required shows and check for available seats at different
theatres.
 Select: User is allowed to select required number of seats at liked places.
 Payment: Payment is done through net banking or debit/credit cards or through UPI. The seats
will be booked and blocked only after a successful payment.
 Receipt Generation: A unique transaction id is generated for future references.
 Ticket Generation: A ticket is produced with seat numbers, time and place of show on it and also
a QR code.
 Error handling: If any of the above validation/sequencing flow does not hold true, appropriate
error messages will be prompted to the user for doing the needful.

Non-functional Requirements

4.1 Performance Requirements

The following list provides a brief summary of the performance requirements for the
software:
4.1.1 Capacity
The booking portal shall provide customers a 24-hour service.
4.1.2 Dynamic requirements
The initial loading time must not exceed 4 secs under normal server workload and 7
secs under peak workload. Registration and login need password verification which
should not exceed 2 secs to login. Time limit to search a show must not cross 3 secs. For
the display of available seats server takes a maximum time of 4 secs. For payment
render i.e., selection of mode of payment it takes 3-4 secs. For the complete transaction
to happen it takes a maximum time of 8 secs and to produce a transaction receipt with a
unique transaction id it may take 3-4 secs. And finally, to generate a ticket it should not
exceed 5 secs under a normal load and 7 secs under a heavy load.
4.1.3 Quality

The primary objective is to produce quality software. As the quality of a piece of

software is difficult to measure quantitatively, the following guidelines will be used
when judging the quality of the software:

3
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

  Consistency – All code will be consistent with respect to the style. (This is implied
when adhering to the standard).
 Test cases – All functionality will be thoroughly tested

4.2 Software System Attributes

5.1 Reliability
 The system provides storage of all databases on redundant computers with automatic
switchover.
 The reliability of the overall program depends on the reliability of the separate/distinct
components. The main pillar of reliability of the system is the backup of the database which is
continuously maintained and updated/revised to reflect the most recent changes.

5.2 Availability
 The system should be available at all times, the meaning user can access it using a web browser,
only restricted/ prohibited by the downtime/ rest of the server on which the system runs.

  In case of a hardware failure or database corruption, a replacement page will be shown. Also, in
case of a hardware failure or database corruption/ fraud, backups of the database should be
retrieved/ obtained from the server and saved by the administrator. Then the service will be
restarted. It means 24×7 availability.

5.2.3 Security
  The system uses SSL (secured socket layer) in all transactions that include any confidential
customer information.

 The system must automatically log out all customers 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 backend servers shall only be accessible to authenticated administers.

 Sensitive data will be encrypted before being sent over insecure connections like the internet.

5.2.4 Maintainability
A commercial/saleable 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
program will be done. Furthermore, the software design is being done with modularity
in mind so that Maintainability can be done efficiently.

(l) USE-CASE DIAGRAM

A use case diagram is used to represent the dynamic behavior of a system. It
encapsulates the system's functionality by incorporating use cases, actors, and their
relationships. It models the tasks, services, and functions required by a
system/subsystem of an application. It depicts the high-level functionality of a system
and also tells how the user handles a system.

The online ticket reservation system uses the following use cases:

4
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

1. Request for seat availability

2. make Reservation
3. Cancellation
4. Check status
5. Print ticket

ACTORS INVOLVED:
1) System
2) Passenger

USE-CASE NAME: REQUEST FOR SEAT AVAILABILITY

The passenger can view the train available in the database for deciding which
train ticket he wishes to reserve. The passenger can search the train information based on
journey date, train type and reservation type. The passenger can view the details of flights
such as, train number, source station, destination station, arrival time, departure time, fare
and number of seats available.

USE-CASE NAME: MAKERESERVATION

The user is allowed to reserve a ticket on train as he/she requires on the particular
date and time. The user has to provide details such as name, train number, date of travel,
source station, destination station, proof name and money transaction details .

USE-CASE NAME: PRINT TICKET

The user after booking a ticket can print a copy of the ticket reserved. The user
has to provide the details about ticket number for searching in the database and passenger
name for confirming passenger identity.

USE-CASE NAME: CANCEL TICKET

A passenger can decide to cancel a ticket after the ticket is booked. The passenger
has to provide details about ticket for searching and details about him for confirmation of
identity.

USE-CASE NAME: CHECK STATUS

The passenger can view the status of the reserved tickets. So the passenger can
confirm his/her travel.

5
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

(ll) CLASS DIAGRAM:

The class diagram, also referred to as object modeling is the main static analysis
diagram. The main task of object modeling is to graphically show what each object will
do in the problem domain. The problem domain describes the structure and the
relationships among objects.

the online ticket reservation system makes use of the following classes:
1. ticketReservation
2. trainInfo
3. passengerInfo
4. seatAvailStatus

1. TICKETRESERVATION
It consists of twelve attributes and two operations. It records the details of every
ticket booked such as ticket number, passenger ID, source and destination station and etc.

2. TRAININFO
It stores the details of all the trains such as train number, train name, speed, source
and destination stations, etc.

3. PASSENGERINFO
It consists of seven attributes and three operations. This class is used to store

6
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

passenger details such as, passenger name, age, address and etc.

4. SEATAVAILSTATUS
This class is used to update the number of seats available for a particular train by
using updateStatus() operation.

CLASS DIAGRAM FOR E-TICKETING

(lll)SEQUENCE DIAGRAM

A sequence diagram in Unified Modeling Language(UML) is a kind of interaction

diagram that shows how processes operate with one another and in what order.It is a
construct of a message Sequence Chart.there are two dimensions

7
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

 Vertical dimension-represent time.

 Horizontal dimension-represent different objects.

This sequence diagram describes the sequence of steps to show

• Passenger are used to login the form. And then its verify the username and
password.
• If the password and username are correct then applicants are used to login the
filling details.
• Passenger are used to selecting the train and book the tickets.
• Now the E-Ticketing DataBase verify the filling Details.
• And then the E-Ticketing DataBase displays the ticket information.
• Incase of any sudden change of the plan, the applicant can cancel the ticket.

SEQUENCE DIAGRAM

(iv) Collaboration Diagram:

8
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

A collaboration diagram ,also called a communication diagram or interaction

diagram.A sophisticated modelling tool can easily convert a collaboration into a
sequence diagram and the vice versa. A collaboration diagram resembles a
flowchart that potrays the roles,functionality and behaviour of individual objects
as well as the overall operation of the system in real time

COLLABRATION DIAGRAM

(v)ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-
by-step workflows of components in a system. An activity diagram shows the overall
flow of control. An activity is shown as an rounded box containing the name of the
operation.

This activity diagram describes the behaviour of the system.

9
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

• First state is login where the passenger login to the E-Ticketing system.
• The next state is filling details the passenger are used to fill the form.
• Then passenger used to selecting the flight.
• The passenger appears for book ticket and search details from E-Ticketing DataBase.

10
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

11
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

12
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

13
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

(vi)COMPONENT DIAGRAM

A component diagram is used to break down a large object-oriented system

into the smaller components, so as to make them more manageable. It models the
physical view of a system such as executables, files, libraries, etc. that resides within the
node.

It visualizes the relationships as well as the organization between the components

present in the system. It helps in forming an executable system. A component is a single
unit of the system, which is replaceable and executable. The implementation details of a
component are hidden, and it necessitates an interface to execute a function. It is like a
black box whose behavior is explained by the provided and required interfaces.

14
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

(vii) State chart Diagram

Statechart diagram describes the flow of control from one state to another state.
States are defined as a condition in which an object exists and it changes when some
event is triggered. The most important purpose of Statechart diagram is to model
lifetime of an object from creation to termination.
Statechart diagrams are also used for forward and reverse engineering of a system.
However, the main purpose is to model the reactive system.
Following are the main purposes of using Statechart diagrams −
 To model the dynamic aspect of a system.
 To model the life time of a reactive system.
 To describe different states of an object during its life time.
 Define a state machine to model the states of an object.

15
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

16
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

TEST CASES

Test Summa Pre- Post- Execution Steps Expecte

Cases ry condition condition d
Output
TC-1 To URL Successful  Open the passed
verify http:// login of the browser
for the www.railtic user  Enter the test
login ket.co.in URL
for the  Click on “GO”
user button
 Enter the
Username.
 Enter the
password.
TC-2 To Trains slots  After login passed
verify Start & are enter enter
the destination displayed date in format
invalid along with DD/MM/YYYY .
data/ date and  Enter the
empty time must starting and
data be entered destination
field points.

TC-3 To Enter the Seats  Login

verify no.of availability  Start &
the persons is Destination
Ticket Boarding displayed. details.
Availabi should be  Ticket Details
lity enterd.
TC-4 Reserva Personal Tickets passed
tion details must be Login
Form should be booked  Login
entered and  Start &
database Destination
must be details.
uploaded  Details
Login

17
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

Start & Destination

details.

Ticket Details
Start & Destination
details.

Ticket Details
Login

Start
Ticket Details
TC-5 Cancell Ticket Ticket must  Login. passed
ation number be  Start &
Form were cancelled Destination
entered and details.
database  Details
must be
Uploaded
6.0 RISK MANAGEMENT
INTRODUCTION
Railways are regarded as an economic, efficient, environmentally friendly and very safe
mode of transport. Risk, in the railroad sector, can be defined as relating to accidents and
events that lead to injury to passengers and employees. For the national risk assessment
model, the definition of a generic railway system, technical specifications and operating
systems is very important and must be considered.
Risk management process

At the broadest level, risk management is a system of people, processes and technology that
enables an organization to establish objectives in line with values and risks.

A successful risk assessment program must meet legal, contractual, internal, social and
ethical goals, as well as monitor new technology-related regulations. By focusing attention on
risk and committing the necessary resources to control and mitigate risk, a business will
protect itself from uncertainty, reduce costs and increase the likelihood of business continuity
and success.
Three important steps of the risk management process are risk identification, risk analysis and
assessment, and risk mitigation and monitoring.

Types of Risks

18
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

The three main aspects of the concept of railway system safety risk are:

(1) the system of risk is not the absence of a system, safety.

(2) the system of risk is dynamic and predictable.

(3) the system of risks presents a dynamic evolution process in an accident.

Identifying risks
Risk identification is the process of identifying and assessing threats to an organization, its
operations and its workforce. For example, risk identification may include assessing IT
security threats such as malware and ransomware, accidents, natural disasters and other
potentially harmful events that could disrupt business operations.

Risk analysis and assessment

Risk analysis involves establishing the probability that a risk event might occur and the
potential outcome of each event. Risk evaluation compares the magnitude of each risk and
ranks them according to prominence and consequence.

Risk mitigation and monitoring

Risk mitigation refers to the process of planning and developing methods and options to
reduce threats to project objectives. A project team might implement risk mitigation
strategies to identify, monitor and evaluate risks and consequences inherent to completing a
specific project, such as new product creation. Risk mitigation also includes the actions put
into place to deal with issues and effects of those issues regarding a project.

Risk management is a nonstop process that adapts and changes over time. Repeating and
continually monitoring the processes can help assure maximum coverage of known and
unknown risks.

GLOBAL SAFETY MANAGEMENT SYSTEM IN THE RAILWAY SECTOR

Safety management is an important issue in all safety critical sectors including railway industry and
regarded as an important means for improving safety culture.

Safety Management System and Lifecycle Stages of the Railway Transport System

The main lifecycle stages of a Railway Transport System focusses on generic management issues.
There should be specific elements of any developed SMS that deal with aspects of each of the
following stages of the Railway Transport System lifecycle:

 Pre-operation: Safety approval, system handover and acceptance are therefore crucial
interfaces between the developer and the duty-holder that need to be managed effectively
to ensure safety. The dutyholders need to assure themselves that the system development
has been undertaken in a manner that is consistent with the risk tolerability criteria set for
this overall Railway Transport System SMS framework.

19
 E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

 Operation: The duty holder should have the necessary arrangements for identifying the
operating requirements of the equipment, subsystems and systems it controls. They should
include requirements and constraints for their normal and degraded modes of operation.
 Maintenance: A duty holder should have adequate arrangements for implementing
planned and preventative maintenance (including, where appropriate, maintenance based
on monitoring of equipment condition) of its equipment, subsystems and systems.
 Renewal: A duty-holder should have necessary arrangements for identifying and planning
renewal work which it has to undertake for regulatory or business reasons. For example, for
maintaining performance level a duty holder may need to carry out like for like replacement
for time-expired assets, or introduce new technology to improve performance.
RISK TABLE:
Risk Title Risk Description Risk measure Probability Impact

New equipment fails New equipment(e.g.cable Programme delay cost 2 3

joins)fails when
commissioning the new
system.
Specialist staff Specialist staff required to Programme delay cost 3 4
undertake the works may be
unavailable
Freight Operations Unable to rationalise current Programme objectives 2 4
freight/passenger operations
to achieve business case
capacity
Infrastructure Existing infrastructure may Cost 1 3
damage be damaged during
construction
Signalling Records Availability of signalling Cost 5 1
records and resource to
undertake any modifications
Theft and vandalism Theft and vandalism disrupts Cost 3 2
works
Safety Case Issues associated with safety Cost 3 2
case approvals
Weather Exceptionally adverse Schedule 2 3
weather occurs
Power Capacity Inadequate capacity of Cost 4 3
power supply and local grid
network to accommodate
electrical demand
requirements of railway
station
Network Change Objectives of network Cost 2 4

20
E-TICKETING(RAILWAY TICKET SYSTEM) MGIT

change proposal to remove

existing operational slidings
7.0 SOFTWARE CONFIGURATION MANAGEMENT
The SCMP (Software Configuration management planning) process planning begins at the
early coding phases of a project. The outcome of the planning phase is the SCM plan which
might be stretched or revised during the project.
• The SCMP can follow a public standard like the IEEE 828 or organization specific standard
• It defines the types of documents to be management and a document naming.
• SCMP defines the person who will be responsible for the entire SCM process and creation
of baselines.
• Fix policies for version management & change control
• Define tools which can be used during the SCM process
• Configuration management database for recording configuration information.

21