railway reservation software document a ion

8/2/2019 Railway Reservation Software Document a Ion

1/22
http://images.search.yahoo.com/search/images/view?back=http%3A%2F%2Fimages.search.yahoo.com%2Fsearch%2Fimages%3Fp%3DANIMATED%2BTRAIN%2BPICTURE%26fr%3Dyfp-t-331%26toggle%3D1%26cop%3Dmss%26ei%3DUTF-8%26fp_ip%3DIN%26vc%3D&w=277&h=250&imgurl=www.plymouthlights.com%2Fimages%2F2003%2FOther%2Ftrain_small.jpg&rurl=http%3A%2F%2Fwww.plymouthlights.com%2F2003.htm&size=16.2kB&name=train_small.jpg&p=ANIMATED+TRAIN+PICTURE&type=jpeg&no=9&tt=920&oid=d5cb772dd01e61a0&ei=UTF-8


2/22

Software Requirements Specification

For

Automated Railway Reservation System

PREPARED FOR

PROF. H A RSH A LA

PREPARED BY BE G JOV E RIA M IRZ A [11]

ARA TH Y N A IR [47]

(SYBSC.I.T. A )


3/22

- o wareRequirement

SpecificationsThe initial specification of user requirements may be based on interviews with

the database users and on the designers own analysis of the enterprise.

The basic issues that the SRS writer(s) shall address are the following:

a) Functionality. What is the software supposed to do?

b) External interfaces. How does the software interact with people, thesystems hardware, other hardware, and other software?

c) Performance. What is the speed, availability, response time, recovery time of

various software functions, etc.?

d) Attributes. What are the portability, correctness, maintainability, security,etc. considerations?


4/22

A n SR S should be

a) C orrect

b) U nam biguousc) C om plete

d) C onsistent

e) R anked for im portance and/or stability

f) Verifiable

g) M odifiable

h) Traceable

e) Design constraints imposed on an implementation. Are there any requiredstandards in effect, implementation language, policies for database integrity,

resource limits, operating environment(s) etc.?


5/22

ER -D iagram :

An entity-relationship (ER) diagram is a specialized graphic

that illustrates the interrelationships between entities in a database.

Structure chart:

The entry for every type of categorization under considerationisgiven in a structure chart.


6/22

ER -D IA G R A M :

Name

BOOKING

IdCUSTOMER DETAILS

Name Address

PERSONAL

Age

Gender

Tel.no

OFFICIAL

Designation

Office.add Tel.no

PIDO.id

C.id

Asks

for

Has

aHas

a

Has

a


7/22

TRAINS

Train noTrain name

SEAT

AVAILABILITY

Tno

Src.Stn

Dest.Stn

Class

Quota

User

asks

for

Date

FARE

DistanceClass

Trnno.

CANCELLATION

CPNR

No. of seats

Date

Class

User asks for

User books


8/22

TICKETSPNR

No. of

seats

Board

Trn.no

Destination

Quota

Class

Fare

Distance

CLASS

AC

General

No of

seats

PNRno

Sleeper

TRno

Has

a

Seats vacant

Trno Date

Source

Destination

No. of seats

Is a

date


9/22

BOOKING/

STATIONS

CUSTOMER DETAILSTRAINS

CANCELLATION SEAT

AVILABILITY

TICKETS FARE SCHEDULE

CLASS DISCOUNTS

Level 1

Level 22

Level3

Level4

STRU CTURED CH AR T


10/22

D FD Principles :

The general principle in Data Flow Diagramming is that a system can be

decomposed into subsystems, and subsystems can be decomposed into

lower level subsystems, and so on.

Each subsystem represents a process or activity in which data is

processed. At the lowest level, processes can no longer be decomposed.

Each 'process' in a DFD has the characteristics of a system.

Just as a system must have input and output (if it is not dead), so aprocess must have input and output.

Data enters the system from the environment; data flows between

processes within the system; and data is produced as output from the

system


11/22

DATA FLOW

D IA G RA M

CONTEXT LEVELDFD


12/22

BOOKING

CENTREPASSENGER

Terms and conditions/

Procedure

Passenger Details (sign up)

ONLINE

RAILWAY

RESERVATIO

N

SCHEDULE FARES

Ticket Details

Ticket Confirmation

Cancellation/Change

Cancel/Change Confirmation

passenger/seat details

Birth/Ticket Info.

Ticket confirmation

Schedule/Discounts Info.

Booking Information

passenger personal Info.

Schedule/Train Info .

Seats available

Class/Birth Schedule

Passengers/Ticket InfoFare/Discounts Details

Ticket Details

Amount

Book Ticket

Paid Details


13/22


14/22

Account

Profile

1.0

Find Train

Registration

MenuSIGN UP IndividualRegistration

SIGN IN

Validates

Passenger Account

Database

1.1

Make Reservation

3.0

Cancellation

2.0

Booked History

Update ProfileChange

Password

Make Reservation

Database

Cancellation Database

4.0

Cancelled Ticket

History

Passenger


15/22


16/22

1.0

Find Train

Details Required:

1) To

2) From

3) Date

4) Quota5) Class

6) Tatkal(YES/NO)

Check Date Should be after three days

Check Quota General

Ladies

heck Tatkal

Only valid for some trains

Passenger

Discounts

Class

Have to select one

Find Trains

Valid DestinationValid source

P O i


17/22

Lists of Trains

1.3Show Availability

1.2

Get Fare

1.4

Show Route

1.1

Book TicketSelect Train

Passenger Account

Database

Tatkal

Status ReportQuota

Senior Citizen

Class

Distance

Route Distance

Display

Birth preference

Age

Payment Options

ReservationDatabase


18/22


19/22

2.0

Booked History

Password

Cancellation

Database

Displays details

PNR number

Valid

YES

NO Displays Error

Passenger


20/22

3.0

Cancellation

Password

Passenger

Cancellation

Database

Booked

History

Displays

Error

Processed

Valid

Invalid


21/22

4.0

Cancelled

Ticket

History

Password

Reservation

Database

Displays details

PNR number

Valid

YES

NO Displays Error

Passenger


22/22

THANKING-YOU

railway reservation software document a ion

Documents