1

A
PROJECT REPORT
ON

RAILWAY RESERVATION SYSTEM

Session 2021-22
BCA PART-III
GUIDED BY SUBMITTED BY
[GUIDE NAME] [STUDENT NAME]
(Assistant Professor)

SUBMITTED TO

DEPARTMENT OF COMPUTER SCIENCE

GOVT. V.Y.T. PG AUTONOMOUS COLLEGE DURG,
CHHATTISGARH, INDIA
2

CERTIFICATE OF APPROVAL

This is to certify that the Project work entitled “NAME OF PROJECT” is

carried out by Mr./Ms. Name of student, student of BCA-III YEAR. At
GOVT. V.Y.T. PG AUTONOMOUS COLLEGE DURG, C.G., INDIA is
hereby approved as a credible work in the discipline of Computer Science &
Information Technology for the award of degree of BACHELOR OF
COMPUTER APPLICATION during the year 2021-22 from “HEMCHAND
YADAV UNIVERSITY DURG, C.G.”

HOD
DEPT. OF COMP. SCIENCE
3

CERTIFICATE OF PROJECT GUIDE

This is to certify that the Project work entitled “PROJECT NAME” submitted
to the GOVT. V.Y.T. PG AUTONOMOUS COLLEGE DURG, C.G.,
INDIA by Mr./Ms “STUDENT NAME” in partial fulfillment for the
requirements relating to nature and standard of the award BACHELOR OF
COMPUTER APPLICATION degree for the academic year 2021-22 .

This project has been carried out under my guidance.

(Guide Name)

DEPT. OF COMP. SCIENCE

4

CERTIFICATE OF EVALUATION

This is to certify that the Project work entitled “PROJECTNAME” is carried

out by Mr./Ms. “STUDENT NAME”, a student of BCA-III YEAR. At
GOVT. V.Y.T. PG AUTONOMOUS COLLEGE DURG, C.G., INDIA after
proper evaluation and examination, is hereby approved as a credible work in the
discipline of Computer Science and is done in a satisfactory manner for its
acceptance as a requisite for the award of degree of BACHELOR OF
COMPUTER APPLICATION during the year 2021-22 .

Internal Examiner External Examiner

5

DECLARATION

This to certify that the Project report entitled “PROJECT NAME”,which is

submitted by me in the partial fulfillment for the award of thedegree of
BACHELOR OF COMPUTER APPLICATION, GOVT. V.Y.T. PG
AUTONOMOUS COLLEGE DURG, C.G., INDIA comprises the original
work carried out by me.

I further declare that the work reported in this project has not been submitted
and will not be submitted, either in part or in full for the award of any other
degree or diploma in the institute or any other Institute or University.

PLACE: STUDENT NAME

DATE: ROLL NO:- …….
6

ACKNOWLEDGEMENT

It is great pleasure to present project report entitled “PROJECT NAME”

submitted to the Department of Computer Science to fulfill the BACHELOR IN
COMPUTER APPLICATION to GOVT. V.Y.T.PG AUTONOMOUS
COLLEGE, DURG (C.G).

We are greatly indebted to our [GUIDE NAME] and faculty member for
providing us the appropriate topic to work on. We are thankful to our faculty for
their whole-hearted co-operation, encouragement, valuable suggestions and
guidance.

Finally we are also grateful to our Principal sir and all those who directly or
indirectly helped us for the successful completion of this project report.

SUBMITTED BY

STUDENT NAME
7

INDEX
1. INTRODUCTION
 OBJECTIVES
2. REQUIREMENT ANALYSIS
 SOFTWARE &HARDWAREREQUIREMENT.
 MODULES.
3. SYSTEM ANALYSIS
 E-R DIAGRAM
 DATA FLOW DIAGRAM
 DATA DICTIONARY
4. SYSTEM DESIGN
 OUTPUT SCREEN
5. TESTING
6. ADVANTAGES AND LIMITATION
7. CONCLUTION
8. FUTURE ENHANCEMENTS
9. REFERENCE
10. BIBLIOGRAPBHY
8

INTRODUCTION
9

INTRODUCTION:-
The “Railway Reservation System” has been developed to override the
problems prevailing in the practicing manual system. This software is supported
to eliminate and in some cases reduce the hardships faced by this existing
system. Moreover this system is designed for the particular need of the
company to carry out operations in a smooth and effective manner.

The application is reduced as much as possible to avoid errors while entering

the data. It also provides error message while entering invalid data. No formal
knowledge is needed for the user to use this system .Thus by this all it proves it
is user-friendly .Railway Reservation System , as described above , can lead to
error free , secure , reliable and fast management system. It can assist the user to
concentrate on their other activities rather to concentrate on the record keeping.
Thus it will help organization in better utilization of resources.

Every organization, whether big or small, has challenges to overcome and

managing the information of Ticket ,Train ,Customer ,Seat ,Payment .Every
Railway Reservation System has different Train needs, therefore we design
exclusive employee management system that are adapted to your managerial
requirements .This is designed to assist in strategic planning, and will help you
ensure that your organization is equipped with the right level of information and
details for your future goals .Also, for those busy exclusive who are always on
the go,our systems come with remote access features ,which will allow you to
manage your workforce anytime ,at all times .These systems will ultimately
allow you to better manage resources.
10

OBJECTIVES OF RAILWAY
RESERVSTION SYSTEM:-
1. The objective of railway reservation system is to give structural design to
railway system.

2. The project provides functionality and flexibility to railway system such that
one can operate that system easily and efficiently.

3. This project also provides a complete set of solutions for some common and
specific areas of work.

4. The main objective of the project on railway reservation system is to manage

the details of Train, Ticket, Booking, Customer,Payment.It manages all the
information about Train, Seat, Payment .The project is totally built at
administrative end and thus only the administrator is guaranteed the access.The
purpose of the project is to build an application program to reduce the manual
work for managing the Train, Ticket, Seat, Booking. It tracks all the details
about the Booking, Customer, Payment.

Through this system, a practical approach has

been taken under study to understand how online reservation system works.
This system will include all the necessary fields which are required during
online reservation system. The basic idea behind this project is to save data in a
central database which can be accessed by any authorize person to get
information and saves time and burden which are being faced by their
customers.
11

REQUIREMENT ANALYSIS

SYSTEM SPECIFICATION:-
12

Hardware Requirement:-
 Intel-13(Processor).
 4GB RAM.
 Microsoft compatible 101 or more keyword.
 Hard disk 1 TB.

Software Requirement:-
 Operating System: Window 10 with MS Office.
 Programming Language: c#
 Back-End: SQL Server.
 Front-End: ASP.NET Framework and Microsoft Visual Studio
2010.
 Document Developer: MS Word.

Introduction of Microsoft visual studio 2010

and asp.net framework.
13

Microsoft Visual Studio 2010:-

Visual Studio is an Integrated Development Environment (IDE) developed by

Microsoft to develop GUI (Graphical User Interface), console, Web applications,
web apps, mobile apps, cloud, and web services, etc. With the help of this IDE, you
can create managed code as well as native code. It uses the various platforms of
Microsoft software development software like Windows store, Microsoft Silverlight,
and Windows API, etc. It is not a language-specific IDE as you can use this to write
code in C#, C++, VB (Visual Basic), Python, JavaScript, and many more languages.
It provides support for 36 different programming languages. It is available for
Windows as well as for Mac OS.

Visual Studio 2010 IDE has the ability to drag a child window outside of
the IDE parent window. Monitors have become affordable enough to allow
developers to use two (or more) in their work, and this new feature lets you
spread out your coding and design windows across multiple screens.

ASP.NET Framework:-
ASP.NET is an open-source, server-side web-application framework designed
for web development to produce dynamic web pages. It was developed by
Microsoft to allow programmers to build dynamic website, application and
services. It was first released in January 2002 with version 1.0 of the .NET
Framework and is thesuccessor to Microsoft’s Active Server Pages (ASP)
technology. ASP.NET is built on the Common Language Runtime (CLR),
allowing programmers to write ASP.NET code using any supported .NET
language.

SQL server:-

MS SQL Server is a relational database management system (RDBMS)

developed by Microsoft. This product is built for the basic function of storing
14

retrieving data as required by other application.SQL stands for Structured

QueryLanguage

Following are the benefits of SQL server:-

 SQL can execute queries against a database.

 SQL can retrieve data from a database.
 SQL can insert records in a database.
 SQL can update records in a database.
 SQL can delete records from a database.
 SQL can create new databases.
 SQL can create new tables in a database.
 SQL can create stored procedures in a database.
 SQL can create views in a database.
 SQL can set permissions on tables, procedures, and views.

Using SQL in Your Web Site:-

To build a web site that shows data from a database, you will need:

 An RDBMS database program (i.e. MS Access, SQL Server, MySQL).

 To use a server-side scripting language, like PHP or ASP.
 To use SQL to get the data you want.
 To use HTML / CSS to style the pages.
15

MODULES

PROJECT MODULES
MODULES USED:-
The proposed system categories and follows these modules to
implement.
Login Component
16

1. Passenger
Passenger Component
1. Train details.
2. Train Enquiry.
3. Passenger details.
4. Reservation.
5. Ticket.
MODULES DESCRIPTION:-
Passenger
Passenger is a person who can book ticket online and pay fare online.
Following tasks performed by passenger are as follows:
1. Passenger can view the details of train.
2. Passenger can enquiry about train.
3. Passenger can book ticket online.
4. Passenger can pay fare online.

SYSTEM ANALYSIS
17

SYSTEM ANALYSIS:-

1. Existing system
Under existing system passengers were only provided with list of
trains between two stations and train number is only the available
information by they can take an action. Under existing system
passengers were not able to get information on their arrival and
departure and route by which particular train will travel. Passengers
were only able to select the seat number and not provided which seat
type they want to select and this sometimes not creates a familiar
environment during their journey. During making payment final
validation and authorization was one by system to identify the
particular passengers to make deduction for their fare charges to make
final reservation.

2. PROPOSED SYSTEM
Through this system passengers do not have to wait in line and they
will able to get their answers in just a click. Through this system
online form will be available by which passengers will able to fill their
details along with their journey details. To book their seats, users will
have to first search their trains as per their requirements and after
getting correct train they will have to provide train number. After
pressing next button, it will show its status, whether it has been
activated or in process. Online cancellation form will also be available
and to cancel their reservation, they will have to provide their PNR
number again to carry the next task.
18

E-R Diagrams:

The Entity-Relationship (ER) model was originally proposed by Peter in 1976

[Chen76] as a way to unify the network and relational database views. Simply
stated the ER model is a conceptual data model that views the real world as
entities and relationships. A basic component of the model is the Entity-
Relationship diagram which is used to visually represent data objects. Since
Chen wrote his paper the model has been extended and today it is commonly
used for database design for the database designer, the utility of the ER model
is:

 It maps well to the relational model. The constructs used in the ER

model can easily be transformed into relational tables.
 It is simple and easy to understand with a minimum of training.
Therefore, the model can be used by the database designer to
communicate the design to the end user.
 In addition, the model can be used as a design plan by the database
developer to implement a data model in specific database
management software.

Connectivity and Cardinality

The basic types of connectivity for relations are: one-to-one, one-to-many, and
many-to-many. A one-to-one (1:1) relationship is when at most one instance of
a entity A is associated with one instance of entity B. For example, "employees
in the company are each assigned their own office. For each employee there
exists a unique office and for each office there exists a unique employee.
19

A one-to-many (1:N) relationships is when for one instance of entity A, there

are zero, one, or many instances of entity B, but for one instance of entity B,
there is only one instance of entity A. An example of a 1: N relationships is a
department has many employees each employee is assigned to one department.

A many-to-many (M:N) relationship, sometimes called non-specific, is when for

one instance of entity A, there are zero, one, or many instances of entity B and
for one instance of entity B there are zero, one, or many instances of entity A.
The connectivity of a relationship describes the mapping of associated

ER Notation

There is no standard for representing data objects in ER diagrams. Each

modelling methodology uses its own notation. The original notation used by
Chen is widely used in academics texts and journals but rarely seen in either
CASE tools or publications by non-academics. Today, there are a number of
notations used; among the more common are Bachman, crow's foot, and
IDEFIX.

All notational styles represent entities as rectangular boxes and

relationships as lines connecting boxes. Each style uses a special set of symbols
to represent the cardinality of a connection. The notation used in this document
is from Martin. The symbols used for the basic ER constructs are:

 Entities are represented by labeled rectangles. The label is the name

of the entity. Entity names should be singular nouns.
 Relationships are represented by a solid line connecting two entities.
The name of the relationship is written above the line. Relationship
names should be verbs
20

 Attributes, when included, are listed inside the entity rectangle.

Attributes which are identifiers are underlined. Attributes names
should be singular nouns.
 Cardinality of many is represented by a line ending in a crow’s foot.
If the crow’s foot is omitted, the cardinality is one.
 Existence is represented by placing a circle or a perpendicular bar on
the line. Mandatory existence is shown by the bar (looks like a 1) next
to the entity for an instance is required.

DATA FLOW DIAGRAM

21

The DFD takes an input-process-output view of a system i.e. data objects flow
into the software, are transformed by processing elements, and resultant data
objects flow out of the software.

Data objects represented by labeled arrows and transformation

are represented by circles also called as bubbles. DFD is presented in a
hierarchical fashion i.e. the first data flow model represents the system as a
whole. Subsequent DFD refine the context diagram (level 0 DFD), providing
increasing details with each subsequent level.

The DFD enables the software engineer to develop models of the

information domain & functional domain at the same time. As the DFD is
refined into greater levels of details, the analysts perform an implicit functional
decomposition of the system. At the same time, the DFD refinement results in a
corresponding refinement of the data as it moves through the processes that
embody the applications.

A context-level DFD for the system the primary external entities

produce information for use by the system and consume information generated
by the system. The labeled arrow represents data objects or object hierarchy.

RULES FOR DFD:

22

 Fix the scope of the system by means of context diagrams.

 Organize the DFD so that the main sequence of the actions
 Reads left to right and top to bottom.
 Identify all inputs and outputs.
 Identify and label each process internal to the system with Rounded
circles.
 A process is required for all the data transformation and Transfers.
Therefore, never connect a data store to a data Source or the
destinations or another data store with just a Data flow arrow.
 Do not indicate hardware and ignore control information.
 Make sure the names of the processes accurately convey everything
the process is done.
 There must not be unnamed process.
 Indicate external sources and destinations of the data, with
Squares.
 Number each occurrence of repeated external entities.
 Identify all data flows for each process step, except simple Record
retrievals.
 Label data flow on each arrow.
 Use details flow on each arrow.
 Use the details flow arrow to indicate data movements.
23

DFD LEVEL ZERO

DFD LEVEL 1
24
25

DATA DICTIONARY

LOGIN TABLE
26

TRAIN DETAIL TABLE

27

TRAIN ENQUIRY TABLE

28

PASSENGER DETAIL TABLE

29

TICKET RESERVATION TABLE

TICKET
30
31

SYSTEM DESIGN

INTRODUCTION:

Design is the first step in the development phase for any techniques and
principles for the purpose of defining a device, a process or system in sufficient
detail to permit its physical realization.
32

Once the software requirements have been analyzed

and specified the software design involves three technical activities - design,
coding, implementation and testing that are required to build and verify the
software.

The design activities are of main importance in this

phase, because in this activity, decisions ultimately affecting the success of the
software implementation and its ease of maintenance are made. These decisions
have the final bearing upon reliability and maintainability of the system. Design
is the only way to accurately translate the customer’s requirements into finished
software or a system.

Design is the place where quality is fostered in

development. Software design is a process through which requirements are
translated into a representation of software. Software design is conducted in two
steps. Preliminary design is concerned with the transformation of requirements
into data.
33

OUTPUT SCREEN
34

LOGIN
35

TRAIN DETAILS
36
37

TRAIN ENQUIRY
38

PASSENGER DEAILS
39

RESERVATION
40

TICKET
41

TESTING
 42

Testing is a process of executing a program with the intent of finding an error.

Testing is a crucial element of software quality assurance and presents ultimate
review of specification, design and coding.

System Testing is an important phase. Testing represents an interesting anomaly

for the software. Thus a series of testing are performed for the proposed system
before the system is ready for user acceptance testing.

A good test case is one that has a high probability of finding an as

undiscovered error. A successful test is one that uncovers an as undiscovered
error.

Testing Objectives:

1. Testing is a process of executing a program with the intent of finding an error

2. A good test case is one that has a probability of finding an as yet undiscovered
error
3. A successful test is one that uncovers an undiscovered error

Testing Principles:

 All tests should be traceable to end user requirements

 Tests should be planned long before testing begins
 Testing should begin on a small scale and progress towards testing in large
 Exhaustive testing is not possible
 To be most effective testing should be conducted by a independent third party

The primary objective for test case design is to derive a set of tests that has
the highest livelihood for uncovering defects in software. To accomplish this
objective two different categories of test case design techniques are used. They
are
43

 White box testing.

 Black box testing.

White-box testing:

White box testing focus on the program control structure .Test cases are
derived to ensure that all statements in the program have been executed at least
once during testing and that all logical conditions have been executed.

Block-box testing:

Black box testing is designed to validate functional requirements without regard

to the internal workings of a program. Black box testing mainly focuses on the
information domain of the software, deriving test cases by partitioning input and
output in a manner that provides through test coverage. Incorrect and missing
functions, interface errors, errors in data structures, error in functional logic are
the errors falling in this category.

Testing strategies:

A strategy for software testing must accommodate low-level tests that are
necessary to verify that all small source code segments has been correctly
implemented as well as high-level tests that validate major system functions
against customer requirements.

Testing fundamentals:

Testing is a process of executing program with the intent of finding error.

A good test case is one that has high probability of finding an undiscovered
error. If testing is conducted successfully it uncovers the errors in the software.
Testing cannot show the absence of defects, it can only show that software
defects present.
44

Testing Information flow:

Information flow for testing flowsthe pattern. Two class of input provided
to test the process. The software configuration includes a software requirements
specification, a design specification and source code.

Test configuration includes test plan and test cases and test tools. Tests
are conducted and all the results are evaluated. That is test results are compared
with expected results. When erroneous data are uncovered, an error is implied
and debugging commences.

Unit testing:

Unit testing is essential for the verification of the code produced during
the coding phase and hence the goal is to test the internal logic of the modules.
Using the detailed design description as a guide, important paths are tested to
uncover errors within the boundary of the modules. These tests were carried out
during the programming stage itself. All units of ViennaSQL were successfully
tested.

Integration testing:
Integration testing focuses on unit tested modules and build the program
structure that is dictated by the design phase.

System testing:
System testing tests the integration of each module in the system. It also
tests to find discrepancies between the system and its original objective, current
specification and system documentation. The primary concern is the
compatibility of individual modules. Entire system is working properly or not
will be tested here, and specified path ODBC connection will correct or not, and
giving output or not are tested here these verifications and validations are done
 45

by giving input values to the system and by comparing with expected

output .Top-down testing implementing here.

Acceptance Testing:

This testing is done to verify the readiness of the system for the implementation.
Acceptance testing begins when the system is complete. Its purpose is to
provide the end user with the confidence that the system is ready for use. It
involves planning and execution of functional tests, performance tests and stress
tests in order to demonstrate that the implemented system satisfies its
requirements.

Tools to special importance during acceptance testing include:

Test coverage Analyzer – records the control paths followed for each test case.

Timing Analyzer – also called a profiler, reports the time spent in various
regions of the code are areas to concentrate on to improve system performance.

Coding standards – static analyzers and standard checkers are used to inspect
code for deviations from standards and guidelines.

Test Cases:

Test cases are derived to ensure that all statements in the program have
been executed at least once during testing and that all logical conditions have
been executed.
Using White-Box testing methods, the software engineer can drive test cases
that

 Guarantee that logical decisions on their true and false sides.

 46

 Exercise all logical decisions on their true and false sides.

 Execute all loops at their boundaries and within their operational bounds.
 Exercise internal data structure to assure their validity.
The test case specification for system testing has to be submitted for review
before system testing commences.

ADVANTAGES AND DISADVANTAGES

ADVANTAGES:-
• Time and resource saving

• Chances of error minimize

• Reduce the paper work

• Easy access of system

• Long amount of data can be stored

• Backup resource facility available

• Consistent data standard and system design

• Eliminating manual processes

DISADVANTAGES:-
• You need internet access.
• You need to be ready for an influx of new customer.
• Not all online booking systems are created equal.
• Avoid booking system that doesn’t bring you knew quality customers.
47

CONCLUTION

CONCLUSION:-
Practical training is very important part of the curriculum as it
strengthens the concept and enhances knowledge about the practical
48

implementation of all the theory concepts, we have learnt so far in

different subjects.
The main aim of developing Reservation system is to provide all
information that is required by the user friendliness is a must that is
the user must get the details without complicated searching
procedures. Other important requirements of software are data
security, extensibility and maintainability. All these features are
included in this web application.
The project greatly helped in understanding the various phases in
website development and exposure to a new developer platform MS
Visual Studio.Net and database MS SQL Server.
49

FUTURE
ENHANCEMENTS

FUTURE ENHANCEMENTS:-
 We can add printer in future.
 We can give more advance software for Railway Reservation
System including more facilities.
 We will host the platform on online servers to make it accessible
worldwide.
 Integrate multiple load balancers to distribute the load of the
system.
 Create the master and slave database structure to reduce the
overload of the database queries.
 Implement the backup mechanism for taking backup of
codebase and database on regular basis on different servers.
50

The above mentioned points are the enhancements which can be

done to increase the applicability and usage of this project. Here
we can maintain the records of Train and Tickets. Also, as it can
be seen that now-a-days the players are versatile, i.e. so there is
a scope for introducing a method to maintain the Railway
Reservation System. Enhancements can be done to maintain all
the Train, Ticket, Booking, Passenger, payment.

REFERENCE
CONCLUSION
51

REFERENCES:
References are always needed for the development of any System /
Software development. Through the system development life cycle, I
refer the following books and manuals for related sources.

Book NameAuthor Name

Microsoft visual c# step by step - John Sharp

Programming in c# - E
BalaGuruSwamy
52

BIBLIOGRAPHY

BIBLIOGRAPHY:-
The following books were referred during the analysis and execution phase of
the project
53

Professional ASP.NET 4.5 in C# and VB (WROX)” by Jason N Gaylord and

Christian Went.

“ASP.NET 4.5, CoversC# and VB Codes, Black Book” by Cogent Learning

Solutions Inc.

Websites:

www.google.com

www.microsoft.com