8/2/2019 Design Phase 1

1/16

Railway Reservation & Information System

Design Document 1

Version 1.2

Group Id:

Supervisor Name:

8/2/2019 Design Phase 1

2/16

Revision HistoryDate (dd/mm/yyyy) Version Description Author

21/01/2010 1.0 Design Document-I25 /01 /2010 1.1 Design Document-I27 /01 /2010 1.2 Design Document-I

Table of Contents

8/2/2019 Design Phase 1

3/16

1. Introduction (of analysis and design phase)

2. Overview (of proposed system)

3. Data Flow Diagram s (DFD)

(To be developed using Microsoft Visio)

4. Entity Relationship Diagram (ERD)

(To be developed using Microsoft Visio or ERWIN)

5. Activity Diagram

6. Sequence Diagrams

(To be developed using Rational Rose)

7. Architecture Design Diagram

1. Introduction (of analysis and design phase)

The analysis phase defines the requirements of the system, independent of how

these requirements will be accomplished and implemented. This phase defines the

problem that the customer is trying to solve. The deliverable result at the end of this

8/2/2019 Design Phase 1

4/16

phase is a requirement document. Ideally, this document states in a clear and

precise fashion what is to be built. This analysis represents the ``what'' phase. The

requirement document tries to capture the requirements from the customer's

perspective by defining goals and interactions at a level removed from the

implementation details.

In the design phase the architecture is established. This phase starts with the

requirement document delivered by the requirement phase and maps the

requirements into architecture. The architecture defines the components, thei

interfaces and behaviors. The deliverable design document is the architecture. The

design document describes a plan to implement the requirements. This phase

represents the ``how'' phase. Details on computer programming languages and

environments, machines, packages, application architecture, distributed architecture

layering, memory size, platform, algorithms, data structures, global type definitions

interfaces, and many other engineering details are established.

2. Overview (of proposed system)

This system will be designed to provide the online railway reservation system for the

users. The interface of this system will be user friendly and graphical. This electronic

railway reservation system will be cheaper than the non electronic reservation

system.

3. Data Flow Diagrams (DFD) (To be developed using Microsoft Visio)

Context Diagram:

8/2/2019 Design Phase 1

5/16

Rai lwa y R eservat ion&In format i on Sys tem

Visi tor

A dm in

Passenger

U p da t e T r a i n R ou t e

U p da t e F a ir

U p da t e F A Q

Rep ly Quer i es

C on f i r m U p da t e s

Re ce ive Quer i es& issues

R e s p ondQ u e r y

V ie w F A Q

P u t Q u e r y

V ie w F A QR e qu e s t

S ign U pR e qu e s t

S how

Regi s teredS ta tus

V ie w F a r e

Re ques t Seat Reservat ion

Reques t Concess ionReservat i on

Reques t Spec ia l&

Tou r i st R eservat ion

V iew Re servat ion S ta tus

R e qu e s t C a r goReservat i on

R e qu e s t Lu ggageBook ing

V ie w C a r go&Lu ggage S t a tu s

V ie w R e p o r t s

V ie w T r a i n R ou t e

Contex t D iagram(D F D)

Level-1 Data Flow Diagram:

8/2/2019 Design Phase 1

6/16

ReservationDatabase

PassengerDatabase

Train InfoDatabase

F AQ& QueryDatabase

Ad m in ist ra to r

P1Update FAQ

Visitor

Update FAQ

Update FAQ info

P2View FAQ

Get FAQdata

View FAQ

View F AQRequest

P3

Reply Quer ies

Reply Queries

Update Queries Info

P4Put Queries

Get QueryResponse

View QueryReply

P5Update Fare

Update Fare

Update Fa re info

P6

View Fare

Get Faredata

View Fa re

Put Query

P7Update Train

Route

Update TrainRoute

Update Train info

Sign UpRequest

P9Sing Up

ViewRegistered

Status

Passenger

P8Show Train

Info

Get Traininfo

View TrainRoute

P11

Make SeatReservation

P12

Check SeatAv aila bi lity

RequestSeat Reservation

Check Seat

Status

Get Seat Status

Reserve

SeatUpdate PassengerDatabase

CheckSeat availability

ShowReservation

Status

CheckRules

Feedback

P10Log In

Open accountSession

ProvideSessionToken

VerifyInfo

Provide

Login info

Level-1 Data Flow D iagram

4. Entity Relationship Diagram (ERD) (To be developed using Microsoft Visio or

any other UML tool)

8/2/2019 Design Phase 1

7/16

8/2/2019 Design Phase 1

8/16

5. Activity Diagram

Sign Up Activity Diagram:

Fill theformat SignupPage

ValidateLoginInfofromDatabase

CreateAccount intheDatabase

Correct Info

IncorrectInfo

Log In Activity Diagram:

8/2/2019 Design Phase 1

9/16

Fill Log In Formand Send

Verify login info . Fromdatabase

Open the account

Login Formfields validation at Client Side

Correct info

WrongInfo

Correct info

WrongInfo

Seat Reservation Activity Diagram:

8/2/2019 Design Phase 1

10/16

Select a Route

ConfirmReservation

Selects a Train

True Info

Display Available Seats

Select a Seat and Press Reserve

Payment

Made

NotMade

False Info

Log In

Cancel Reservation Activity Diagram:

8/2/2019 Design Phase 1

11/16

User Login

Open Cancel Reservation Page

Check Cancel ReservationDue Date

Valid

Cancel Reservation

True

Expire

6. Sequence Diagrams (To be developed using Rational Rose)

Sign-up:

8/2/2019 Design Phase 1

12/16

: Visitor

: signup

UserInfo(param)

storeUserInfo(param)

Process()

Return registered staus

Show Status

: database

Login:

: Passenger

: login

requestLogIn()

verifyLoginInfo()

Process()

send resultOpen Account Session

: database

View Fare:

8/2/2019 Design Phase 1

13/16

: Visitor

: fare

getFare()

retriveFare()

Process()

send result

View Fare

: database

View FAQs:

: Visitor

: faq

getFAQ()

retriveFAQ()

Process()

send result

View FAQ

: database

Seat Reservation Status:

8/2/2019 Design Phase 1

14/16

: Passenger

: seatstatus

getSeatStatus()

checkSeatAvailibility()

Process()

send result

Display Seat Status

: database

Update Fare:

: Admin

: updatefare

updateFare()

storeFare()

Process()

send notification

Confirm update

: database

Make Seat Reservation:

8/2/2019 Design Phase 1

15/16

: Passenger

: seatreservation

reqSeatReservation()

reserveSeat()

Process()

send result

Show Seat Reservation Status

: database

Cancel Booking:

: Cargo Officer

: cancelbooking

reqCancelBooking()

deleteBooking()

Process()

delete notification

Confirm Booking Cancellation

: database

7. Architecture Design Diagram

8/2/2019 Design Phase 1

16/16