Railway Management System 1

Download as pdf or txt
Download as pdf or txt
You are on page 1of 31

RAILWAY RESERVATION SYSTEM

By
Shreetu Kumari
Vasudha Nagar
Tanisha Nagar
Geetansh Laxkar

Submitted to the Department of Computer Science & Applications


In partial fulfillment of the requirements
For the Degree/Diploma of
BCA (Bachelor of Computer Application)
in
Computer Science

University of Kota
Session: 2020-21
Under the Esteemed Guidance of
Mr.Kamal Kulshestra
Lecturer
Dept. of Computer Science & Applications, MIMT, Kota

1
Modi Institute of Management & Technology, Kota

CERTIFICATE
Certified that project work entitled "Railway Reservation System"
is a bonafide work carried out Shreetu Kumari , Vasudha Nagar ,
Tanisha Nagar, Geetansh Laxkar at MIMT, Kota. In partial
fulfillment for the award of "BCA (Bachelor of Computer
Application) in Computer Science from University of Kota, Kota
during the academic year 2023-24
_________________
___________________
(External)
(Internal/Guide)
Name of External Name of
Internal/Guide
Date:
(Signature Date)

Dept. of Computer Science &Application


Modi Institute of Management & Technology,
Kota

2
ACKNOWLEDGEMENT

We take this occasion to thank God, almighty for blessing us with his grace
and taking our endeavor to a successful culmination. We extend our sincere
and heartfelt thanks to our esteemed guide, Mr,Kamal Kulshestra , for
providing us with the right guidance and advice at the crucial junctures and
for showing me the right way. We extend our sincere thanks to our respected
Head of the department Mr. Kamal Kulshreshtha, for allowing us to use the
facilities available. We would like to thank the other faculty members also,
at this occasion.
Last but not the least, we would like to thank our friends and family for the
support and encouragement they have given us during the course of our
work

3
INDEX

S.NO. PARTICULARS PAGE NO.


1. ABSTRACT 2
2. INTRODUCTION 4
3. OBJECTIVES AND OVERVIEW OF PROJECT 5
4. PROJECT PROFILE 5
5. SOFTWARE ENGINEERING PARADIGM APPLIED 6
6. SYSTEM STUDY 7
6.1. FEASIBILITY STUDY 7
7. REQUIREMENT ANALYSIS 9
8. APPLICATION DESIGN 12
8.1. DESIGN DESCRIPTION
8.1.1. USE CASE DIAGRAM 13
8.1.2. CLASS DIAGRAM 14
8.1.3. DATA FLOW DIAGRAM 15
8.1.4. ER DIAGRAM 16
8.2. DATABASE DESIGN 17
8.2.1. TABLES DESIGN DIAGRAM
8.3. INPUT OUTPUT SCREENS 20
9. TESTING 25
10. IMPLEMENTATION 27
11. ADVANTAGES AND LIMITATIONS 28
12. FUTURE SCOPE 29
13. CONCLUSION 29
14. REFERENCES 30

4
ABSTRACT

Project Name : Railway Reservation System


Project Team: Shreetu Kumari , Vasudha Nagar , Tanisha Nagar, Geetansh
Laxkar
Term: 2023-24 ( BCA Final Year)

Summary :
Railway Reservation System facilitates the passenger to enquire about the
trains available on the basis of source and destination. Booking of Tickets,
Travelling Details, Registration of new Passenger with unique PNR, ete. The
aim of the project is to design and develop a database maintaining the
records of different trains and passengers.
This project contain introduction to the Railway Reservation System. It is
the computerized system of reserving the seat of trains in advance. Online
reservation has made the process for the reservation of seats very much
easier than ever before.
This project contain Entity Relationship Model Diagram based on Railway
Reservation
System and also design of the Database of Railway Reservation System.

5
RAILWAY
MANAGEMENT
SYSTEM

6
INTRODUCTION

Every indian can been proudly say that the Indian Railway is the world second largest
railway system.If going by figures it covers,6853 station and 63028 kilometers of track
distance,carrying a load of 37840 passengers and around 500 tons of freight annualy.
With this huge magnitude our railway system faced a problem of a complete and fast
reservation system,which has been started as PRS(passenger reservation system) in 1985 and was
formed around the objective or providing reserved reservation to the train travelers.Even after a
lot of pilots done for this system it fell short of the expectations as it was not automated and
hence officients.
Due to the efforts put in this direction now reserved tecketing for anywhere in India
terminals and interactive voice response systems on telephone,or touch screens
Now one can easily plan the journey comfortably as the process is efficient and made
through the Indian railways site or at the ample reservation centers all over agencies which
provide reservation facility on behalf of india railways and without the booking is done through
an E-Ticket issue which have a PNR number of which the station.
It not only reservation but cancellation can also be done through this system at the
process.
This being a big step in terms of improvement in the railway system.

7
OBJECTIVES AND OVERVIEW OF PROJECT

The project hence completed is intended to meet the requirements and hopefully perform
below the mentioned tasks.

 To act as an interface between the data provider and the database.


 Quick access to the complex and vast amount of data.
 To make the job of routine more dependent on computer thus reducing
human errors.
 Allow a more user friendly system, which will save precious time and
effort.
 Reduce the cases of wrong details as the system has many checks
performed throughout the system.
 A systematic and tabular storage of data.

PROJECT PROFILE

PROJECT : Railway Management System

PLATFORM USED : Windows XP

FRONTEND : VB 6.0

BACKEND : MS – ACCESS 2003

SOFTWARE ENGINEERING PARADIGM APPLIED

8
This paradigm also known as Software Development Life Cycle
(SWDLC). SWDLC is an abstract representation of gradual development and
evaluation of software that undergoes a series of sequential or concurrent steps of the
software development process. Our project “Stock Maintenance System” includes
this type for analyzing our requirements to make us understand the exact needs of
employer & employee.

System study

System Analysis

Design

Coding

Testing

Customer Evaluation Implementation

9
SYSTEM STUDY

System study is the first stage of system development life cycle. The system
study is done in two phases:

 Preliminary Survey: This helps in identifying the scope of the system.


 Detailed Study: This phase is more detailed and in-depth study in which
the identification of user’s requirement and the limitations and problems
of the present system are studied.

After completing the system study, a system proposal is prepared and placed
before the user. The proposed system contains the findings of the present system
and recommendation to overcome the limitations and problems of the present
system in the light of the user’s requirements.

Feasibility Study

Many feasibility studies are disillusioning for both user and analysts. First, the study
often presupposes that when the feasibility document is being prepared, the analyst is in
apposition to evaluate solutions. Second, most studies tend to overlook the confusion
inherent in system development- the constraints and the assumed attitudes. If the
feasibility study is to serve as a decision document, it must answer three key questions:

1. Is there a new and better way to do the job that benefits the user?
2. What are the costs and savings of the alternative(s)?
3. What is recommended’?

10
Economic Feasibility

Economic analysis is the most frequently used method for evaluating the effectiveness of
a candidate system. More commonly known as cost/benefit analysis, the procedure is to
determine the benefits and savings that are expected from a candidate system and
compare them with cost.

• Developing training cost.


• Hardware cost.

Technical Feasibility

Technical feasibility centers around the existing computer system (h/w, s/w) and to what
extent it can support the proposed addition.

Operational Feasibility

Operational feasibility has no adverse effects. To find out whether the proposed system is
operationally feasible or not we compare it with the existing system and manual work and
find out whether it satisfy the end users need. Then the existing system and manual work
will be completely discarded. The proposed system is flexible, easy to understand and
provides an interface with actual implementation so it fulfills every requirement of end
users.

Time Feasibility

• Analysis : 15 days
• Design : 5 days

11
REQUIREMENT ANALYSIS

Analysis specifies what the software should do. Analysis is the process of gathering
and interpreting facts, diagnosing problems and using the information to recommend
improvements to the system.

Analysis is a detailed study of various operations performed by a


system and their relationships within and outside the system. During analysis, data are
collected on the available files, decision points and transaction handled by the present
system.

During this phase we determined the following system elements:

1.System Objective: We determine the centralized and single objective of the system.

2.Required Resources: Resources may be hardware, people, software etc. We use


resources such as VB.NET & MS – ACCESS 2007 in the initial phase.

3.Assessment of Feasibility: Our system satisfy the technical, economical, operational


feasibilities.

12
Working of Existing system:-

In the present scenario of the system all the information related to the maintenance of
stock has to be done manually in a transaction book. We have to keep all the details of
the stock separately. There is a lot of manual work and a separate log book is to be
maintained for each type of transaction.

Disadvantages of Existing System:-

 It is a time consuming job because the work is done manually i.e. the storing of
information .
 Since it requires operating manually hence consumes manpower .
 Quick generation of information is not possible.
 No data consistency is there.
 Lack of data security.
 High implementation cost.
 Data redundancy.

Proposed System:-
To overcome all the drawback of the existing system, an automated system is
required, which fulfills all the requirements of the end users.This software provides a
facility store the information about the stock details.

Advantages of the Proposed System:-


 Redundancy of data is reduced at high level.
 Saves time.
 Reduces manual work.
 Quick Generation of report on time.
 Provides data security.

13
SOFTWARE REQUIREMENTS

Software required for the accomplishment of our project are:


 Visual Studio .NET 2003 Version
 Microsoft Access-2007
 Visual VB Dot NET (Language Used)

HARDWARE REQUIREMENTS

Hardware Specifications of the system on which the project has been


devised are:
 Hard Disk 20 GB
 Memory 128 MB of RAM
 Processor Intel® Pentium
 CPU 1.72 GHz

14
APPLICATION DESIGN

The design of an information system provides the details that state how a system
will meet the requirements identified during system analysis. Designing phase was
most interesting and creating part of our project during this period we made various
windows based forms according to the requirement of our project, basically a form is
designed by inserting various controls from the toolbox provided in the .NET Studio.
The design proceeds in two stages:

 Preliminary Design: In the preliminary design, the features of the new


system are specified. The costs of implementing these features and the
benefits to be derived are estimated. If the project is still considered to be
feasible, we move to the detailed design stage.

 Structured or Detailed Design: In the detailed design stage, computer


oriented work begins in earnest. At this stage, the design of the system
becomes more structured. Input, output and processing specifications are
drawn up in detail. In the design stage, the programming language and the
platform in which the new system will run are also decided.

15
Use Cases

Ticket Use-Case

16
Class Diagram

17
CONTEXT FLOW DIAGRAM

Railway
Login Management
USER
System
Logout

DATA FLOW DIAGRAM

0 level

18
ER DIAGRAM

19
DATABASE DESIGN

 Reservation Table:

 Passenger Table:

20


 Train table:

 Journey table

21
 Types of seat Table

22
Input/Output Screens

Our project comprise of following forms, viz :


1. Login: This form checks if the user is a valid user or not and
asks the password, username for authentication.
2. Password Change: This form is used to change the password of the
existing user.
3. Main Form: This form is the Central Form of our project through which
we can visit to any other forms excluding Login Form. The main menu is
used as control.
4. Book your rail ticket: By using this form we can book tickets.
5. Purchasing ticket: This process is of purchasing ticket by giving money
on ticket counter.
6. Layout of railway path: This is a layout of railway path.

23
 Login Form

 Password change

24
 Main Form

 Book your rail ticket

 Purchasing ticket

 Layout of railway path

TESTING

Testing provides an interesting anomaly for software engineers during earlier software
engineering activities. The engineer create a series of test that are intended to “demolish” the
software has been built. In fact testing is one step in the software process that could be

25
viewed as distinctive rather than constructive. Testing requires that the developer discard
preconceived. Notions of the “correctness” of software just developed and overcome a
conflict of interest that occurs when error are uncovered.

The testing phase of our module in this we tests our project with some dummy
data’s in order to retrieve the progression of our report to seek the proper functioning of the
controls we included in our project.

Testing should have these features:


1. Testing should begin “in the small” and progress toward testing “in the large”.

2. To be most effective, testing should be conducted by an independent third party.

3. All tests should be traceable to customer requirements.

 Unit Testing:

Unit testing focuses verification effort on the smallest unit of Software


Design –Software component or module. Using the Component level design
description as a guide, important control paths are tested to uncovered errors
within the boundary of the module.

Boundary conditions are tested to insure that the module operates properly
at boundaries established to limit or restrict processing. All independent paths
through the control structure to ensure that all statements in a module have been
executed at least once. And finally, all error handling paths are tested.

 Integration Testing:

26
Integration testing is a systematic technique for constructing the program
structure while at the same time conducting tests to uncover errors associated with
interfacing. The objective is to take unit tested components and build a program
structure that has been dictated by design.

 Validation Testing:
At the culmination of integration testing, software is completely assembled as a
package, interfacing errors have been uncovered and corrected, and a final series of
software test- validation testing- may begin.
Validation can be defined in many ways, but a simple definition is that validation
succeeds when software functions in a manner that can be reasonably expected by the
customer.

IMPLEMENTATION

After having the user acceptance of the new system developed, the implemented phase
begins. Implementation is the stage of a project during which theory is turned into
practice. During this phase, all the programs of the system are loaded onto the user’s

27
computer. After loading the system, training of the user starts. Main topics of such type
of training are:
 How to execute the package
 How to enter the data
 How to process the data
 How to take out the reports
After the users are trained about the computerized system, manual working has to
shift from manual to computerized working.

ADVANTAGES & LIMITATIONS

ADVANTAGES :

28
 Simple & easy to understand.
 Economical.
 User Friendly.
 Catering to Exact Needs.
 Use of report provides print facility.

LIMITATIONS :

 This software supports only English language.

FUTURE SCOPE

 This software supports only English language.


 Help facility can be provided.

29
 Icons for direct access can be provided.
 Context menu can be provided.
 Railway Management System next version will contain better features
with above limitations removed.
.

CONCLUSION

The project development period was really a very enriching and informative experience
for us. We got the feel of the designing wear and field, besides developing our
programming skills .We understood the importance of planning and designing which is a
part of software development .The making of the project has enhanced our practical
knowledge and taught us how to work in teamwork. The project is the outcome of our
continual teamwork. The regular guidance and constant watch never let us frivolous and
kept us aware of what was going on in other parts of the department and the world. In the
end, we would once again thank, all the persons who made such kind of project work
possible for us. Developing this project has helped us to gain some experience on real
time application.

30
31

You might also like