Objective:

The purpose of this source is to describe the railway reservation system which provides thetrain timing
details, reservation, billing and cancellation on various types of reservationnamely,

• Confirm Reservation for confirm Seat.

• Reservation against Cancellation.

• Waiting list Reservation.

• Online Reservation.

• Tatkal Reservation.

Scope:

Railways Reservation System” is an attempt to simulate the basic concepts of an online

Reservation system. The system enables to perform the following functions:

SEARCH FOR TRAIN

BOOKING OF A SELECTED FLIGHT

PAYMENTS

CANCELLATION

Freight Revenue enhancement

Passenger Revenue enhancement

Improved & optimized service

Project Functions:

Booking agents with varying levels of familiarity with computers will mostly use this system.With this in
mind, an important feature of this software is that it be relatively simple to use.The scope of this project
encompasses: -¨

Search: This function allows the booking agent to search for train that are available betweenthe two
travel cities, namely the "Departure city" and "Arrival city" as desired by the traveller.The system initially
prompts the agent for the departure and arrival city, the date of departure, preferred time slot and the
number of passengers. It then displays a list of train available withdifferent airlines between the
designated cities on the specified date and time.
Selection: This function allows a particular train to be selected from the displayed list. Allthe details of
the train are shown:-

1. Train Number

2. Date, time and place of departure

3. Date, time and place of arrival

4. TRAIN Duration

5. Fare per head

6. Number of stoppages -0, 1, 2…

¨Review: If the seats are available, then the software prompts for the booking of train. Thetrain
information is shown. The total fare including taxes is shown and flight details arereviewed.¨

Traveller Information: It asks for the details of all the passengers supposed to travelincluding name,
address, telephone number and e-mail id.¨

Payment: It asks the agent to enter the various credit card details of the person making thereservation.

1. Credit card type

2. Credit card number

3. CVC number of the card

4. Expiration date of the card

5. The name on the card¨

Cancellation:The system also allows the passenger to cancel an existing reservation. Thisfunction
registers the information regarding a passenger who has requested for a cancellationof his/her ticket. It
includes entries pertaining to the train No., Confirmation No., Name, Dateof Journey, Fare deducted.

User Characteristics:

EDUCATIONAL LEVEL:-

At least user of the system should be comfortable with Englishlanguage.

TECHNICAL EXPERTISE: -

User should be comfortable using general purposeapplications on the computer system.

Constrains:
Software constraints:

The system will run under windows98 or higher platforms of operating system.

Assumptions and Dependencies:

Booking Agents will be having a valid user name and password to access the software

The software needs booking agent to have complete knowledge of railways reservationsystem.

Software is dependent on access to internet.

Diagram

A use case diagram in the Unified Modelling Language (UML) is a type of behaviouraldiagram defined by
and created from a Use-case analysis. Its purpose is to present a graphicaloverview of the functionality
provided by a system in terms of actors, their goals (representedas use cases), and any dependencies
between those use cases. The main purpose of a use casediagram is to show what system functions are
performed for which actor. Roles of the actorsin the system can be depicted.Interaction among actors is
not shown on the use case diagram. If this interaction is essentialto a coherent description of the
desired behaviour, perhaps the system or use case boundariesshould be re-examined. Alternatively,
interaction among actors can be part of the assumptionsused in the use case.

Use cases: A use case describes a sequence of actions that provide something of measurable value to
anactor and is drawn as a horizontal ellipse.

Actors: An actor is a person, organization, or external system that plays a role in one or
moreinteractions with the system.

System boundary boxes (optional): A rectangle is drawn around the use cases, called the system
boundary box, to indicate itsscope of system. Anything within the box represents functionality that is in
scope andanything outside the box is not.

Use-case Diagram:
State diagram

Data Flow Diagram

A data flow diagram(DFD) is a graphical representation of the "flow" of data through aninformation
system. DFDs can also be used for the visualization of data processing (structureddesign).On a DFD, data
items flow from an external data source or an internal data store to aninternal data store or an external
data sink, via an internal process. A DFD provides noinformation about the timing of processes, or about
whether processes will operate insequence or in parallel. It is therefore quite different from a flowchart,
which shows the flowof control through an algorithm, allowing a reader to determine what operations
will be performed, in what order, and under what circumstances, but not what kinds of data will beinput
to and output from the system, nor where the data will come from and go to, nor wherethe data will be
stored (all of which are shown on a DFD).It is common practice to draw a context-level data flow
diagram first, which shows theinteraction between the system and external agents which act as data
sources and data sinks.On the context diagram (also known as the 'Level 0 DFD') the system's
interactions with theoutside world are modelled purely in terms of data flows across the system
boundary. Thecontext diagram shows the entire system as a single process, and gives no clues as to
itsinternal organization.This context-level DFD is next "exploded", to produce a Level 1 DFD that shows
some of thedetail of the system being modelled. The Level 1 DFD shows how the system is divided
intosub-systems (processes), each of which deals with one or more of the data flows to or from
anexternal agent, and which together provide all of the functionality of the system as a whole. Italso
identifies internal data stores that must be present in order for the system to do its job, andshows the
flow of data between the various parts of the system.

Level 0:

Level 1:
Level 2:

Graphical user interface:

Screen Short
The system shall provide a uniform look and feel between all the web pages.

Home Page: login:

Registration: search train: