CENTRL UNIVERSITY OF BIHAR

Project report
On
TOPIC: ONLINE RAILWAY RESERVATION SYSTEM
Submitted by Submitted to
Shubham Gupta Dr. Prabhat Ranjan

MSc. CS 2nd sem Dept.t of CS

Dept.t of CS CUB Patna

CUB Patna




ONLINE
RESERVATION
SYSTEM FOR
RAILWAY



TABLE OF CONTENTS
TOPICS PAGE NO.

1. OBJC!"# $
2. "%!RODUC!"O% &BOU! !' SO(!)&R *
+. S,S!M D#-OPM%! -"( C,C- .
$. SO(!)&R R/U"RM%! SPC"("C&!"O% 0
*. US C&S D("%"!"O% 1$
.. US C&S D"&GR&M 1*
0. US C&S DSCR"P!"O% 1.
1. R D"G&R&M 10
2. D&!& (-O) D"&GR&M 11
13. S/U%C D"&GR&M 23
11. -"M"!&!"O% 4 (U!UR SCOP 21




OBJECTIVE
Our project 5ntroduces ra567a8 reser9at5on s8stem 75th an object59e to ma:e the reser9at5on s8stem more eff5c5ent; eas5er and fast.
!h5s project e<p6ores ho7 computer techno6o=8 can be used to so69e the prob6em of user.
!he ma5n object59es pro95ded b8 th5s soft7are are as fo66o7s>
)e can en?u5re about a9a56ab565t8 of tra5ns
)e can reser9e and cance6 the5r seats
)e can mod5f8 the 5nformat5on re6ated to
a@ !ra5ns
1@ !5metab6e
2@ !ra5n %ame
+@ !ra5n %umber
b@ !5c:et (are
!h5s project 5s ded5cated to mode6 e<5st5n= ra567a8 reser9at5on s8stems that a5m at de9e6opment of Ra567a8 Reser9at5on S8stem that
fac565tates the ra567a8 customer to mana=e the5r reser9at5ons and the ra567a8 adm5n5strator to mod5f8 the bac:end database 5n a userA
fr5end68 manner.



INTRODUCTION
"n th5s emer=5n= 7or6d of computers; a6most a66Amanua6 s8stem has s75tched to automated and computer5Bed s8stem. !herefore; 7e
are de9e6op5n= the soft7are for CRa567a8 Reser9at5on S8stemD to mode6 the present s8stem and to remo9e the dra7bac:s of the
present s8stem. !h5s project e<p6ores ho7 computer techno6o=8 can be used to so69e the prob6em of user.
!h5s be5n= a b5= step 5n terms of 5mpro9ement 5n the ra567a8 s8stem 5t 5s 75de68 accepted across the countr8. Rather than des5=n5n=
manua668; 7e ha9e made use of computer. Use of computer has so69ed man8 prob6ems; 7h5ch are faced dur5n= manua6 ca6cu6at5on.
Once data are feed; 5t can perform accurate funct5ons. !herefore; to reduce the comp6e<5t8 and eff5c5enc8 a 9ersat56e and an
outsourc5n= ra567a8 reser9at5on s8stem has been de9e6oped.
!h5s project 5ntroduces ra567a8 reser9at5on s8stem. "t e<p6a5ns ho7 reser9at5on 5s be5n= done 5n "nd5an Ra567a8s. !he s8stemat5c
procedure 5s e<p6a5ned. !h5s project 5s de9e6oped 5n &sp.net 6an=ua=e. &66 most a66 the header f56es ha9e been used 5n th5s project.
Proper comments ha9e been =59en at des5red 6ocat5ons to ma:e the project user fr5end68. #ar5ous funct5ons and structures are used to
ma:e a comp6ete use of th5s 6an=ua=e.
!he customers are re?u5red to re=5ster on the ser9er for =ett5n= access to the database and ?uer8 resu6t retr5e9a6. Upon re=5strat5on;
each user has an account that 5s essent5a668 the E95e7 6e9e6F for the customer. !he account conta5ns comprehens59e 5nformat5on of the
user entered dur5n= re=5strat5on and perm5ts the customer to =et access to h5sGher past reser9at5ons; en?u5re about tra9e6 fare and
a9a56ab565t8 of seats; ma:e fresh reser9at5ons; and update h5s account deta56s. ach passen=er 5s a66otted a un5?ue P%R no. throu=h
7h5ch one can access h5sGher account.
!he ra567a8 adm5n5strator 5s another member 5n9o69ed 5n the transact5ons. !he adm5n5strator 5s re?u5red to 6o=5n us5n= a master
pass7ord; once authent5cated as an adm5n5strator; one has access and r5=ht of mod5f5cat5on to a66 the 5nformat5on stored 5n the
database. !h5s 5nc6udes the account 5nformat5on of the customers; attr5butes and stat5st5cs of stat5ons; descr5pt5on of the tra5n
stoppa=es and ph8s5ca6 descr5pt5on of coaches; a66 the reser9at5ons that ha9e been made. !he ra567a8 adm5n5strator has the r5=ht to
mod5f8 an8 5nformat5on stored at the ser9er database.
!h5s project 5s ded5cated to mode6 the e<5st5n= ra567a8 reser9at5on s8stem that a5ms at de9e6opment of Ra567a8 Reser9at5on S8stem
that fac565tates the ra567a8 customer to mana=e the5r reser9at5ons and the ra567a8 adm5n5strator to mod5f8 the bac:end database 5n a
userAfr5end68 manner. !he customer and the ra567a8 adm5n5strator are t7o part5es that 5nteract 75th the database; 7ho ha9e d5fferent
E95e7 6e9e6 schemasF to the database 5nformat5on. !he soft7are pro95des a comprehens59e set of features to enhance the operat5ona6
65m5ts.
%o7 one can eas568 p6an the journe8 comfortab68 as the process 5s eff5c5ent and fast 75th be5n= eas8 to access. !he eff5c5enc8 of the
ra567a8 7566 5ncrease resu6t of computer5Bat5on.



System development life cycle
SPIRAL MODEL
!he sp5ra6 mode6 5s used to de9e6op Ra567a8 Reser9at5on; 75th more emphases p6aced on r5s: ana68s5s. !he sp5ra6 mode6 has four
phases> P6ann5n=; R5s: &na68s5s; n=5neer5n= and 9a6uat5on. & soft7are project repeated68 passes throu=h these phases 5n 5terat5ons
Hca66ed Sp5ra6s 5n th5s mode6@. !he base65ne sp5ra6; start5n= 5n the p6ann5n= phase; re?u5rements 5s =athered and r5s: 5s assessed.
ach subse?uent sp5ra6 bu56ds on the base65ne sp5ra6.
Re?u5rements are =athered dur5n= the p6ann5n= phase. "n the r5s: ana68s5s phase; a process 5s underta:en to 5dent5f8 r5s: and a6ternate
so6ut5ons. & protot8pe 5s produced at the end of the r5s: ana68s5s phase.
Soft7are 5s produced 5n the en=5neer5n= phase; a6on= 75th test5n= at the end of the phase. !he e9a6uat5on phase a66o7s the customer
to e9a6uate the output of the project to date before the project cont5nues to the ne<t sp5ra6.
"n the sp5ra6 mode6; the an=u6ar component represents pro=ress; and the rad5us of the sp5ra6 represents cost.
Spiral Life Cycle Model

Advantages
High amount of risk analysis
Good for large and mission-critical projects.
Software is produced early in the software life cycle.
Disadvantages
Can be a costly model to use.
isk analysis re!uires highly specific e"pertise.
#roject$s success is highly dependent on the risk analysis phase.
%oesn$t work well for smaller projects.
&nd that$s it. 'f you ha(e any input) especially your (iews on ad(antages and disad(antages of any particular model) feel free
to lea(e them in the comments and ' can add them to my copy.



SOFTWARE REQUIREENT SPECIFICATION
& Soft7are Re?u5rement Spec5f5cat5on HSRS@ 5s a re?u5rements spec5f5cat5on for a soft7are s8stem that 5s a comp6ete descr5pt5on of
the beha95or of a s8stem to be de9e6oped. "t 5nc6udes a set of use cases that descr5be a66 the 5nteract5ons the users 7566 ha9e 75th the
soft7are. Use cases are a6so :no7n as funct5ona6 re?u5rements. "n add5t5on to use cases; the SRS a6so conta5ns nonAfunct5ona6 Hor
supp6ementar8@ re?u5rements. %onAfunct5ona6 re?u5rements are re?u5rements that 5mpose constra5nts on the des5=n or 5mp6ementat5on
Hsuch as performance en=5neer5n= re?u5rements; ?ua65t8 standards; or des5=n constra5nts@.
!he 5n5t5a6 spec5f5cat5ons of user re?u5rements ma8 be based on 5nter95e7s 75th the database users and on the des5=ners o7n ana68s5s
of the enterpr5se. !he bas5c 5ssues that the SRS 7r5terHs@ sha66 address are the fo66o75n=>
(unct5ona65t8>
)hat 5s the soft7are supposed to doI
<terna6 5nterfaces.
'o7 does the soft7are 5nteract 75th peop6e; the s8stemFs hard7are; other hard7are; and other soft7areI
Performance.
)hat 5s the speed; a9a56ab565t8; response t5me; reco9er8 t5me of 9ar5ous soft7are funct5ons; etc.I
&ttr5butes.
)hat 5s the portab565t8; correctness; ma5nta5nab565t8; secur5t8; etc. cons5derat5onsI
&n SRS shou6d be>
a@ Correct
b@ Unamb5=uous
c@ Comp6ete
d@ Cons5stent
e@ Ran:ed for 5mportance andGor stab565t8
f@ #er5f5ab6e
=@ Mod5f5ab6e
h@ !raceab6e



!. INTRODUCTION"
!he manua6 s8stem of t5c:et reser9at5on ta:es more t5me and the number of reser9at5ons per da8 5s 65m5ted. !o 5ncrease the eff5c5enc8
of the process; 7e =o for on65ne t5c:et reser9at5on s8stem. !h5s s8stem supports on65ne t5c:et boo:5n=
&n on65ne reser9at5on s8stem 5s soft7are that he6ps 5n reser9at5on of ra567a8 t5c:ets 5n the 5nternet and chec: for the a9a56ab565t8 of
t5c:ets. !h5s s8stem sho7s a66 the 5nformat5on about a66 the transport ser95ces 5nc6ud5n= the5r source and dest5nat5on; and the t5me of
arr59a6 and departure of a66 tra5ns and the a9a56ab565t8 of seats 5n a66 the tra5ns. !h5s s8stem a6so has the fac565t8 of cance66at5on of
t5c:ets. "f the t5c:ets are not a9a56ab6e; then the current status of the s8stem 5s a6so :no7n throu=h th5s s8stem. !he on65ne reser9at5on
s8stem ma5nta5ns the fu66 deta56s of the ent5re passen=er 7ho are reser95n= the t5c:ets 5n the spec5f5ed ra567a8 ser95ces.
!.!.PURPOSE"
!he purpose of th5s soft7are 5s to descr5be the Ra567a8 Reser9at5on S8stem 7h5ch pro95des the ra56 t5m5n= deta56s;
reser9at5on; en?u5r8; b5665n= and cance66at5on on 9ar5ous t8pes of reser9at5on name68>A
Conf5rm reser9at5on for conf5rm seat
Reser9at5on a=a5nst cance66at5on
P%R =enerat5on
!.# SCOPE

!he manua6 s8stem of t5c:et reser9at5on ta:es more t5me and the number of reser9at5ons per da8 5s 65m5ted.
!o 5ncrease the eff5c5enc8 of the process; 7e =o for on65ne t5c:et reser9at5on s8stem.
!h5s s8stem supports on65ne t5c:et boo:5n=.
!.$ OVERVIEW"
!h5s project a5ms at de9e6opment of a Ra567a8 Reser9at5on S8stem that fac565tates the Ra567a8 customers to mana=e the5r
reser9at5ons and the Ra567a8 adm5n5strators to mod5f8 the bac:end databases 5n a UserA(r5end68 manner.
!h5s project 5nc6udes the fo66o75n= funct5ons>
1@ Create ne7 database
2@ &dd ne7 Record
+@ Mod5f8
$@ D5sp6a8 record
*@ !5c:et reser9at5on
.@ !5c:et Mod5f5cat5on



0@ !5c:et Cance66at5on
1@ !5c:et pr5nt5n=



#. T%E OVERALL DESCRIPTION"
#.!.PRODUCT PERSPECTIVE"
"t enab6es us to ma5nta5n the ra567a8 tra5n deta56s 65:e the5r t5m5n=s; number of seat a9a56ab6e; reser9at5on b5665n= and
cance665n= the t5c:ets.
#.!.!. OPERATIONS"
&n8 Reser9at5on counter from 1 am to 1 pm.
One form for f59e persons.
!o sa9e t5me and ?ueue &=ents are other =u5des.
#.#.PRODUCT FUNCTIONS"
"t te66s the short note about the product.
2.2.1. !R&"% D!&"-S>
Customers ma8 95e7 the tra5n number; tra5n name; tra5n t5m5n= Harr59a6 and departure@; arr59a6 and departure stat5on
of the tra5n and number of seats re?u5red.
2.2.2. RSR#&!"O%>
&fter chec:5n= the number of seats a9a56ab6e; the customers reser9e the t5c:ets.
2.2.+. B"--"%G>
&fter reser95n= the re?u5red number of t5c:ets; the customer pa5d the fare.
2.2.$ C&%C--&!"O%>
"f the customer 7ants to cance6 the t5c:et; he can cance6 5t us5n= P%R number.
#.$.USER C%ARACTERISTICS"
Jno76ed=eab6e User
%o95ce User



<pert User
#.&.CONSTRAINTS"
!here 5s no ma5nta5nab565t8 of bac: up so a9a56ab565t8 7566 =et affected. Rea6A65fe cred5t card 9a65dat5on and Ban:5n= s8stem
5s not 5mp6emented. %o mu6t565n=ua6 support. G59en be6o7 5s an o9era66 p5cture of the s8stem; as dep5cted 5n the abo9e
&dm5n5strator>

Database Mana=ement>
Contro6 the database customers and :eep trac: of a66 records of customers.
Contro6 the database of tra5ns and :eep trac: of a66 records of tra5n.
Contro6 fare mana=ement.
#5e7 the deta56s of a66 orders and contro6 the 7ho6e app65cat5on

Customers>
-o=5n>
Customers must ha9e a 9a65d 6o=5n 5d HP%R number@ to enter 5nto the s5te.
Re=5strat5on>
%e7 users can s5=n up b8 creat5n= ne7 "D.
Cance6 Deta56s
Can cance6 h5s reser9at5on deta56s.
$. SPECIFIC REQUIREENTS"
Conf5rm Reser9at5on for conf5rm Seat.



Reser9at5on a=a5nst Cance66at5on
.
)a5t5n= 65st Reser9at5on.
On65ne Reser9at5on.
!at:a6 Reser9at5on.
Pr5nt G95e7 t5c:et
Chec: Reser9at5on Status




$.!.E'TERNAL INTERFACES"
Boo:5n= !erm5na6s
n?u5r8 !erm5na6s
$.#.PERFORANCE REQUIREENTS"
"tFs a9a56ab6e dur5n= a66 2$ hours.
#ar5et8 of compartments based on comfort>
&C
%onA&C
Genera6
!8pes of concerns and comp6e<5t5es>
13 t8pes of tra5ns
+ t8pes of c6asses
$.$.SOFTWARE S(STE ATTRIBUTES"
Re65ab6e
&9a56ab6e
Secure
Portab6e



$.&.FUNCTIONAL REQUIREENTS"
"n soft7are en=5neer5n=; a funct5ona6 re?u5rement def5nes a funct5on of a soft7areAs8stem or component. & funct5on 5s
descr5bed as a set of 5nputs; the beha95or and outputs. (unct5ona6 re?u5rements ma8 be ca6cu6at5ons; techn5ca6 deta56s; data
man5pu6at5on and process5n= and other spec5f5c funct5ona65t8 that sho7 ho7 a use case to be fu6f566ed. !8p5ca668; a
re?u5rements ana68st =enerates funct5ona6 re?u5rements after bu56d5n= use cases. 'o7e9er; th5s ma8 ha9e e<cept5ons s5nce
soft7are de9e6opment 5s an 5terat59e process and somet5me certa5n re?u5rements are conce59ed pr5or to the def5n5t5on of the
use case. Both art5facts Huse cases documents and re?u5rements documents@ comp6ement each other 5n a b5d5rect5ona6
process. & t8p5ca6 funct5ona6 re?u5rement 7566 conta5n a un5?ue name and number; a br5ef summar8; and a rat5ona6e. !h5s
5nformat5on 5s used to he6p the reader understand 7h8 the re?u5rement 5s needed; and to trac: the re?u5rement throu=h the
de9e6opment of the s8stem. !he core of the re?u5rement 5s the descr5pt5on of the re?u5red beha95or; 7h5ch must be a c6ear
and readab6e descr5pt5on of the re?u5red beha95or. !h5s beha95or ma8 come from or=an5Bat5ona6 or bus5ness ru6e; or 5t ma8 be
d5sco9ered throu=h e65c5tat5on sess5ons 75th users; sta:eho6ders and other e<perts 75th5n the or=an5Bat5on. Soft7are
re?u5rements must be c6ear; correct unamb5=uous; spec5f5c and 9er5f5ab6e.
$.&.!. RESERVATION OF TIC)ET"
R/US! !"M !&B->
Passen=er re?uests database to d5sp6a8 ra567a8 t5metab6e.
D"SP-&, !"M!&B->
Database d5sp6a8s t5metab6e to the customer.
R/US! !O RSR# !"CJ!>
Passen=er re?uests the c6er: to reser9e h5sGher t5c:et.
"%PU! D!&"-S>
C6er: as:s customer to enter deta56s for the reser9at5on of t5c:et.
C&-CU-&! (&R>
C6er: ca6cu6ates the tota6 fare of the journe8 accord5n= to the number of passen=ers and te66s the customer.
RSR# !"CJ!>
!5c:et 5s reser9ed and customer pa8s the fare.
R/US! !O PR"%!>
Customer re?uests to pr5nt the t5c:et.



PR"%! !"CJ!>
!5c:et 5s been pr5nted and hand6ed to the customer.
$.&.#. CANCELLATION OF TIC)ET"
R/US! !O C&%C- !"CJ!>
Customer re?uests to cance6 h5sGher t5c:et for 7h5ch heGshe has to =59e the P%R number.
C&%C- !"CJ!>
Once the P%R number 5s rece59ed; the t5c:et 5s cance66ed.
$.*.NON+FUNCTIONAL REQUIREENTS"
"n s8stems en=5neer5n= and re?u5rements en=5neer5n=; nonAfunct5ona6 re?u5rements are re?u5rements that spec5f8 cr5ter5a that
can be used to jud=e the operat5on of s8stem; rather than spec5f5c beha95ors. %onAfunct5ona6 re?u5rements are often ca66ed
?ua65t5es of a s8stem. Other terms for nonAfunct5ona6 re?u5rements are Cconstra5ntsD;
D?ua65t8 attr5butesD; C?ua65t8 =oa6sD and C?ua65t8 of ser95ce re?u5rementsD .
/ua65t5es; 5.e. nonAfunct5ona6 re?u5rements can be d595ded 5nto 2 ma5n cate=or5es>
1. <ecut5on ?ua65t5es such as secur5t8 and usab565t8 are obser9ab6e at run t5me.
2. 9o6ut5on ?ua65f5es; such as e<tens5b565t8 and sca6ab565t8 embod8 5n the stat5c structure of the soft7are s8stem.
!he %onA(unct5ona6 re?u5rements of our project are>
!5me>
!h5s project shou6d be comp6eted 75th5n the st5mu6ated t5me per5od.
Cost>
!he cost 5n9o69ed 5n mar:et5n= the project shou6d be 6ess.
Usab565t8>
!h5s re?u5rement 5s present; as th5s s8stem 7566 5nteract 75th the user.
Re65ab565t8>
!h5s s8stem must be h5=h68 robust.
Performance>
"t shou6d be fast enou=h to produce output.



USE CASE DIAGRAM:
Definition:
& beha95ora6 d5a=ram that sho7s a set of use cases and actors and the5r re6at5onsh5ps 5s ca66ed a use case d5a=ram. "t address
the stat5c use case 95e7 of a s8stem and 5mportant 5n mode65n= the beha95or of a s8stem.
!he major concepts 5n9o69ed 5n use case mode6 are>
A,to- A> an actor represents an8th5n= that 5nteracts 75th the s8stem.
U.e ,/.e A> a use case 5s a se?uence of act5on a s8stem perform that 85e6ds a resu6t to the actor.
Re0/tio1 A> 5t def5nes the re6at5onsh5p bet7een actor and a user.
!he actors 5n9o69ed 5n th5s use case d5a=ram are>
Passen=er
!ra5n deta56s DBHdatabase@
Reser9at5on DB
!he use cases 5n9o69ed are>
-o=5n
Chec: a9a56ab565t8
Date
!ra5n name
Reser9at5on t8pe
(566 and Subm5t form



Ma:e reser9at5on
Ma:e cance66at5on
"ssue t5c:et



ONLINE TIC)ET RESERVATION FOR RAILWA(


Log In
Date & Time
Train No. & Name Train Detail DB

Check Availability
Reservation type
Fill & Sbmit Form
Passenger


!ake Reservation "ay Reservation
Reservation
DB




!ake Cancellation #p$ate Database

Isse Ticket
Use Case Diagram
Problem Statement for Railway Reservation System
&s far as Ra567a8 Reser9at5on s8stem 5s concerned to de9e6op such soft7are 7h5ch 5s prob6em so695n= for a66 the users. !he des5red
s8stem shou6d be d5str5buted 5n ent5re nature. "t shou6d be des5=ned so that 5t pro95des under65ne funct5ona65t8...
USE CASE DIAGRA DESCRIPTION"
Lo2i1"
!h5s funct5on ensures that on68 author5Bed users =a5n access of the reser9at5on. &n author5Bed user 5s one 7ho has account on
the s8stem. Users 5nc6ude passen=ers; ra567a8 off5c5a6s and "RM m5n5str8 off5c5a6s. !he user must =59e the 9a65d user name and
pass7ord.
I13ut." user name and pass7ord 5s an 5nput =59en for the 6o=5n.
Out3ut." the output 5s successfu6 or unsuccessfu6 6o=5n.
P-e,o1ditio1" on68 author5Bed users can =a5n access.
Po.t ,o1ditio1" shou6d not affect the passen=er database.
B/.i, 40o5" chec: the deta56s of tra5n accord5n= to the des5=nat5on.
C6e,7 A8/i0/bi0ity"
!h5s funct5on a66o7s see5n= the tra5ns 5nc6ud5n= the5r source; dest5nat5on; a9a56ab6e seats; arr59a6 and departure t5me; t5c:et
amount.
I13ut.> !ra5n name.
Sou-,e> the 6o=5n funct5on 5s the source use.
Out3ut.> !ra5n schedu6e and a9a56ab565t8 status 5s d5sp6a8ed.
P-e,o1ditio1> !he user shou6d access 7eb
B/.i, 40o5" Reser95n= the re?u5red number of t5c:ets.
/7e Re.e-8/tio1"
!h5s funct5on a66o7s for ma:5n= reser9at5on for a part5cu6ar tra5n on a part5cu6ar date for certa5n number of t5c:ets.



I13ut." Source; dest5nat5on; reser9at5on t8pe; tra5n name; date; t5me and number of seats.
Sou-,e" User 5nputs about source; dest5nat5on and tra5n.
Out3ut." !he output 5s successfu6 or unsuccessfu6 reser9at5on.
P-e+,o1ditio1" #a65d 5nformat5on of tra5n name and other deta56s.
Po.t ,o1ditio1" Successfu6 reser9at5on added to passen=er DB.
B/.i, 40o5" !he user e5ther pa8 amount or cance6 reser9at5on.
P/y Re.e-8/tio1"
!h5s funct5on a66o7s the user pa8 for the5r reser9at5on. !he user must 5nput a 9a65d cred5t card number to pa8.
I13ut." !8pe of cred5t card; card number; card ho6der name and phone number.
Sou-,e" !he user pro95des a66 the necessar8 deta56s.
Out3ut." !he t5c:et 7566 be d5sp6a8ed.
P-e ,o1ditio1" #a65d cred5t card.
Po.t ,o1ditio1" !he Passen=er DB updated and card ba6ance 7566 be updated.
B/.i, 40o5" !he t5c:et 7566 be f5na65Bed.
I..ue Ti,7et"
!h5s funct5on a66o7s 5ssu5n= the conf5rmed t5c:et to the concerned user.
I13ut." %56
Sou-,e" !he 9a65d deta56s entered b8 user and pa8ment pa5d.
Out3ut" !he t5c:et 7566 be d5sp6a8ed 7h5ch can be pr5nted.
P-e+,o1ditio1" (u66 pa8ment shou6d be pa5d.
Po.t+,o1ditio1" !he tra5n deta56s DB and passen=er deta56s DB are updated.
B/.i, 40o5" !he pr5nt out of the t5c:et 5s ta:en and ?u5t.

E+R DIAGRA



CUSTOER
RESERVATION
OFFICER
%&M
AGE
GENDER
AGE

NAE
DEPT.
ENQUIR(
ENQUIR(
OFFICER
AGE
%AE
DEPT.
RESERV
E
P%R %o.
DATA FLOW DIAGRA
9+LEVEL DFD



Pa8ment
Re?uest for (orm
Subm5t (orm
Conf5rmat5on
Reject5on
Chec: for Status
Re?uest for Reser9at5on
Re?uest for en?u5r8
"ssue (orm
&ns7er to en?u5r8
n?u5r8
Pa8ment Rece59ed
&pp65cat5on (orm
Conformat5on
Reject5on
!5c:et Pr5nt5n=
%/U"R,
O(("CR
COUS!MR
RSR#&!"O%
O(("CR
1.
R&"-)&,
RSR#&!"O%
S,S!M
DATA FLOW DIAGRA
!+LEVEL DFD



!ra5n !5m5n= and a9a56ab565t8

Reser9at5on Record
!5c:et to Costumer
Chec: for Status
Reject5on
Conformat5on
Pa8ment Rece59e
"ssue !5c:et
Chec: Status
Update
Record
&ns7er to n?u5r8
Re?uest for en?u5r8
Pa8ment
!.!
%/U"R,
PROCSS
1.$
PR"%!"%G
PROCSS
1.2
P&,M%!
PROCSS
COS!UMR
RSR#&!"O%
O(("CR
%/U"R,
O(("CR
Conf5rm
n?u5r8
!5c:et Rece59ed
1.+
RSR#&!"O%
PROCSS
Subm5t (orm
"ssue (orm
Re?uest for (orm
Conformat5on
Reject5on
&pp65cat5on (orm
Se:ue1,e Di/2-/m



PASSENGER RAILWA(
DATABASE
CLER) TIC)ET
2. D5sp6a8 t5metab6e
1. Re?uest t5metab6e
+. Re?uest to reser9e H@
$. "nput deta56s
*. Ca6cu6ate fare
.. Reser9e t5c:et
1. Pr5nt !5c:et
13. Cance6 !5c:et
0. Re?uest to pr5nt t5c:et
2. Re?uest to cance6 t5c:et

LIITATIONS
Our project meets the fo66o75n= 65m5tat5ons>
1@ !he soft7are 5s not ab6e to reser9e t5c:ets for more than 13 peop6e per tra5n.
2@ !he fare a66otted for e9er8 reser9at5on 5s 5ndependent of J56ometres tra9e66ed 5nstead 5t 5s set for e9er8 mode H&C; %onA&C or
Genera6@ of each tra5n.
+@ !he soft7are 5s made such to carr8 out reser9at5on 5n ma< 1* tra5ns.
$@ !he soft7are does not support mu6t5Ada8 reser9at5on s8stem; 5.e.; the reser9at5ons cannot be done 5n ad9ance rather 5t 5s
carr5ed out for s5n=6e da8.
*@ !he soft7are does not pro95de concess5on 5n fare rates for ch56dren; a=ed peop6e; armament etc. 5.e.; the fare 5dent5ca6 for a66
peop6e.
.@ !he soft7are does not ta:e 5nto cons5derat5on the stat5ons fa665n= 5n bet7een the source and dest5nat5on stat5on.
FUTURE SCOPE
"f an8one 7ants to e<tend th5s project then heGshe can ma:e an add5t5ona6 database of !ra5n (are. &nd database for updated
a9a56ab565t8 of seats 7h5ch 5s a9a56ab6e after the cance66at5on of t5c:et on that spec5f5c tra5n etc. 'eGshe can a6so add some more
command buttons 5n the e<5st5n= soft7are and e<tend 7or:5n= of the e<5st5n= soft7are.
"mp6ementat5ons of th5s project 5dea are 5n 5ndustr5a6 use. 'ence; th5s can be used for su==est5n= 5mpro9ements 5n des5=n;
performance and =reater usab565t8. &part from the 5ndustr5a6 app65cat5ons; 5t 5s a researchAor5ented project as 7e66; the tas: of
performance e9a6uat5on of d5fferent database des5=ns; for eff5c5enc8; 5s 5n th5s sp5r5t.