Software Engineering Project On

RAILWAY RESERVATION

MAHARAJA A RASEN INST! O" TE#HNOLO Y

$e%e&o'e( )* Na+e , .ranc/ , Ero&& no, a-ra% a-r #!S!E 0101234505

#ONTENTS,
Pro)&e+ State+ent Software Re6-ire+ent S'ecification 78e ca8e (iagra+ 78e ca8e (e8cri'tion Acti%it* $iagra+8 Se6-ence $iagra+8 #&a88 $iagra+ #o&&a)oration $iagra+ E9R $iagra+

PRO.LEM STATEMENT "OR RAILWAY RESERVATION SYSTEM

Software has to be developed for automating the manual reservation system of railway. The system should be standalone in nature. It should be designed to provide functionalities like booking of tickets in which a user should be able to applied for tickets of any train and of any class. A limitation is imposed when the number of tickets for which user apply is greater then available seats or no seats are available. If seats are not available then put user transaction in the waiting queue.If the tickets are available then it is issued to the user and it must be updated in the database concurrently. The system generates the receipt for the same. The software takes the current system date and time as the date of issue and calculates the amount to be paid by the user. It also provide the functionality of cancellation of tickets .If the user wants to cancel the tickets, he/she must enter the details. The system check the records from the database if it is matched with the user entered details, then it cancels the tickets. The system also calculates the amount to be return to the user after deductions. The system must update the database for the same. After that system must check for waiting passenger for that train, if any then these tickets are issued to waiting passenger and update the database. The system displays the details of train of which user enter the name. The information is saved and the corresponding updating take place in the database. In the enquiry, the system should be able to provide information like the availability of tickets of particular train, train schedule. The system should be able to reserve a ticket for a particular user if the tickets are not currently available. The corresponding print outs for each entry issue/cancel! in the system should be generated.

There should be proper information if the waiting list ticket is confirmed, through mail or via sms. It should tell us as to which all stations it haults and current status of the train should be informed. Security provisions like the login authenticity should be provided. "ach user should have a user id and a password. #ecord of the users of the system should be kept in the log file. $rovision should be made for full backup of the system.

SO"TWARE RE:7IREMENT SPE#I"I#ATION 1! INTRODUCTION

The document aims at defining the overall software requirements forRAILWAY RESERVATI ! SYSTE"# Efforts are $een made to define the requirement e%haustivel& and accuratel&# The final 'roduct will $e having onl& features(functionalities mentioned in this document and assum'tion for an& additional functionalit&(feature should not ma)e $& an& of the 'arties involved in develo'ing(testing(im'lementing the 'roducts# In case it is required to have some additional features* a formal change request will need to $e raised and su$sequentl& a new release of this document and(or 'roduct will $e 'roduced# 1!1 P7RPOSE

This s'ecification document descri$es the ca'a$ilities that will $e 'rovided $& the software a''lication +RAILWAY RESERVATI ! SYSTE"# It also states the various required constraints $& which the s&stem will a$ide# The intended audience for this document is the develo'ment team* testing team and the users of the 'roduced# 1!4 S#OPE

The software +RAILWAY RESERVATI ! SYSTE" will $e an a''lication that will $e used for automating the railwa& reservation data$ase# The a''lication will manage the information a$out 'assengers details regarding the reservation of seat in different class for different trains* cancellation of seats* waiting lists of 'assengers* train schedule# The s&stem also 'rovides the facilit& to the 'assenger to chec) the time,ta$le of train* reservation level of the seat* waiting seat level# 1!; $E"INITIONS< A#RONYMS AN$ A..REVATIONS

The following a$$reviations have $een used throughout./A 0 .ata$ase Administrator 1!2 RE"EREN#ES 1a2 IEEE recommended 'ractice for software requirements s'ecifications,IEEE standard 3456,3775#

1!= OVERVIEW

The rest of this SRS document descri$es the various s&stem requirements* interfaces and functionalities in details#

2.
4!1

OVERALL DESCRIPTION
PRO$7#T PERSPE#TIVE

The a''lication will $e a window $ased* self,contained and inde'endent software 'roduct# 4!1!1 !one 4!1!4 7SER INTER"A#ES SYSTEM INTER"A#ES

The a''lication will have a user friendl& and menu $ased interface# 8ollowing screens can $e found>a? A login screen for entering the user name* I. num$er and 'assword for the o'erator will $e 'rovided# Access to different screens will $e $ased u'on the role of the user# >)? There will $e a screen for ca'turing and dis'la&ing 'assenger details vi9# name* age* se%* address# >c? There will $e a screen for ca'turing and dis'la&ing info* regarding which seat is alotted to which 'assenger* date : time of issue and the automaticall& calculated fare of the tic)ets according to different class of tic)et is issued# >(? There will $e a screen for ca'turing and dis'la&ing details of all the tic)ets are availa$le of the different classes of each train# 4!1!; HAR$WARE INTER"A#ES

>a? Screen resolution of at least 466 ; <66 is required for com'lete and 'ro'er viewing of screens# =igher resolution will not $e an& 'ro$lem# >)? Su''ort for 'rinter- 'ro'er drivers must $e installed and 'rinter connected will $e requested for 'rinting of monthl& re'orts# >c? Standalone or networ) $ased not a concern as it will $e 'ossi$le to run the a''lication of an& of them#

SO"TWARE INTER"A#ES 1i2 An& windows $ased o'erating s&stem#

1ii2 1iii2 1iv2

"S E;>ESS ?666 as the ./"S for data$ase future release of the a''lication will aim at u'grading to RA>LE,4i to ./"S#L >r&stal re'orts,4 for generating and viewing re'orts# Visual $asic for coding develo'ing the software# The final a''lication 'ac)ages as an inde'endent setu' 'rogram that will $e delivered to the client#

4!1!2 !one 4!1!=

#OMM7NI#ATION INTER"A#ES

MEMORY #ONSTRAINTS

At least <@ "/ of RA" and ? A/ on hard dis) will $e required for running the a''lication# 4!1!@ OPERATIONS

This 'roduct release will not cover an& automated house)ee'ing as'ects of the data $ase# The ./A at the client site will $e res'onsi$le for manuall& deleting old or non, required data# .ata $ase $ac)u' and recover& will also $e handled $& the ./A# 4!1!5 SITE A$APTATION RE:7IREMENTS

The terminals at client site will have to su''ort the hardware and software interfaces s'ecified B in the a$ove section# 4!4 PRO$7#T PERSPE#TIVE

The s&stem will allow access to onl& authori9ed 'ersonnel# .e'ending on userCs role* he(she will $e a$le to e%cess onl& s'ecific modules of the s&stem# A summar& of the maDor functions hat the software will 'erform are>i? >ii? >iii? A login facilit& for ena$ling onl& authori9ed 'erson to the s&stem# Eser 1with role of ./A2 will $e a$le to add(modif&(delete information a$out different 'assengers that can have name in reservation list* waiting list * train schedule# Eser 1with role of a o'erator2 will $e a$le to access 'assengers details* fine details and view monthl& re'orts#

4!;

7SER #HARA#TERISTI#S >i? >ii? Educational Level- At least graduate should $e comforta$le with English Language# Technical E%'ertise- Should $e comforta$le using general 'ur'ose a''lications on a com'uter#

4!2

#ONSTRAINTS >i? >ii? >iii? Since the ./"S $eing used is "S E;>ESS ?666* which is not a ver& 'owerful ./"S* it will not $e a$le to store a ver& large num$er of records# .ue to limited features of ./"S $eing used* 'erformance tuning features will not $e a''lied to the queries and thus the s&stem will $ecome slow with the increase in num$er of records $eing used# .ue to limited features of ./"S $eing used* data$ase auditing will not $e 'rovided# O" RE:7IREMENTS

4!= !one

APPORTIONIN

3.

SPECIFIC REQUIREMENTS

This section contains the software requirement to a level of detail sufficient to ena$le designers to design the s&stem and testers to test the s&stem# ;!1 ;!1!1 EATERNAL INTER"A#ES 7SER INTER"A#ES The following screens will $e 'rovided>i? LO IN S#REEN This will $e the first screen to $e dis'la&ed# It will allow user to access different screen $ased u'on the userCs role# Various fields availa$le on this screen will $e 1a2 Eser I. - Al'hanumeric u'to 36 characters 1$2 Fassword - Al'hanumeric of length u'to 36 characters# 1c2 Role - will have the following values 1data entr& o'erator2# >ii? PASSEN ERS IN"ORMATION S#REEN This screen is accessi$le to the data entr& o'erator* controller# It allows the user with the second role to add(modif&(delete(records of 'assengers* train# The o'erator can access and modif& these details# The screen will dis'la& the list of 'assengers* their allotted seat no#* train no#* and address# >iii? TRAINS IN"ORMATION S#REEN This screen is accessi$le to the data entr& o'erator which allows to add(modif&(delete train details# This screen will dis'la& train no#* seat no#* num$er of seats in the train#

>i%?

ISS7E$ TI#BET S#REEN This screen is accessi$le to the data entr& o'erator# The user can addC(modif& information# Screen dis'la&s train name* train num$er* seat no#* 'assengers name and other details li)e issue date* time* num$er of seats of different class of different trains are availa$le#

;!1!4

HAR$WARE INTER"A#ES >i? >ii? >iii? Seen resolution of at least 466;<66 is required for com'lete and 'ro'er viewing of screens# =igher resolution will not $e an& 'ro$lem# Su''ort for 'rinter- Fro'er drivers must $e installed and 'rinter connected# Frinter will $e requested for 'rinting of monthl& re'orts# Standalone or networ),$ased,not a concern as it will $e 'ossi$le to run the a''lication of an& of them#

;!1!;

SO"TWARE INTER"A#ES 1i2 1ii2 1iii2 1iv2 An& windows $ased o'erating s&stem "S E;>ESS,?666 as the ./"S for data$ase future release of the a''lication will aim at u'grading to RA>LE,4i to ./"S# >r&stal re'orts,4 for generating and viewing re'orts# Visual $asic for coding develo'ing the software# The final a''lication 'ac)ages as an inde'endent setu' 'rogram that will $e delivered to the client#

;!1!2

#OMM7NI#ATION INTER#A#ES !one

;!4 5#?#3

SYSTEM "EAT7RES PASSEN ERS IN"ORMATION MANA EMENT $ES#RIPTION The s&stem will maintain record of 'assengers name* age* address* allotted seat no#* 'assenger status either in reservation list or in waiting list# The s&stem will allow creation(modification(deletion of new or e%isting 'assengers # SE:7EN#IN IN"ORMATION

Fassenger information for a 'articular 'assenger will have to $e entered $efore an& enquir& details* cancellation details can $e entered for the student# ERROR HAN$LIN CRESPONSE TO A.NORMAL SIT7ATIONS

If an& of the a$ove validations(sequencing flow does not hold true* a''ro'riate error messages will $e 'rom'ted to the user for doing the needful# VALI$ITY #HE#BS >i? >ii? >iii? 5#?#? nl& user with controller or data entr& o'erator will $e authori9ed to access the 'assengers information management module# Ever& 'assenger will have allotted a unique tic)et num$er* seat num$er# Seat num$er and 'assenger name can not $e $lan)#

TRAINS IN"ORMATION MANA EMENT $ES#RIPTION The s&stem will maintain information a$out the train name* train num$er# !um$er of seats in a* $* and general class categor&# The s&stem will allow creation(modification(deletion of new or e%isting seats# VALI$ITY #HE#BS >i? >ii? >iii? nl& user with role of controller or data entr& o'erator can access this module# Ever& seat has a unique num$er# Seat num$er* class and train name can not $e $lan)#

SE:7EN#E IN"ORMATION Tic)et information will $e 'resent in the s&stem $efore it can $e issued# ERROR HAN$LIN CRESPNOSE TO A.NORMAL SIT7ATIONS If an& of the a$ove validations(sequencing flow does not hold true* a''ro'riate error messages will $e 'rom'ted to the user for doing the needful# 5#?#5 ISS7E$ TI#BETS MANA EMENT The s&stem will maintain information a$out seats that are issued# >orres'onding 'assenger details and date of issue# VALI$ITY #HE#BS >i? >ii? nl& user will role of controller or data entr& o'erator can access issued $oo)Cs information# .ate of issue must $e entered as a si% digit num$er#

SE:7EN#E IN"ORMATION Fassenger information and seat information must $e entered $efore a seat can $e allotted # The issue details must $e 'resent $efore the seat is cancelled#

ERROR HAN$LIN CRESPONSE TO A.NORMAL SIT7ATIONS If an& of the a$ove validations(sequencing flow does not hold true* a''ro'riate error messages will $e 'rom'ted to the user for doing the needful# 5#?#@ #AN#EL TI#BET IN"ORMATION MANA EMT $ES#RIPTION The s&stem will calculate refunda$le amount to 'assenger after suita$le deductions* $ased on the time with res'ect to validation of tic)et : date of return# VALI$ITY #HE#BS >i? >ii? >iii? ;!; ;!;!1 .ate of return should $e a valid si% digit num$er# It cannot $e $lan) nl& controller : data entr& o'erator can access this module

OTHER RE:7IREMENTS PER"ORMAN#E RE:7IREMENTS !one

;!2

$ESI N #ONSTRAINTS !one

SO"TWARE SYSTEM ATTRI.7TES ;!2!1 SE#7RITY The a''lication will $e 'assword 'rotected# Esers will have to enter correct username* 'assword and role to access the a''lication# ;!2!4 MAINTAINA.ILITY The a''lication will $e designed in a maintaina$le manner# It will $e eas& to in cor'orate new requirements in the individual modules # ;!2!; PORTA.ILITY The a''lication will $e easil& 'orta$le on an& WI!. W $ased s&stem that has "S,A>>ESS ?666 installed# ;!= LO I#AL $ATA.ASE RE:7IREMENTS The following information will $e 'laced in a data$ase#

>i? >ii?

Fassenger information - name* age* se%* address# Seat information - train num$er* seat num$er* num$er of seats in train#

;!5
!one

Ot/er Re6-ire+ent8

ESE >ASE .IAARA"

Login

Enquiry Operator User

Booking

Cancellation

7SE #ASE $ES#RIPTION

1!

LOGIN

1!1 INTRO$7#TION This use case documents the 'rocedure for logging into the Railwa& Reservation S&stem $ased on user 'rivileges# 'erator 1Login* Enquir&* /oo)ing* >ancellation2#

Eser 1Login* Enquir&* /oo)ing* >ancellation2# 1!4 A#TORS 'erator* Eser 3#5 PRE9#ON$ITIONA !one 3#@ POST9#ON$ITION If use case is successful* the user is logged into the s&stem* otherwise the s&stem state is unchanged# 3#G "LOW O" EVENTS 1!=!1 .ASI# "LOW This use case starts when actor wishes to log into the Railwa& Reservation S&stem# 3# The s&stem requests that the actor enters his(her userHid and 'assword# ?# The actor enters userHid and 'assword# 5# The s&stem validates the userHid and 'assword and chec)s for his(her 'rivileges# @# If the actor is +o'erator* he(she will $e logged into the s&stem and 'resented with o'eratorCs menu# G# therwise* if the actor is +Eser* he(she will $e logged into the s&stem and 'resented with userCs menu# <# The use case ends#

1!=!4

ALTERNATE "LOW

1!=!4!1 INVALI$ NAMECPASSWOR$ If the s&stem receives an invalid userHid or 'assword* an error message is dis'la&ed and the use case ends# 1!@ SPE#IAL RE:7IREMENTS !one 1!5 RELATE$ 7SE #ASES !one

?#

ENQUIRY

4!1 INTRO$7#TION This use case documents the 'rocedure of E!IEIRY for following accounts 3# Enquir& regarding trains ?# Enquir& for reservation status# 4!4 A#TORS 'erator* Eser# 4!; PRE9#ON$ITION 'erator must $e logged in to the s&stem 4!2 POST9#ON$ITION If use case is successful* the user can get information regarding trains*reservation therwise* the s&stem state is unchanged# ?#G "LOW O" EVENTS 4!=!1 .ASI# "LOW The use case starts when a s&stem can get the enquir& from the user# 3# The s&stem chec)s the t&'e of enquir& ?# The s&stem su$mits the user quer& to controller of the s&stem # 5# The controller search the information from the data$ase# @# The resultant information is 'resented infront of the user# G# The use case ends#

4!=!4

ALTERNATE "LOWS

4!=!4!1 INVALI$ EN:7IRY If the user enter the wrong details *then the s&stem shows message according to the quer& and the use case ends# 4!@ SPE#IAL RE:7IREMENT !one 4!5 RELATE$ 7SE #ASES !one#

;!

BOOKING

;!1 INTRO$7#TION This use case documents the 'rocedure of $oo)ing of tic)ets and u'date the data$ase after each transaction # ;!4 A#TOR 'erator* Eser ;!; PRE9#ON$ITION 'erator(Eser must $e logged into the s&stem

;!2 POST9#ON$ITION If the use case is successful* the tic)et is issued to the 'assenger * otherwise the s&stem state is unchanged# ;!= "LOW O" EVENTS ;!=!1 .ASI# "LOW

3#This use case starts when a user enter train name# ?#The s&stem read the information and chec) the availa$ilit& of the seats# 5#If the seats are availa$le *the s&stem e%ecute the transaction # @#The resultant information is u'dated in the data $ase# G# The issue details are sent to the 'rinter to generate the tic)ets# <# The use case ends# ;!=!4 ALTERNATE "LOW

;!=!4!1 NON 9AVAILA.ILTY If the seats are not availa$le the s&stem sends the message accordingl& *and 'uts the user transaction in waiting state *and according to the 'riorit& the seats are allotted to the users # The use case end here# 2! CANCELLATION 2!1 INTRO$7#TION This use case documents the 'rocedure for canceling of issued tic)ets according to the customer transaction# 2!4 A#TORS 'erator* Eser# 2!; PRE9#ON$ITION 'erator( user must $e logged into the s&stem# 2!2 POST9#ON$ITION If the use case is successful * the request or recommendation are fulfilled and data$ase is u'dated accordingl&# 2!= "LOW O" EVENTS 2!=!1 .ASI# "LOW This use case starts when a enters the details regarding canceling of tic)ets# 3# ?# 5# @# The s&stem chec) the details regarding the quer& of the customer# The s&stem u'dates the train reservation status# The s&stem refunds the amount to the user after suita$le deductions# The s&stem chec)s list of waiting 'assengers and allot the vacant seats#

G# The use case ends#

2!@ SPE#IAL RE:7IRMENTS !one 2!5 RELATE$ 7SE #ASES !one

A#TIVITY $IA RAM O" LO

IN

Enter User Name & Password

Validation I wrong Enter your correct Password

I correct Password !ccess User !ccount

A#TIVITY $IA RAM O" .OOBIN

request or a #ooking

c"eck w"et"er a seat is a$aila#le

No

%es add t"e name in waiting list

reser$e t"e seat

con irm reser$ation

A#TIVITY $IA RAM O" #AN#ELLATION

get t"e details or cancellation

update train reser$ation status

re und t"e amount to t"e passenger a ter suita#le deductions

SEIEE!>E .IAARA" - /

JI!A

Operator & User

Booking 'orm

Controller

(rain)detail

*orry message #o+

Passenger detail

Passenger (rain ,etail

Enter-. (rain name /. name *u#mit 0. 1et (rain ,etail

2. C"eck a$aila#il3 ity o seats 4. *eat not a$aila#le 5. !dd 6ecord 9. Update ,etails Update ,etails 7. 8. Booking *uccess ully

SEIEE!>E .IAARA" - >A!>ELLATI !

Operator & User

Cancellation 'orm

Controller

(rain (a#le

Passenger (rain ,etail (a#le

-. Enter (rain ,etails

/. *u#mit ,etails

0. C"eck ,etails Cancel2. seat Update ta#le 4.ta#le Update

5. Cancellation success ul

SEIEE!>E .IAARA" - E!IEIRY

User & Operator

Enquiry 'orm

Controller

(rain)master

-. Enter ,etails /.,etails *u#mit *earc" 0.

2.(rain *"ow In ormation

SEIEE!>E .IAARA" - L AI!

Operator & User

Login 'orm

Controller

Login),etail

-. id:password /. details su#mit

0. 1et Login details

2. 4. Error or *uccess C"eck Login

>LASS .IAARA" - L A >AL VIEW

Login),etail Username Password !dd;< ,elete;< Update;< (rain),etails ,ate (ime (rain Name !$aila#le seats;I&II< !dd;< ,elete;< Update;< 1et,etails;<

(rain)=aster (rain id (rain Name Capacity;I&II< *ource ,estination (ime ,ays !dd;< ,elete;< Update;< 1et,etails;< Passenger)(rain),etail (rain Name *eat no> Class;I&II< date (ime !dd;< ,elete;< Update;< 1et,etails;<

Passenger),etails Passenger Name !ddress !ge P"one no> (rain Name

>LASS .IAARA" - ESE >ASE VIEW ( L AI! .ETAIL

Login),etail
=

(rain)=aster
=

(rain),etails
=

Passenger)(rain),et>>>
= =

Passenger),etails
= =

> LLA/ RATI ! .IAARA" - L AI!

-. Operator & User Login 'orm

4. 2. /. 0. Controller Login),et ail

#OLLA.ORATION $IA RAM , EN:7IRY

-. Operator &user Enquiry orm

/.

2. 0.

Controlle 3r

(rain =aster

#OLLA.ORATION $IA RAM, .OOBIN

2.

-. Operator &User Booking orm

/. Controll33 er 8. 9

0. (rain ,etail

7 4. 5.

*orry =essage #o+

Passenger ,etail

Passenger (rain ,etail

9. 7. 9

> "F !E!T VIEW - "AI!

#oundaries

entities

Control

> "F !E!T VIEW - "AI!

#oundaries

entities

Control

> "F !E!T .IAARA" - > !TR L("AI!

(rain) master (rain) ,etails

Passenge r),etails

Passenger)( rain),etails

> "F !E!T .IAARA" - E!TITIES ( "AI!

Login)details

E DR $IA RAM