LECTURER

 MUHAMMAD AMJAD

GROUP MEMBERS:
 WAJIHA AMJAD
 MUHAMMAD USAMA ALI
 MUHAMMAD FAIZAN RAZA
 MUHAMMAD YASEEN KHAN
AGENDA
Introduction

Scope and feasibility

Technical Details

System Requirements

Data Flow Diagrams

Terminology

Oracle on Network
INTRODUCTION

This system is basically

In this we are discussing What are the rules and
concerned with the
that how the reservation regulations and procedure
reservation of railway
is done. for reservation
tickets to the passengers.

Apart from the industrial

applications, it is a
Hence, this can be used
To overcome many research-oriented
for suggesting
limitations, more efficient, project as well, the task of
improvements in design,
easy handling of data and performance evaluation
performance and greater
records of different database
usability.
designs, for efficiency, is in
this spirit.
In this project we are going to include all
the entities related to reservation.
 Employees DATABASE
 Customers
 Stations
 Trains TABLESPACE
 Forms
 Ticket
 Fare TABLES
 Class
 Time
SCOPE AND OBJECTIVE

All the manual work

should be converted into The database should be Easy to store information Centralized management
Accurate and timely
computerized so that the stored in computer rather and fast accessing of reporting & decision
control program.
load of employees should than in register/manually. information. support.
decrease.

To make it easy for fast To make the Railway

List of accounts of all
processing and Easy retrieval of accounts. system is interactive.
customers is available.
modification. Quick feed back.
TECHNICAL DETAILS

OS OTHER SOFTWARES
BACKEND
DATABASE PLATFORM PLATFORM

ORACLE 11 G WINOWS 7 RED HAT LINUX CHROME

ENTERPRISE SCREEN CASTER
EDITION 5 TEXT PAD
REQUIREMENTS

HARDWARE REQUIREMENT
 Processor : Pentium IV 2GHz and Above
RAM : 2GB
Monitor : VGA Color Monitor

SOFTWARE REQUIREMENT
Operating System : Windows XP onwards
Developing Tool : VB (front end)
Database : MS-ACCESS (back end)

LIMITATIONS
Data Redundancy
Difficulty in accessing the Data
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.
Context level or 0-level DFD
1-level DFD
2-Level DFD
CONTEXT LEVEL OR
0_LEVEL DATA FLOW
DIAGRAM

 PASSENGER
 RAILWAY RESERVATON
 ADMIN
FIRST LEVEL DATA
FLOW DIAGRAM

 PASSENGER
 TICKET GENERATE
 REPORT ADMIN
 ENQUIRY
SECOND LEVEL DATA
FLOW DIAGRAM

 RESERRVATION
 CONFIRMATION
 TICKET GENERATE
 REPORT GENERATE
LOGICAL DESIGN

EMPLOYEES:
In this part we are covering that how the Attribut Data Primary Foreign Constraints
employees are working in reservation section of
railway. In this all the details related to e type key key
employees.
Emp_name Char(10) Not null
 Emp_name
 Emp_id Emp_id Number Pk Primary key
 Address
Address Varchar(50) Not null
 Gender
Gender Char(10) ‘f’,’m’,‘F’,’M’
 Phone no
 Date joined Phn_no Number(10) Not null
 Salary
Date_ joined Date(8) Not null
 Designation
Duty_shift Time(10) Not null
 Duty _shift
CUSTOMER
Attribut Data Primary Foreign Constraints
In this part we are covering all the e type key key
details related to customer cust_name Char(10) Not null
required for reservation.
cust_id Number(10) Pk Primary key
 Customer_name
Ticket_num Number(50) Ticket(ticket_id) Not null
 Customer_id
Gender Text(8) ‘f’,’m’,‘F’,’M’
 Address Phn_no Number(10) Not null

 Age Emp_id Number(8) Employee Not null

(emp_id)
 Gender
Form_id Number(10) Form(form_id) Not null
 Phone no
TICKET Attribute Data type Primary Foreign key Constraints
key

This is the part where we are covering Ticket_num Number(10) Pk Primary key
the tickets detail. It includes many
attributes like id of tickets, class, fare, P.N.R_No. Number Not null
source stations, destination station etc
Ticket can be booked online as well as Source Text Not null
onsite.
Destination Text Not null
 PNR_no
 Ticket_num Class_id Number (10) Class(class_id) Foreign key

 Source and destination Fare Number(10) Not null

 Class
Train_id Number(8) Train(train_id) Not null
 Fare
Seat_id Number (10) Not null
 Train_id
 Seat_id
STATION
Attribute Data type Primary Foreign Constraints
In this part we are covering the key key
details of the station ex; station
name, number of trains passing or Stn_name Text(10) Not null
going from that station or coming
No_of_ Number (10) Not null
to that station. Number of
lines
platforms, number of lines.
Stn_id Number(10) Pk Primary key

 Station_name No_of Number (10) Not null

_platform
 No. Of lines
 Station_id
 No. Of platforms
TRAIN

Attribute Data type Primary Foreign key Constraints

In this part we are covering all the key
details related to the trains. We are
covering train no, train name, no. of Stn_id Number (10) Station(stn_id) Foreign key
passengers traveling through train,
classes is train, Route through which Trn_name Text (10) Not null
the train is going.
 The trains source and Trn_id Number(10) Pk Primary key
destination etc. what are the
different trains are going and Ticket_num Number (10) Ticket Foreign key
coming at one station in one (ticket_num)
day?
 Train_name
 Train_num
FORM

Forms are the most important Attribut Data Primary Foreign Constraints
part of reservation. Forms are the e type key key
source to know the details of the
customers. Form name Text(10) Not null

 •Form_name Form_id Number Pk Primary key

(10)
 •Form_id
cust_id Number Customer Foreign key
(10) (cust_id)
CLASS

In this part we are covering the Attribut Data Primary Foreign Constraints
different types of classes that is: e type key key
 1st class Date Number(10) Not null

 2nd class Trn_id Text Train(trn_id) Foreign key

 Sleeper class No_of_seats Text Not null

 General class Class_id Number (10) Pk Primary key

 So, the price depends upon the

class the customer selects.
General class is the cheapest.
FARE

AT T R I BU T E DATA P R I M A RY FOREIGN CONSTRAINT

TYPE KEY KEY S
Fare is the charges spent by the
customer. Fare is decided according Trn_id Number(10) Not null

to the train which is selected by the Source Text (10) Not null

customer. Destination Text (10) Not null

 For example- We take the Class Text (10) Not null

example of different trains going Fare Text(10) Not null

from Ludhiana and their different Ticket_num Number(8) Ticket Foreign key
charges/fare. (ticket_num)

 Shtabadi Receipt_num Number (10) Pk Primary key

 7:00am and 7:00pm

 Chair car – Rs 450/ -
 1st class – Rs 1099
TIME

Attribut Data Primary Foreign Constraints

In this part all the details related e type key key
to time are covered. This includes:
Ref_no Number(10) Pk Primary key
 Departure time
Dep_time Date/time (8) Not null
 Train id Arrival_time Date/time (8) Not null

 Arrival time Train_id Number (10) Train(trn_id) Foreign key

 Each train has different time. It Stn_id Number(10) Station(trn_id) Foreign key
can be in morning or evening
or night.
ENTITY RELATIONSHIP DIAGRAM
CONCLUSION

This summer training helped us

Practical Training is a very
learn a lot. In this training we did
important part of the curriculum
the project on railway reservation
as it strengthens the concepts and
system. This project is used to keep
enhances knowledge about the
a track on reserving the seat to
practical implementation of all the
the passenger. It helps managing
theory concepts, we have learnt so
the system very efficiently and
far in different subjects.
conveniently.