Post on 04-Apr-2015
ONLINE RAILWAY RESERVATION SYSTEM
Rakesh Kumar Shah IIT2009018Bijay Dhital IIT2009025Prashish Rajbhandari IIT2009031Rishi Gosai IIT2009130Avishek Pant IIT2009134
PROBLEM STATEMENT
Information about the route, cancellation of tickets, departure time, arrival time, number of trains available and other such information.Store and retrieve information about the various transactions related to Rail travel.Keep track of all its passengers and thus schedule their journey accordingly.Maintains records of passengers travelling in the different trains on different dates reaching different destinations in the system.User friendly interface to administrator and customer
ER DIAGRAM
USER TRAIN CLASS
TICKET-1 FARE PAYMENT
TICKET-2
FUNCTIONS OF USER
Train Enquiry Book Ticket Payment Check PNR Status Cancel Ticket Login and Logout
FUNCTIONS OF ADMIN
Add/Remove Trains Add/Remove User Book Ticket Cancel Ticket Get Passenger List Login and Logout
Tables and Normalization
username
password
first_name
last_name
age email Registration-date
username
password
first_name
last_name
age email Registration-date
Admin table
The above table consists of username as a primary key which determines all other attributes of it. There is no partial and transitive dependency so it is in 3NF.
The above table consists of username as a primary key which determines all other attributes of it. There is no partial and transitive dependency so it is in 3NF.
User table
train_no train_name
source destination
distance
arrival_time
dep_time
Train table
Train number is the primary key of train table . It consists of atomic values of attributes and there is no partial and transitive dependency so it is in 3NF.
PNR
train_no
train_name
source
destination
distance
class
fare
arrival_time
departure_time
Name
date
seat_no
Ticket table
train_no train_name
source destination
distance
arrival_time
dep_time
Train_details
train_no class fare
Fare table
1 NF – 3 NF conversion of Train table
PNR train_no
name date seat_no
class fare
Ticket _details
PNR train_no
name date seat_no
class
Ticket1 table
PNR fare
Ticket2 table
train_no
General
Sleeper
Ac I Ac II Ac III
Class_details
receipt_no
username
card_no pin_no bank type
Payement table
DFD (Data Flow Diagram)
3 Level Diagram
-Level 0-Level 1-Level 2
Level 0
User Level 1
Admin Level 1
User Level 2
Admin Level 2
TRIGGERS
If user has entered data in payment, send a trigger to change the value of paid field in ticket (initially set at zero).
Confirmation mail to be sent to the user on his email if he has cancelled the ticket or created an account.
When a new train is added to the train table the fare table should also be updated.
Snapshots
THANK YOU PLEASE VIEW OUR
DEMO