GYAN GANGA COLLEGE OF TECHNOLOGY

JABALPUR

MINOR PROJECT REPORT ON

ONLINE RAILWAY RESERVATION

SYSTEM
Submitted to the

RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA, BHOPAL

In partial fulfilment of the requirement for the award of the Degree of

MASTER OF COMPUTER APPLICATIONS

Submitted to

DEPARTMENT OF COMPUTER APPLICATIONS

Gyan Ganga College of Technology Jabalpur (M.P.)

Under the Guidance of

[Link] Utmal. Mr. Varun Garg .

HOD, MCA Dept Professor

Submitted by

AJAY KORI (0208CA241009)

MCA III SEM 2025-26

 ABSTRACT

Our system is developed for supporting entire general Wire Industry Billing
System Process. It is based on current need provided by the offices to their
employees.

It is developed on two tier architecture by which presentation layer is

separated by database logic.

This system is designed for secure transactions and can with stand in heavy
loads.

This project facilitates central control in distributed environment.

It is having the facility of user registration so that only intended user can access
this system based on their roles.

This s/w provides the quick way for analysing and reporting the transaction
based on duration, item and generation of bill.

Different type of client-side validations are implemented for ensuring data

integrity.

This system will definitely reduce the time required for item reg., issuing and
bill generation of item and managing database.
 GYAN GANGA COLLEGE OF TECHNOLOGY

JABALPUR

DECLARATION
I hereby declare that this project report titled “ ONLINE RAILWAY RESERVATION
SYSTEM ” submitted by me in fulfilment for the award of Master of Computer
Applications (M.C.A.) by Rajiv Gandhi Proudyogiki Vishwavidyalaya, Bhopal is a
result of authentic work under taken by me.

The same has not been submitted by me to this or any other university for any
other graduate/post graduate course whatever.

PROJECT SUBMITTED BY:

Mr AJAY KORI
 GYAN GANGA COLLEGE OF TECHNOLOGY
JABALPUR

CERTIFICATE
This is to certify that the project report entitled “ONLINE RAILWAY RESERVATION
SYSTEM” which has been completed and submitted by AJAY KORI III SEM MCA the
Student of Master of Computer Application (MCA) is a bonafide work by his/her.
This Project report has been approved by us. The project report is satisfactory
both in respect of its contents and literally representation.

This project report is in accordance with the requirement of degree of Master of

Computer Application (MCA) awarded by RAJIV GANDHI PROUDYOGIKI
VISHWAVIDALAYA, Bhopal (M.P.).

Date:15-12-2025. DR. MEGHNA UTMAL

HOD MCA
 GYAN GANGA COLLEGE OF TECHNOLOGY
JABALPUR

CERTIFICATE
This is to certify that the project report entitled “ONLINE RAILWAY RESERVATION
SYSTEM” which has been completed and submitted by AJAY KORI III SEM MCA the
Student of Master of Computer Application (MCA) is a bonafide work by his/her.
This Project report has been approved by us. The project report is satisfactory
both in respect of its contents and literally representation.

This project report is in accordance with the requirement of degree of Master of

Computer Application (MCA) awarded by RAJIV GANDHI PROUDYOGIKI
VISHWAVIDALAYA, Bhopal (M.P.).

Internal examiner : External examiner :

Date : Date :
 TABLE OF CONTENTS
ABSTRACT

ACKNOWLEDGEMENT. DECLARATION.
CERTIFICATE. CETRTIFICATE OF GUIDANCE

CHAPTER No. AND TITLE

1. INTRODUCTION
1.1 About the Project. 1.2 Features Of Project.
1.3 Scope. 1.4 Limitation.
1.5 Process Framework. 1.6 Software Development Life
Cycle(SDLC)

2. FEASIBILITY & REQUIREMENT

2.1 Feasibility Study. 2.2 Three Phases Of Feasibility

Study. 2.3 Steps Involved In Feasibility Study. 2.4
Feasibility Analysis Report

3. SOFTWARE REQUIREMENT SPECIFICATION

3.1 Introduction. 3.2 SRS of the Project.

3.3 Detailed Description Of Project. 3.3.1 Introduction.
3.3.2 Overall Description. 3.4 Software Requirement
3.5 Hardware Requirement. 3.6 Introduction To Visual
Basic/C++ [if other tool is used introduction of that tool and data base]
4. SYSTEM DESIGN

4.1 Design. 4.2 Various Approaches For Design

Documentation. 4.3 Abstraction. 4.4 Modularity.
4.5 Module Level Concept. 4.6 Module-Based Design.
4.7 ER Diagram. 4.8 Flow Chart.

5. CODE AND USER INTERFACE

6. TESTING

6.1 Test Cases. 6.2 Type Of Testing.

7. CONCLUSION

8. BIBLIOGRAPHY
 Chapter-1
INTRODUCTION

1.1 ABOUT YOUR PROJECT

This project will give us the information about railway reservation. This system is basically
concerned with the reservation and cancellation of railway tickets to the passengers. 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 basic functions being performed by our system
are reservation and cancellation.

Customers can find the proper and correct information about the railway and shows the

• It reserves and cancels seats for the passenger.

It contains information about the trains.
It contains information about the Seat Availability
Railway time table.
Reservation Possibilities.
• Train Ticket booking.
• Booked Railway Ticket Status,
• Train between station
1.2 FEATURES OF PROJECT

1. Searching of data is easy. 2. Passengers don't have to wait

for a long time. 3. Information is accurate. 4. It is a
fast process. 5. Data efficiency is more

1.3 SCOPE

The scope of this project is limited to an engineering college. This project aims to maintain
passenger and train information. Other scopes of this project are as follows:

• Freight Revenue enhancement

• Passenger Revenue enhancement
• Improved and optimised service

1.4 LIMITATIONS :

When the train journeys started in India, it used to work with steam engines and it has
developed through time till they become electric express trains. Thanks to modern
technology, the Indian Railways have now their distinguished revolutionary concept to the
extent that you can have your reservation while you are at home using the internet. No
doubt, this is a very brave step; especially when you talk about a country where internet
illiteracy is so high.
1.5 PROCESS FRAMEWORK

A process framework establishes the foundation for a complete software process by

identifying a small number of framework activities that are applicable to all software
projects, regardless of their size and complexity. In addition, the process framework
encompasses a set of umbrella activities that are applicable across the entire software
process.

The following generic process framework is applicable to the vast majority of software
projects.

Communication: The framework activity involves heavy communication and collaboration

with the customer and encompasses requirements gathering and other related activities.

Planning: This activity establishes a plan for the software engineering work that follows. It
describes the technical tasks to be conducted, the risks that are likely, the resources that
will be required, the work products to be produced, and a work schedule.

Modelling: This activity encompasses the creation of models that allow the developer and
the customer to better understand software requirements and the design that will achieve
those requirements.

Construction: this activity combines code generation and the testing that is required
uncovering errors in the code.

Deployment: The software is delivered to the customer who evaluates the delivered
product and provides feedback based on the evaluation.
The modelling activity is composed of two software engineering actions-analysis and
design. Analysis encompasses a set of work tasks(requirements gathering, elaboration,
negotiation, specification and validation) that leads to the creation of the analysis model.
Design encompasses work tasks(data design, architectural design, interface design, and
component-level design) that create a design model. The
framework described is complemented by a number of umbrella activities-

1. Software project tracking control

2. Risk Management
3. Software Quality Assurance
4. Formal Technical Reviews
5. Measurement
6. Software Configuration Management
7. Reusability Management
8. Work Product Preparation and Production

1.6 SOFTWARE DEVELOPMENT LIFE CYCLE(SDLC)

Phase 1: Requirement collection and analysis

Phase 2: Feasibility study:

Phase 3: Design:

Phase 4: Coding:

Phase 5: Testing:

Phase 6: Installation/Deployment:

Phase 7: Maintenance
 Chapter-2

Feasibility Study

2.1 FEASIBILITY STUDY

Feasibility study is a study, usually done by engineers, that establishes whether conditions
are right to implement a particular project. Feasibility studies can be done for many
purposes, and are sometimes done in IT in order to look at feasibility for new hardware and
software setups.

2.2 THREE PHASES OF FEASIBILITY STUDY

[Link] Feasibility

This is concerned with specifying equipment and software that will successfully satisfy the
user requirement. The technical needs of the system may vary considerably, but might
include:

• The facility to produce outputs in a given time.

• Response time under certain conditions.
• Ability to process a certain volume of transaction at a particular speed.
• Facility to communicate data to distant locations.
[Link] Feasibility

This is concerned with specifying equipment and software that successfully satisfy the
user requirement. The technical needs of the system may vary considerably, but might
include:

• The facility to produce outputs in a given time.

• Response time under certain conditions.
• Ability to process a certain volume of transaction at a particular speed.
• Facility to communicate data to distant locations.

[Link] Feasibility

This is mainly related to human organizational and political aspects. The points to be
considered are:

• What changes will be brought with the system?

• What organizational structure are disturbed?
• What new skills will be required? Do the existing staff members have these skills? If
not, can they be trained in due course of time?

This feasibility study is carried out by a small group of people who are familiar with
information system technique and are skilled in system analysis and design process.
Proposed projects are beneficial only if they can

be turned into information system that will meet

the operating requirements of the organization.

This test of feasibility asks if the system will work

when it is developed and installed.

2.3 STEPS INVOLVED IN FEASIBILITY ANALYSIS

Step 1: Conduct a Preliminary Analysis. ...

Step 2: Prepare a Projected Income Statement. ...

Step 3: Conduct a Market Survey....

Step4: Plan Business Organization and

Operations. ...

Step 5: Prepare an Opening Day Balance Sheet....

Step 6: Review and Analyse All Data. ...

Step 7: Make “Go/No Go” Decision.

 CHAPTER-3

SOFTWARE REQUIREMENT SPECIFICATION

3.1 INTRODUCTION

Software requirements specification (SRS) is a

detailed description of a software system to be

developed with its functional and non-functional

requirements. The SRS is developed based the

agreement between customer and contractors. It may

include the use cases of how user is going to interact with

software system. The software requirement specification

document consistent of all necessary requirements

required for project development. To develop the

software system we should have clear understanding of

Software system. To achieve this we need

To continuous communication with customers to gather all requirements.

3.3 DETAIL DESCRIPTION OF THE PROJECT

The Indian Railways (IR) carries about 5.5 lakhs passengers in reserved accommodation
every day. The Computerised Passenger Reservation System(PRS) facilities the booking
and cancellation of tickets from any of the 4000 terminals(i.e. PRS booking window all over
the countries). These tickets can be booked or cancelled for journeys commencing in any
part of India and ending in any other part, with travel time as long as 72hours and distance
upto several thousand kilometres.

The project of PRS was launched on 15 th November 1985, over Northern Railway with the
installation of Integrated
Multiple Train Passenger Reservation System(IMPRESS), an online transaction processing
system developed by Indian Railways in association with Computer Maintenance
Corporation Ltd., at New Delhi. The objective was to provide reserved accommodations on
any train from any counter, preparation of train charts and accounting of the money
collected. The application was implemented in 1987

Mumbai, Chennai, Kolkata, Skanderbeg ,subsequently

3.3.1 INTRODUCTION

• Railway passengers frequently need to know about their ticket reservation status,
ticket availability on a particular train or for a place, train arrival or departure details,
special trains etc.. Customer information centres at the railway stations are unable
to serve such queries at peak periods.

• The number of the reservation counters available to the passengers and customers
are very less.
 • On most of the reservation systems there are long queues, so it takes a long time for
any individual to book the ticket.

• As now there are no call centres facilities available to solve the queries of the
passengers.

3.3.2 OVERALL DESCRIPTION

ONLINE BOOKING: With the help of this people can book their tickets online through
internet, sitting in their home by a single click of mouse. Using their credit cards people can
easily get their tickets done within minutes. There are certain charges for online booking as
well.

COUNTER BOOKING: This is the oldest method of booking the tickets. The reservation
counters are there at railway department from where people can get the tickets to their
respective destinations.
3.4 SOFTWARE REQUIREMENTS-

1. Platform - Win XP, 7, 8, 10

2. Back End- Internet Explorer, Google Chrome

3. Front End - HTML, JAVA Script

3.5 HARDWARE REQUIREMENTS-

Hardware Requirement For Client's:

1. Minimum RAM - 256 MB

2. Processor - Pentium 4

3. LAN Card - Ethernet, wireless

4. Free Space - 40 GB

Hardware Requirement For Server:

1. Minimum RAM - 256 MB

2. Processor - Pentium 4

3. LAN Card - Ethernet, wireless

4. Minimum Free Space - 40 GB

3.6 INTRODUCTION TO VISUAL BASIC/C++

Microsoft Visual C++ (often abbreviated to MSVC) is an integrated development

environment (IDE) product from Microsoft for the C, C++, and C++/CLI programming
languages. MSVC is proprietary software; it was originally a standalone product but later
became a part of Visual Studio and made available in both trial ware and freeware forms. It
features tools for developing and debugging C++ code, especially code written for the
Windows API, DirectX and .NET.

Many applications require redistributable Visual C++ runtime library packages to function
correctly. These packages are often installed independently of applications, allowing
multiple applications to make use of the package while only having to install it once. These
Visual C++ redistributable and runtime packages are mostly installed for standard libraries
that many applications use.
 CHAPTER 4

ANALYSIS

1. In Online Railway Reservation System, for booking the tickets online the intended
user has to enter details like username and password.

2. Once the username and passwords are verified then he is allowed to enter the main
system wherein he can select the destination, date and no of tickets.

3. For the purchase of the tickets he is asked for payment details (like credit card details
etc).

4. The user is also provided with a provision of canceling the reservation where in the
entire amount is credited back to his account.

The analysis part also comprises of the UML diagrams that boost the program.
4.2 SPIRAL MODEL DIAGRAM

4.3 SPIRAL MODEL

The spiral model, originally proposed by Boehm [BOE88], is an

evolutionary software process model that couples the iterative
nature of prototyping with the controlled and systematic aspects of
the linear sequential model.
 • It provides the potential for rapid development of incremental versions of the
software. Using the spiral model, software is developed in a series of
incremental releases.

• During early iterations, the incremental release might be a paper model or

prototype. During later iterations, increasingly more complete versions of the
engineered system are produced.

• A spiral model is divided into a number of framework activities, also called task
regions. Typically, there are between three and six task regions.

4.4 USE OF SPIRAL MODEL

Figure depicts a spiral model that contains six task regions:

• Customer communication tasks required to establish effective communication
between developer and customer.

• Planning tasks required to define resources, timelines, and other project related
information.

• Risk analysis tasks required to assess both technical and management risks.

• Engineering-tasks required to build one or more representations of the

application.

• Construction and release-tasks required to construct, test, install, and provide

user support (e.g., documentation and training).

• Customer evaluation tasks required to obtain customer feedback based

on evaluation of the software representations created during

the engineering stage and implemented during the installation stage.

4.5 USE OF CASE DIAGRAM

 CHAPTER 5
EXPLORING THE CODE AND USER

INTERFACE

<html>

<head>

<title>railway reservation form </title>

</head>

<body bicolour="#0AAFFBC">

<form name="railway">

<centre>

<h1><marquee bicolored"#0FBF00">Railway

Reservation System </marquee> </h1>

<table>

<tr>

<td>From:</td>

<td><input type="text" name=""railway"</td>

</tr>

<tr>

<td>To:</td>
 <td><input type="text" name="txt2"</td>

</tr>

<tr>

<td>Name:</td>

<td><input type="text" name=""</td></tr>

<tr>

<td>Age:</td>

<td><input type="number" name=""</td>

</tr>

<tr>

<td>Address:</td>

<td><input type="text" nqme=""</td></tr>

<tr>

<td>Payment options:</td>

<td>

<input type="radio" name="payment" value="сс"

/>Credit Card <br />

<input type="radio" name="payment" value="dc" />Debit

card <br />

<input type="radio" name="payment"

value="wallet">wallet<br/>

</td>
 <tr>

<td><input type=”submit” value=”submit”</td

<td><input type=”submit” value=”Cancel”</td></tr>

</table>

</body>

</html>
 CHAPTER 6

Test
6.1 TEST CASE

A TEST CASE is a set of conditions or variables under which a tester will determine
whether a system under test satisfies requirements or works correctly. The process of
developing test cases can also help find problems in the requirements or design of an
application.

6.2 TYPES OF TESTING

Unit testing

Integration testing

System testing

Sanity testing

Smoke testing

Interface testing

Regression testing

Beta/Acceptance testing
CHAPTER CONCLUSION

Practical Training is a very important part of the curriculum as it strengthens the

concepts and enhances knowledge about the practical implementation of all the theory
concepts, we have learned so far in different subjects.

Our project is railway reservation system. This project is used to keep a track on
reserving the seat to the passenger. It helps managing the system very efficiently and
conveniently.

Although the project work has been done in a complete and detailed manner but due to
the constraint of time, we could not include some more features we wanted to. We left
these features as a part of the feature development. As soon as we'll get time, we'll try
to add them to my project.
 CHAPTER 8

BIBLIOGRAPHY
• Search Engine [Link]
• Complete Reference VB 6.0
• VB BLACK BOOK
• BPB publication “Mastering Database Programming In Visual Basic 6.0”
• Roger s Pressman “Software Engineering”
• Bipin Singh Desai “Relation Data Base Management System”