ATAL BIHARI VAJPAYEE- INDIAN INSTITUTE OF INFORMATION

TECHNOLOGY AND MANAGEMENT

GWALIOR-474001

RAILWAY RESERVATION SYSTEM

SOFTWARE ENGINEERING LAB PROJECT REPORT

Submitted To: Submitted By:

Dr. Santosh Rathore Priyash Gupta (2017IMT-070)
Arihant Jain (2017IMT-096)
Kalp Kumar Varshney (2017IMT-099)
Ruchika Agrawal (2017IMT-105)
TABLE OF CONTENTS

1. Introduction
1.1. Overview of the Project
1.2. Objectives of the Project
1.3. The Need for the Project
1.4. Overview of Existing Systems and Technologies
1.5. Scope of the Project
1.6. Deliverables
2. Feasibility Study
2.1. Financial Feasibility
2.2. Technical Feasibility
2.3. Resource and Time Feasibility
3. Considerations
1. Introduction
1.1. Overview of the Project
This system is basically concerned with the reservation and cancellation of railway
tickets to the passengers. The need of this system arose because as is the known fact
that India has the largest railway network in the whole of the world and to handle it
manually is quite a tough job. By computerizing it, we will be able to overcome many of
its limitations and will be able to make it more efficient. The handling of data and records
for such a vast system is a very complex task if done manually but it can be made much
easier if the system is computerized. To be more specific, our system is limited in such a
way that a train starting from a particular source will have a single destination.​The
program helps users to reserve or cancel a train ticket. Moreover, the program also
helps us to know the present status of a reserved ticket, i.e. whether the ticket is
confirmed or not using its PNR number. It includes various function programs to do the
above mentioned tasks.

1.2. Objectives of the Project

The objectives of the project are:

❖ The objective of railway reservation system is to give structural design to railway system
❖ It reserves tickets for the passenger.If the asked seat is not available, it puts it in waiting
list.
❖ It allows the passenger to cancel his/her reserved seats.
❖ It allows PNR status checking
❖ It contains information about the trains.
❖ It contains information about the passenger.
❖ It contains the details of reservation fees, any concessions etc.
❖ It makes entries for reservation, waiting, cancelled tickets. (seat availability)
❖ Payment options – one chosen by default, others available upon request.

1.3. The Need for the Project

To develop software is the first thing which comes to mind. But then why do we need to
develop software? What are the problems faced by the user or staff to manually maintain
their records that they decided to computerize their working? In railway reservation there
are so many tasks, which are tedious and time consuming. The person who maintains
the reservation manually faces so many problems like searching for details of booked
tickets. Security concern is also a major issue because manual records can easily be
manipulated. So, to solve these types of problems we’ve designed a computerized
railway reservation system, which is easy to operate, and only authorized person can
edit the information. Record entry and searching is not time consuming and fine is
calculated automatically.

❖ Searching of the trains is so easy.

❖ Reduce the possibility of making mistakes.
❖ Reservation and cancellation can be done very easily.
❖ The project provides functionality and flexibility to railway system such that one can
 operate the system easily and efficiently.

1.4. Overview of Existing Systems and Technologies

Indian Railway Catering and Tourism Corporation consists some of the use cases that
are implemented in our project.But our project is mainly concerned with ticket
reservation,cancellation and details of the ticket and trains.

Main Technology associated with our project.

❖ Web programming technologies (HTML, CSS, JS, Django, React)

❖ SQLite 3 (Database)

1.5. Scope of the Project

Main actors of this system are:

❖ Admin
❖ Management Staff
❖ Passenger

Main use cases associated:

❖ Admin and Management Staff can

➢ Update information about seats in the train.
➢ Update information about source and destination of the train.
➢ Update the timing of trains.
➢ Update the information regarding running/cancelled status of trains.
➢ Update the fare of the trains.

❖ Passenger can
➢ Reserve a ticket for a train.
➢ Cancel the reserved ticket.
➢ Check PNR status.
➢ Check the available trains from one station to another station.

1.6. Deliverables
A web based software system. It contains a central database and functionalities for
various stakeholders. Since many number of stakeholders are involved, different login
portal will be provided to different users​.
2. Feasibility Study
2.1. Financial Feasibility
Being a web application ,it will have an associated hosting cost. Since the system
doesn’t consist of any multimedia data transfer, bandwidth required for the operation of
this application is very low. The system will follow the freeware software standards. No
cost will be charged from the potential customers (except the ticket charges) .Bug fixes
and maintaining tasks will have an associated cost. At the initial stage the potential
market space will be the Indian Railway. Beside the associated cost, there will be many
benefits for the customers. From these it’s clear that the project RTS is financially
feasible.

2.2. Technical Feasibility

Our Project is a complete web based application. The main technologies and tools that
are associated with RTS are:

❖ HTML
❖ CSS
❖ SQLite3
❖ JS
❖ Django
❖ React

Each of the technologies are freely available and the technical skills required are
manageable. Time limitations of the product development and the ease of implementing
using these technologies are synchronized. Initially the web site will be hosted in a free
web hosting space, but for later implementations it will be hosted in a paid web hosting
space with sufficient bandwidth. Bandwidth required in this application is very low, since
it doesn’t incorporate any multimedia aspect. From these it’s clear that the project RTS is
technically feasible.

2.3. Resource and Time Feasibility

Resource feasibility
Resources that are required for the RTS project includes:
❖ Programming device (Laptop)
❖ Hosting space (freely available)
❖ Programming tools (freely available)
❖ Programming individuals

So, it’s clear that the project RTS has the required resource feasibility.
3. Considerations
Performance:
RTS requires a very low bandwidth, hence the performance will not degrade with
increasing number of potential users. At the development stage, a free hosting
service will be used. But when installing the system to a real environment, it will
be hosted in a much more reliable server to increase the performance. SQLite3
will provide the adequate speed for database transactions. Since no big data
analysis is done, SQLite3 is the ideal database for this project.

Response time: less than 2 seconds

Processing time: Less than 2 seconds (no batch processing involved)
Query and reporting times: yet to be tested
Throughput: yet to be tested
Storage: yet to be tested

Security:
Security measures are provided in many aspects in this system.

User authentication: Users will have to authenticate using the username and
passwords. Depending on the access level, each user will gain functionality of
the system. Passwords can be changed by the user.

Usability and Ease of use:

The interfaces are designed to make it easy for any potential user to get familiar
with the system within one hour. No additional training is required to use the
system.

Capacity and scalability:

RTS system can accommodate many simultaneous users.

Availability:
System will be available throughout the 24 hours. Mean time to failure and mean
time to repair will be decided to increase the availability. With a paid hosting
space, the availability can be guaranteed to a great precision.

Maintainability:
RTS is designed using the best practices of Django. Since every single segment
in the system is very well structured, the system is highly maintainable. 4+1 view
model will be used as the main architectural pattern in this system. Hence the
separation of each task is improved, hence maintainability improved.