The document describes a railway reservation and management system project. The system will manage a website that allows public interaction and services like train inquiries, seat availability checks, ticket booking and cancellations, and complaints. It will use a database of train timings and fares to calculate journey plans, expenses, and more. The system architecture includes backend databases modeling train, station, and user data and their relationships, an application program to perform calculations, and a frontend website for reservations and other functions.

1. Railway Reservation and
Management System
P
R
O
J
E
C
T
By
Aakarsh Mohan and
Shashanker Das

2. Introduction
Railway Reservation and management system manages a railway website
that provides public interaction and services.
Project’s scope is about how to use predefined railway timetable data and
use it to manage your journey plans, give you a brief idea about trains
available for public services and writing complaints for bad services of
railways.

3. Main Idea
Main idea behind the project is having a database related to train timings,
possible fair of journey and possible trains between two stations.
People can come and do ….
» Train enquiries
» Seat availability in trains
» Booking tickets for their journey
» Journey Expenditure
» Cancelation of pre-booked tickets
» Complaints regarding railway management and staff etc.

4. Relations
Primarily we’re going to require relations having all the details of the
available trains and stations that would be
» Trains
» Stations
» Administration
Then data of all the individual trains and stations lets say
» Train_#Train_no
» Station_#Station_code
Finally we come to the reservation lists of people
» Confirmed_reservation
» Waiting_reservation

5. Schema : Trains
The data in the train table would be all the basic information about all the
trains available.
Trains
Train_no Numeric 5
Train_name Varchar 40
Train_type Varchar 15
Superfast Boolean
{Available _classes} Varchar
{Working_days} Varchar

6. Schema : Stations
The data in the stations table will have all the basic information about all
the station.
Stations
Station_code Varchar 5
Station_name Varchar 40
Station_type Varchar 1
Zone Varchar 2

7. Schema : Administration
Administration table will contain the data regarding the administration of
the station and will also allow people to write online complains to the
proper personnel regarding any inconvenience or service issue.
Administration
Station_code Numeric 5
Sr_station_master Varchar 40
Jr_station_master Varchar 40
Executive_engineer Varchar 40
Station_budget Numeric 10
Catering_Incharge Varchar 40

8. Schema : Train_#Train_no
The following table will contain the data of all the station the train passes
through plus the distance from the origin station and the accurate timings
of arrival and departure from any station on the way.
Later the relation can be used to calculate journey expenses and travel
time of passengers.
Train_#Train_no
Station_code Varchar 5
Arrival _time Time
Departure_time Time
Distance_travelled Numeric 4

9. Schema : Station_#Station_code
Table will represent data of all the trains passing through any possible
station .
Station_#Station_code
Train_no Numeric 5

10. Schema : Confirmed_reservation
The data of the passenger got a confirm reservation in their respective
trains.
Confirmed _reservation
PNR_no Numeric 15
Coach Varchar 2
Birth Numeric 2
Passenger_name Varchar 40
Passenger_age Numeric 3
Passenger_gender Varchar 1
Train_no Numeric 5
Starting_station Varchar 5
Ending_station Varchar 5
Quota Varchar 2
Mobile_no Numeric 10

11. Schema : Waiting_reservation
The data of the passenger didn’t get a confirm reservation in their
respective trains and they are in the waiting list.
Confirmed _reservation
PNR_no Numeric 15
Waiting_no Numeric 3
Passenger_name Varchar 40
Passenger_age Numeric 3
Passenger_gender Varchar 1
Train_no Numeric 5
Starting_station Varchar 5
Ending_station Varchar 5
Quota Varchar 2
Mobile_no Numeric 10

12. Entity Relationship Model
An entity relationship model of the following database is given in the
following page that describes the relationship among different entity
sets.

13. Stations Trains
Waiting _reservationConfirmed_reservation
Train_#Train_no_1 Train_#Train_no_2Station_#Station_code_2Station_#Station_code_1
Administration
admins C_list W_list
passes
have have contains contains
[Will have ‘n’ number of stations as entities] [Will have ‘n’ number of trains as entities]

14. Architecture
Back End
• Contains the
entire databases
of railways and
their relationship
models.
Application
Program
• Calculates the
journey fair
journey time and
distance travelled
and such
information.
Front End
• Contains the
PHP/XHTML page
for the
reservation site.
• Reservations,
cancelations,
enquires and
complaints can
be done.
There is a three level architecture involved in the database.

15. Process: Application Program
Application program would calculate the following things
» Distance Travelled
» Time of Journey
» Total fair of Journey
» Seat Allotment
» Waiting List auto Cancelation
» Refund Money Calculation
» Calculation of Concession etc.
[NOTE: The application program will also calculate some auto fill data like Time_of_Journey, complaint filling data
etc.]

16. Calculations
Travel fair would be calculated according to the distance travelled within
particular class of travel and deductions regarding respective quotas.
That would be….
» SC (Senior Citizen)
» PH (Physically handicapped)
» Military Personnel etc.
The calculations would be like
Travel expense = (Total distance travelled)*(Per kilometer charge)
- Deductions(Calculated w.r.t percentage)

17. Front End
Menus
» Reservation : for new reservations
» Cancelation of ticket : for existing confirmed/waiting.
» Complaints : regarding facilities provided by railways.

18. Process: Reservation
Step II Step III
Selection
of train
Selection
of Class
Starting
Station
Date of
Journey
Ending
Station
Personal
info +
Payment
of money
Step I

19. Process: Cancelation
Partial
• Cancelling Tickets of ticket of some
particular passengers under the same
PNR no
• Requires details of PNR and name age sex
and seat no of the particular passenger.
Complete
• Cancelation of tickets of all
passengers under the same PNR no
• Requires PNR no
Auto
• If a passengers ticket doesn't get
confirmed in the final chart of the train
then requires an auto cancelation of
ticket.
• All ticket from waiting list whose time of
journey is past.
Cancelation

20. Process: Complaints
1
2
3
Open the complaint portal and fill up your personal
entries for example train no, date of journey etc.
Fill the details of the department you’re having
complaints with and describe your problem.
Click on submit, an automatic complaint application will
generate on your behalf and it will be sent to the
designated officer.

21. Any Questions ?

22. Thank You