MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION
VIDYA VARDINI’S
BAHUSAHEB VARTAK POLYTECHNIC
MICRO PROJECT
ACEDEMIC YEAR: 2019-20
ER DIAGRAM OF RAILWAY
RESERVATION SYSTEM
PROGRAM/CODE: COMPUTER ENG (CO) SEMESTER: 3
COURSE/CODE: DATABASE MANAGEMENT SYSTEM (22319)
NAME OF FACULTY: PROF.
ROLL NO. NAME ENROLLMENT NO.
MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION
CERTIFICATE
THIS IS TO CERTIFY THAT MR./MS.
........................................................................................................................…………
ROLL NO. .............. OF THIRD SEMESTER OF DIPLOMA IN COMPUTER ENGINEERING
OF INSTITUTE, B.V.POLYTECHNIC (CODE: 0093) HAS COMPLETED THE MICRO PROJECT
SATISFACTORILY IN SUBJECT- DATABASE MANAGEMENT SYSTEM (22319) FOR THE
ACEDEMIC YEAR 2019-20 AS PRESCRIBED IN THE CURRICULUM.
PLACE: .......................... ENROLLMENT NO. :
........................................
DATE: ............................ EXAM. SEAT NO. :
..........................................
SUBJECT TEACHER HEAD OF THE DEPARTMENT PRINCIPAL
Seal of institution
WEEKLY ACTIVITY SHEET
INSTITUTE CODE:0093/ ACADEMIC YEAR: 2019-20
PROGRAM: SYCO2 ENGINEERING ROLL N0.
COURSE &CODE: DATABASE MANAGEMENT SYSTEM (22319)
NAME OF CANDIDATE :
SEMESTER: III NAME OF FACULTY: PROF.PREETI AWARE
SR. WEEK ACTIVITY PERFORMED DATE SIGN OF
NO FACULTY
1 1st Discussion and finalization of
topic
2 2nd Literature review
3 3rd Collection of data
4 4th Collection of data
5 5th Discussion and outline of
content
6 6th Formulation of content
7 7th Editing and proof reading of
content
8 8th Compilation of report
9 9th Report presentation
10 10th Final submission of micro
project
RUBRIC FOR EAVLUATION ON MICRO PROJECT
INSTITUTE CODE: 0093 ACADEMIC YEAR: 2019-20
PROGRAM: SYCO2 COURSE CODE: 22319
SEMSTER: 3 NAME OF FACULTY: PROF. PREETI AWARE
SR. CHARACTERISTICS TO BE ASSESSED POOR AVERAGE GOOD
NO (1-2) (3-4) (5-6)
01 LITERATURE SURVEY/REFERENCE
02 PROJECT PROPOSAL/REPORT/CONTENT
03 RELEVANCE TO THE COURSE
04 PLANNING AND TIMELY COMPLETION OF
TARGET
05 ANALYSIS OF DATA/REPRESENTATION
06 QUALITY OF PROTOTYPE/MODEL
07 TOTAL MARKS FORM ASSESMENT OF MICRO PROJECT (OUT OF
6)
08 MARKS OBTAINED IN INDIVISUAL PRESENTATION (OUT OF 4)
09 TOTAL MARKS(OUT OF 10)
SIGNATURE OF FACULTY SIGNATURE OF STUDENT
ANNEXTURE-II
EVALUATION SHEET FOR THE MICRO PROJECT
ACADEMIC YEAR: 2018-19 NAME OF FACULTY: PROF. PREETI AWARE
COURSE CODE: 22319 SEMESTER: 3
COURSE: DATABASE MANAGEMENT SYSTEM.
TITLE OF PROJECT : ER Diagram for Railway Reservation System
CO’s addressed by the Micro Project
Outcomes in affective domain:
A. ER Diagram for Railway Reservation System.
Comments/suggestions about team work/leadership/inter personal communication (IF ANY)
Roll. Enrollment Student name Marks out of 6 Marks out of 4 Total out
no No. for performance for of 10
in group activity performance
in group
activity
INDEX
SR. PAGE
NO. CONTENT NO.
1 Introduction of Railway Reservation 1
System
2 ER Diagram Railway Reservation 2
System
3 ER Diagram into Data tables 3,6
4 Entity Relationships 7
5 Conclusion 8
6 References 9
INTRODUCTION
The railway reservation system facilitates the passengers to enquire about the trains available on the
basis of source and destination, booking and cancellation of tickets, enquire about the status of the
booked ticket, etc.
The aim of case study is to design and develop a database maintaining the records of different trains,
train status, and passengers. The record of train includes its number, name, source, destination, and
days on which it is available, whereas record of train status includes dates for which tickets can be
booked, total number of seats available, and number of seats already booked.
ER Diagram of Railway Reservation System
Step 1: Converting the E-R Diagram into Tables
a. Converting entity to table and attribute to columns
USER
U_id Primary Key
Password Attributes
Security_quest Attributes
Train_Status
Status_id Primary Key
Wait_seat Attributes
Avail_seat Attributes
Booked_seat Attributes
Train_id Foreign key references to Train_id of Train Table
PNR Foreign key references to PNR of Passenger table.
Passenger:-
PNR Primary Key
P_name Attributes
Age Attributes
Gender Attributes
Seat_no. Attributes
Reserve_status Attributes
U_id Foreign key references to U_id of User table.
Status_id Foreign key references to Status_id of Train_Status Table.
Train_id Foreign key references to Train_id of Train Table
Station:-
Station_id Primary Key
Station_name Attributes
Route:-
Arr_time Attributes
Depart_time Attributes
Stop no. Attributes
Station_id Foreign key references to Station_id of Station table.
Train_id Foreign key references to Train_id of Train Table
Step 2 : Mapping of Attributes
a. Simple Attributes
Simple attributes which cannot be divided into subparts.
Example: Seat Number of passenger
b. Composite Attributes
Composite attributes which can be divided into subparts.
Example: Passenger Name, Reservation status
P_name
First_Name
Middle_Name
Last_name
Reserve_status
Waiting
Confirmed
Step 3: Mapping of entity set
a. Weak entity set
For each weak entity type with owner entity, create a table and include all simple attributes of weak
entity type as columns of table, including foreign key attributes as the primary key of the table that
correspond to the owner entity type.(Owner entity is strong entity having own primary key.)
Example: Route (Weak Entity) in Train (Owner entity).
Step 4: Mapping of Relationships
a. Foreign Key approach
Passenger_Table
U_id Passenger table makes foreign key references to U_id of User table.
Status_i Passenger table makes foreign key references to Status_id of Train_Status
d Table.
Train_id Passenger table makes foreign key references to Train_id of Train Table
Train_Status
Train_i Train_status table makes foreign key references to Train_id of Train Table
d
PNR Train_status table makes foreign key references to PNR of Passenger table.
Train
Route
Station_i Route table makes foreign key references to Station_id of Station table.
d
Train_id Route table makes foreign key references to Train_id of Train Table
Step 5: Identifying the relationships
a. Passenger can book many tickets.
Therefore the relations are 1……..N.
b. Trains are associated with each Train_status
Therefore the relation is M……..1.
c. Trains can route from one route.
Therefore the relations are N……..1.
d. Station has a set of Route.
Therefore the relations are 1……..N.
Conclusion
In our project Railway reservation system we have stored all the
information about the Trains scheduled and the users booking tickets and
even status of trains, seats etc. This data base is helpful for the
applications which facilitate passengers to book the train tickets and
check the details of trains and their status from their place itself it avoid
inconveniences of going to railway station for each and every query they
get. We had considered the most important requirements only, many
more feachers and details and be added to our project inorder to obtain
even more user friendly applications.
References
https://www.ques10.com/p/9477/draw-e-r-diagram-for-online-ticket-railway-reser-1/
http://www.muengineers.in/computer-project-list/java-projects-list/railway-reservation-system
