Railway-reservation cb.pdf

8/13/2019 Railway-reservation cb.pdf

1/32

Software Engineering Project

On

RAILWAY RESERVATION

MAHARAJA A RASEN INST! O" TE#HNOLO Y

$e%e&o'e( )*

Na+e , a-ra% a-r .ranc/ , #!S!E Ero&& no, 0101234505


2/32

#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+


3/32

PRO.LEM STATEMENT "OR RAILWAYRESERVATION SYSTEM

Software has to be developed for automating the manualreservation system of railway. The system should be standalone in nature.It should be designed to provide functionalities like bookingof tickets in which a user should be able to applied for ticketsof any train and of any class.A limitation is imposed when the number of tickets for whichuser apply is greater then available seats or no seats areavailable. If seats are not available then put user transactionin the waiting queue.If the tickets are available then it isissued to the user and it must be updated in the databaseconcurrently. The system generates the receipt for thesame.

The software takes the current system date and time as thedate of issue and calculates the amount to be paid by theuser.It also provide the functionality of cancellation of tickets .Ifthe user wants to cancel the tickets, he/she must enter thedetails. The system check the records from the database if it

is matched with the user entered details, then it cancels thetickets. The system also calculates the amount to be return to theuser after deductions. The system must update the databasefor the same.After that system must check for waiting passenger for thattrain, if any then these tickets are issued to waitingpassenger and update the database.

The system displays the details of train of which user enterthe name.

The information is saved and the corresponding updatingtake place in the database.In the enquiry, the system should be able to provideinformation like the availability of tickets of particular train,train schedule.

The system should be able to reserve a ticket for a particularuser if the tickets are not currently available.

The corresponding print outs for each entry issue/cancel! inthe system should be generated.


4/32

There should be proper information if the waiting list ticket isconfirmed, through mail or via sms.It should tell us as to which all stations it haults and currentstatus of the train should be informed.

Security provisions like the login authenticity should beprovided. "ach user should have a user id and a password.#ecord of the users of the system should be kept in the logfile. $rovision should be made for full backup of the system.


5/32

SO"TWARE RE:7IREMENT SPE#I"I#ATION

1! INTRODUCTION

The document aims at defining the overall software requirements forRAILWAYRESERVATI ! 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& additionalfunctionalit&(feature should not ma)e $& an& of the 'arties involved indevelo'ing(testing(im'lementing the 'roducts# In case it is required to have someadditional 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 $& thesoftware a''lication +RAILWAY RESERVATI ! SYSTE"# It also states thevarious required constraints $& which the s&stem will a$ide# The intended audiencefor 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 willmanage the information

a$out 'assengers details regarding the reservation of seat in different class fordifferent 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,IEEEstandard 3456,3775#

1!= OVERVIEW


6/32

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

2. OVERALL DESCRIPTION

4!1 PRO$7#T PERSPE#TIVE

The a''lication will $e a window $ased* self,contained and inde'endent software 'roduct#

4!1!1 SYSTEM INTER"A#ES

!one

4!1!4 7SER 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 theo'erator will $e 'rovided# Access to different screens will $e $ased u'on therole 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 seatis 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 areavaila$le of the different classes of each train#

4!1!; HAR$WARE INTER"A#ES

>a? Screen resolution of at least 466 ; )? 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''licationof an& of them#

SO"TWARE INTER"A#ES

1i2 An& windows $ased o'erating s&stem#


7/32

1ii2 "S E;>ESS ?666 as the ./"S for data$ase future release of thea''lication will aim at u'grading to RA>LE,4i to ./"S#L

1iii2 >r&stal re'orts,4 for generating and viewing re'orts#1iv2 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 #OMM7NI#ATION INTER"A#ES

!one

4!1!= MEMORY #ONSTRAINTS

At least i? A login facilit& for ena$ling onl& authori9ed 'erson to the s&stem#>ii? ser 1with role of ./A2 will $e a$le to add(modif&(delete information

a$out different 'assengers that can have name in reservation list* waitinglist * train schedule#

>iii? ser 1with role of a o'erator2 will $e a$le to access 'assengers details* finedetails and view monthl& re'orts#

4!; 7SER #HARA#TERISTI#S

>i? Educational Level- At least graduate should $e comforta$le with EnglishLanguage#

>ii? Technical E%'ertise- Should $e comforta$le using general 'ur'osea''lications on a com'uter#


8/32

4!2 #ONSTRAINTS

>i? 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 ofrecords#

>ii? .ue to limited features of ./"S $eing used* 'erformance tuning featureswill not $e a''lied to the queries and thus the s&stem will $ecome slowwith the increase in num$er of records $eing used#

>iii? .ue to limited features of ./"S $eing used* data$ase auditing will not $e 'rovided#

4!= APPORTIONIN O" RE:7IREMENTS

!one

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 E TERNAL INTER"A#ES

;!1!1 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 accessdifferent screen $ased u'on the userCs role# Various fields availa$le on thisscreen will $e -

1a2 ser I. - Al'hanumeric u'to 36 characters1$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 theuser with the second role to add(modif&(delete(records of 'assengers*train# The o'erator can access and modif& these details# The screen willdis'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 toadd(modif&(delete train details# This screen will dis'la& train no#* seat no#*num$er of seats in the train#


9/32


10/32

If an& of the a$ove validations(sequencing flow does not hold true* a''ro'riateerror messages will $e 'rom'ted to the user for doing the needful#

VALI$ITY #HE#BS

>i? nl& user with controller or data entr& o'erator will $e authori9ed toaccess the 'assengers information management module#>ii? Ever& 'assenger will have allotted a unique tic)et num$er* seat num$er#>iii? Seat num$er and 'assenger name can not $e $lan)#

5#?#? TRAINS IN"ORMATION MANA EMENT

$ES#RIPTION

The s&stem will maintain information a$out the train name* train num$er# !um$erof 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? nl& user with role of controller or data entr& o'erator can access thismodule#

>ii? Ever& seat has a unique num$er#>iii? 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


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? nl& user will role of controller or data entr& o'erator can access issued $oo)Cs information#

>ii? .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 $eallotted # The issue details must $e 'resent $efore the seat is cancelled#


11/32

ERROR HAN$LIN CRESPONSE TO A.NORMAL SIT7ATIONS


5#?#@ #AN#EL TI#BET IN"ORMATION MANA EMT

$ES#RIPTION

The s&stem will calculate refunda$le amount to 'assenger after suita$ledeductions* $ased on the time with res'ect to validation of tic)et : date of return#

VALI$ITY #HE#BS

>i? .ate of return should $e a valid si% digit num$er#>ii? It cannot $e $lan)

>iii? nl& controller : data entr& o'erator can access this module

;!; OTHER RE:7IREMENTS

;!;!1 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# sers will have to enter correctusername* '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 incor'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#


12/32

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

;!5 Ot/er Re6-ire+ent8

!one


13/32

SE >ASE .IA RA"

Operator

Login

Booking

Enquiry

Cancellation

User


14/32

7SE #ASE $ES#RIPTION

1! LOGIN

1!1 INTRO$7#TION

This use case documents the 'rocedure for logging into the Railwa& ReservationS&stem $ased on user 'rivileges#

'erator 1Login* Enquir&* /oo)ing* >ancellation2#

ser 1Login* Enquir&* /oo)ing* >ancellation2#

1!4 A#TORS

'erator* ser

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 stateis unchanged#

3#G "LOW O" EVENTS

1!=!1 .ASI# "LOW

This use case starts when actor wishes to log into the Railwa& ReservationS&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 + ser* he(she will $e logged into the s&stem and

'resented with userCs menu#


15/32

1!=!4 ALTERNATE "LOW

1!=!4!1 INVALI$ NAMECPASSWOR$

If the s&stem receives an invalid userHid or 'assword* an error message isdis'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! IRY for following accounts -

3# Enquir& regarding trains?# Enquir& for reservation status#

4!4 A#TORS

'erator* ser#

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#


16/32

4!=!4 ALTERNATE "LOWS

4!=!4!1 INVALI$ EN:7IRY

If the user enter the wrong details *then the s&stem shows message according tothe quer& and the use case ends#

4!@ SPE#IAL RE:7IREMENT

!one


!one#

;! BOOKING

;!1 INTRO$7#TION

This use case documents the 'rocedure of $oo)ing of tic)ets and u'date the data$aseafter each transaction #

;!4 A#TOR

'erator* ser

;!; PRE9#ON$ITION

'erator( ser 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 thes&stem state is unchanged#

;!= "LOW O" EVENTS

;!=!1 .ASI# "LOW


17/32

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#


18/32

G# The use case ends#

2!@ SPE#IAL RE:7IRMENTS

!one


!one


19/32

A#TIVITY $IA RAM O" LO IN

Enter User Name &Password

Validation

Enter yourcorrect Password

I wrong

!ccess User !ccount

I correct Password


20/32

A#TIVITY $IA RAM O" .OOBIN

add t"e name inwaiting list

request or a#ooking

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

reser$e t"eseat

con irmreser$ation

%es

No


21/32

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

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

get t"e details orcancellation

update trainreser$ation status


22/32

SE E!>E .IA RA" - / JI!

Operator User Booking 'orm Controller (rain)detail *orry message#o+

Passengerdetail

Passen(rain ,e

-.Enter (rain

name /.*u#mit name0.1et (rain ,eta il

2.C"eck a$aila#il3

ity o seats4.*eat not a$aila#le

5. !dd 6ecord

7.

Update ,etails

8.Booking

*uccess ully

9.

Update ,etails


23/32

SE E!>E .IA RA" - >A!>ELLATI !

Operator & User Cancellation'orm

Controller (rain (a#le Passenger (rain,etail (a#le

-.Enter (rain

,etails /.*u#mit ,etails0.

C"eck ,etails

2.Cancel seat

Update ta#le

5.Cancellation

success ul

4.Update ta#le


24/32


25/32

SE E!>E .IA RA" - L I!

Operator & User Login 'orm Controller Login),etail

id:password

1et Login

details

C"eck LoginError or

*uccess

-.

/.

0.

2.

4.

su#mit details


26/32

>LASS .IA RA" - L >AL VIEW

Login),etailUsernamePassword

!dd;ASE VIEW ( L I! .ETAIL

Login),etail=

(rain)=aster

=

Passenger)(rain),et>>>

=

Passenger),etails=

=

=

(rain),etails

=

=

=


28/32

> LLA/ RATI ! .IA RA" - L I!

Operator &User

Login'orm

Controller Login),etail

2.

-.

/.

4.

0.

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

Operator &user

Enquiryorm

Controlle3r

(rain=aster

-.

/.

0.

2.


29/32

#OLLA.ORATION $IA RAM, .OOBIN

Operator &User

Bookingorm

Controll33er

(rain,etail

*orry =essage#o+ Passenger

,etailPassenger(rain ,etail

-. /. 0.

2.

4. 5.

9.

7

7. 9

98.


30/32

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

#oundaries entities

Control

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

#oundaries entities

Control


31/32

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

(rain) master

(rain) ,etails

Passenger),etails

Passenger)(

rain),etails

> "F !E!T .IA RA" - E!TITIES ( "AI!

Login)details


32/32

E DR $IA RAM

Documents

Railway-reservation cb.pdf