SYSTEM ANALYSIS AND DESIGN OF

AN ONLINE TRAIN TICKETTING

SYSTEM
Published by Chijama Chidera

CONTENT
1. Introduction

2. Problem Statement

3. Proposed System

4. Requirement Analysis

4.1. Functional Requirements

4.2. Non-Functional Requirements

5. System Architecture

6. System Design

6.2. Business Process Design

7. Logic Model Design

8. Diagrams

9. References
 1. INTRODUCTION
Nigeria is a massive country with 201 million people. The primary means of transportation in
Nigeria is by road, which generates a ridiculous amount of traffic. There is a need to diversify
the means of transportation adopted in Nigeria, which brings us to the Railway. There is a dense
railway network across Nigeria, and passenger trains circulate on several routes across the
country. Still, trains' sluggish speed and the low quality of service have hindered railway
transportation from genuinely taking off. With such a vast population, there is a need to take the
train ticketing system online without eradicating the physical ticketing system. The Online Train
Ticketing System(OTTS) solves the problem of low-quality service, time wastage, inefficient
utilization of resources, overcrowding, etc. It allows the users to book or cancel local train tickets
and receive a receipt online. It also allows users to see all possible and available routes. It also
has an option to connect with google maps to view the various available stations across the
country.

2. PROBLEM STATEMENT:
People have to waste their time standing in the queue, which will eventually lead them to miss
their train, making them waste money and resources. The counter clerks are not fast enough to
handle the crowd in the station and issue tickets. The smart Ticketing machines cannot
efficiently and effectively attend to every single customer. Sometimes, it isn't possible to validate
whether a person has a ticket or not, whether the ticket is fake or not, whether it is an already
used ticket or not, especially in a crowd. To overcome such difficulties, we introduce the Online
Train Ticketing System.

3. PROPOSED SYSTEM
The main aim of the proposed system is to reform the current season ticket booking process
(Ticket) for local travelling. i.e. with the help of this application travelers will able to book
tickets through their mobile using Wi Fi connectivity and GPRS.[1]

4. REQUIREMENT ANALYSIS

4.1 Functional Requirements[2]

 Associate every online reservation with an account

 A single account cannot be associated with multiple users
 Enable users to search and find the most recent and relevant booking options.
 The system should enable users to book/pay for their tickets only in a timeboxed
manner after being added to the cart.
 Booking confirmation should be sent to the specified contact details.
  The system should consider timezone synchronisation when accepting bookings
from different timezones.
 Calculate and display accommodation charges and other utilities
 Cancel bookings.
 Display and change the records of users.

4.2 Non Functional Requirement

Security:

 System login: For the user to login, valid login details are required before
granting further access.
 Data encryption: The Online Train Ticketing System encrypts all
information before writing it into the database.
 Maximum login attempts: This system allows a maximum of five
consecutive trials.
 Transaction recordings: This system shall keep a record of all failed login
attempts with user login, terminal login and time.

Maintainability:

 Problem reduction: The payroll system’s major problem shall be resolved

in two hours maintenance window.
 Automatic backups: The Online Train Ticketing System shall perform
automatic backups once per batch.

Availability:

 System availability: It is the probability that the program is operating

according to the requirements at any point in time. The system should be
available to users from any smart device provided they meet the specified
requirements. In case of a database failure, the backup data shall be
retrieved from the server.

5. SYSTEM ARCHITECTURE
 Presentation Tier- The presentation tier is the front end layer in the 3-tier system and
consists of the user interface. This user interface is often a graphical one accessible
through a web browser or web-based application and displays content and information
useful to the end-user. This tier is built on web technologies such as HTML5, JavaScript,
CSS, or other popular web development frameworks. It communicates with other layers
through API calls.
 Application layer tier: This is the application service layer. It is the core of this three-
layer structure. This layer handles the system functions and business logic. In this layer,
the system's business logic is encapsulated, the application service interface is provided
for the user interface layer and the system modules between the function calls. The
application service layer also updates data in the database according to the top layer's
service request. The middle tier is designed to capture information like: the user's login
details, booking a ticket, cancelling a ticket, making payment, etc.

 Database tier: The database is used to hold data, including user registration information,
ticket ordering information, ticket information, payment information and all of the other

information.

Fig 1. Diagram Showcasing the Interaction between the 3 tiers in the systems
architecture
6. SYSTEM DESIGN
The system design includes business process design and database design. Database design
mainly realizes data tables and the relationship between data tables. Business process design
implements the order of various functions and links between the various parts.

6.1 Database design

In the database conceptual design phase, the entity - relationship diagram can be used to
establish the data model to form a ER graph model independent of the machine and DBMS.

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
 Train
Payment

PK train_id
PK payment_id

train_name
payment_user_id

departure_time
payment_date

departure_date
payment_amount

PK arrival_date
payment_description

train_description
make
departure_location
User
arrival_time
PK user_id
arrival_location

name
PK distance

associate
email_address

password

has telephone

PK sex

Ticket

PK ticket_id

ticket_user_id
cancel
ticket_type

date_issued

ticket_description

ticket_price

book
seat_number

Fig 2. Entity Relationship Diagram

6.2 Business process design

The following business process is made after a detailed analysis of business functions about
railway online booking system.
  Users register personal information so that they can order tickets in the
system.
 Users search for train information through the system and see whether
their route is available.
 Users order tickets on the user interface by making payment.
 The system returns the ticket(s) with the necessary information.
 Customers can select cancelling operation for some reason(s)

Fig 3. Business Process Diagram.

7. LOGIC MODEL DESIGN

The logic model design task is to convert the basic ER diagram of the conceptual models to the
logical structure of the consistent data model supported by DBMS products. In this paper, the
user view method is used for standard tables. All the keywords of the tables are listed. The
design result of the user view is summarized. All user view tables are composed of a complex
database system. The logic design of the database are as follows;

User ( user ID, name, password, sex, telephone, address).

Payment (payment ID, user ID, ticket ID, payment date, payment amount, payment description)

Ticket( ticket ID, user ID, payment ID, train ID, ticket type, date issued, ticket description, ticket
price, seat number)
Train (train ID, train name, departure time, arrival time, departure date, arrival date, train
description, arrival date, departure location, arrival location, distance)

8. DIAGRAMS

Fig 4. UML Class Diagram

USE CASE DIAGRAM :

 Definition: A behavioural diagram that shows a set of use cases and actors and their
relationships is called a use case diagram. It addresses the static use case view of a system and is
essential in modelling a system's behaviour. The major concepts involved in use case model are

Actor: an actor represents anything that interacts with the system.

Use case: a use case is a sequence of action a system performs that yields a result to the actor.

Relation: it defines the relationship between the actor and a user.

The actors involved in the use case diagram are:

 User
 Train
 Application Layer

The use cases involved are:

 Login
 Register
 Issue ticket
 Choose source and destination
 Book ticket
 Make payment
 Check availability
o Date
o Train name
o Reservation type
o Fill and Submit form
 login <<extend>> register

check availability Train

*Date
*Time
*Reservation Type
User

Choose source, destination

book ticket
<<extend>>

<<extend>>
cancel booked ticket

update booked ticket

Application Layer

make payment

<<include>>

issue ticket

Fig 5. UML Use Case Diagram

 Check Availability

if available

Request booking form

Provide booking form

Validate booking

Update detail

Make Payment

Validate Payment Update payment detail

Issue Ticket

Request cancellation

Perform cancellation

Validate cancellation

Update train

Update cancellation detail

Fig 6. Sequence Diagram[3]

Enter Details Database

User Online Train Update Info
Layer
Issue Ticket Ticketing System Retrieve Info

Fig 7. Context DFD

9. REFERENCES
1. Shartriyan M.A. & Vijay M., (2018). GPS Based Railway Ticketing and Checking
Application(Indian Railway Local Ticketing), 3(12))
2. What are the requirements for a hotel reservations system ....
https://www.siteminder.com/r/technology/hotel-internet-booking-engines/requirements-
hotel-reservations-system/
3. SRS. Railways Reservation. https://www.slideshare.net/khushikalaria/srs-for-railway-
reservation-system