Railway Management System

1. RAILWAY SYSTEM
By:
SANDEEP KUMAR GOND
(2K20/SE/119)
SEHNISH DAGER
[2K20/SE/123]
To Submitted:
Prof. Abhilash Sharma

2. INTRODUCTION
 This system is basically concerned with the reservation of
railway tickets to the passengers.
 In this we are discussing that how the reservation is
done.
 What are the rules and regulations and procedure for
reservation?

3. Scope & Objectives
 All the manual work should be converted into
computerized so that the load of employees should
decrease.
 The database should be stored in computer rather than
in register/manually.

4. Features
 Searching of data is easy.
 Passengers don't have to wait for a long time.
 Information is accurate.
 It is a fast process.
 Data efficiency is more.

5. Requirements & Limitations
Limitations
 Data Redundancy
 Difficulty in
accessing the
Data
Hardware Requirements
 Processor : Pentium
IV 2GHz and Above
 RAM : 1GB
 Monitor : VGA Color
Monitor
Software Requirements
 Operating System :
Windows Xp onwards
 Developing Tool : VB
(front end)
 Database : MS-
ACCESS (back end)

6. Data flow diagram
 The data flow diagram is a graphical representation that
depicts information flow and the transforms that are applied
as data moves from input to output.
1. Context level or 0-level DFD
2. 1-level DFD
3. 2-Level DFD

7. Data flow diagram
Context Level or 0-level DFD 1-level DFD

8. 2- LEVEL DFD

9. Logical Design
 EMPLOYEES: In this part we are covering that
how the employees are working in reservation
section of railway. In this all the details related
to employee’s.
 Emp_name
 Emp_id
 Address
 Gender
 Phone no
 Date joined
 Salary
 Designation
 Duty_shift
EMPLOYEE TABLE

10. CUSTOMER
In this part we are covering all the details
related to customer required for
reservation.
 Customer_name
 Customer_id
 Address
 Age
 Gender
 Phone_no
CUSTOMER TABLE

11. Ticket
 This is the part where we are covering the
tickets detail. It includes many attributes
like id of tickets, class, fare, source
stations, destination station etc. Ticket can
be booked online as well as onsite.
 PNR-no
 Ticket_num
 Source and destination
 Class
 Fare
 Train_id
 Seat_id
TICKET TABLE

12. Train
 In this part we are covering all the details
related to the trains. We are covering
train no, train name, no. of passengers
traveling through train, classes is train,
Route through which the train is going.
 The trains source and destination etc.
what are the different trains are going
and coming at one station in one day?
 Train_name
 Train_num
TRAIN TABLE

13. FORM
 Forms are the most important part of
reservation. Forms are the source to
know the details of the customers
 Form_name
 Form_id
FROM TABLE

14. TIME
 In this part all the details related
to time are covered.This includes
 Departure time
 Train_id
 Arrival time
 Each train has different time. It
can be in morning orevening or
night.
TIME TABLE

15. E-R DIAGRAM
create table TRAIN(
train_no INTEGER PRIMARY KEY,
train_name varchar(30),
AMOUNT INTEGER NOT NULL,
TC_NAME VARCHAR(20),
train_date DATE
);
create table PASSENGER( pnr_no
INTEGER PRIMARY KEY,
train_name varchar(30),
passenger_name varchar(30),
passenger_age int(3) NOT NULL,
COACH_no INTEGER NOT NULL,
train_date DATE
);
SQL queries

16. ADVANTAGES & DISADVANTAGES
 Dependable
 Better Organised
 High Speed over Long Distances
 Suitable for Bulky and Heavy Goods
 Safety
 Larger Capacity
 Employment Opportunities
 Administrative Facilities of
Government
 Huge Capital Outlay
 Lack of Flexibility
 Unsuitable for Short Distance and
Small Loads
 Booking Formalities
 No Rural Service
 Centralised Administration
ADVANTAGES DISADVANTAGES

17. CONCLUSION
 In the conclusion we are glad to inform that the proposed system
implementation and testing has been completed successfully. The proposed
system successfully avoids the unfair seat allotment practice of the waiting
list passengers after the chart has been prepared. It is also proven that the
system is user friendly and very easy to use. The proposed system is
designed in such a way that it can book multiple tickets by multi users at
the same time. The scheduling algorithm FCFS used has made the seat
allotment easier and faster. With the help of the proposed system we hope
to reduce the corruption and the unfair seat allotment to the waiting list
passengers

18. THANK YOU