 Presented By:

 Divya Ailani
 Anjali Karira
 Renita Vaswani
 This system is basically concerned with the
reservation of railway tickets to the
passengers.
 In this we are discussing that how the
reservation is done.
 What are the rules and regulations and
procedure for reservation?
 In this project we are going to include all the
entities related to reservation.
 User
 Passenger
 Station
 Train
 Train_Status
 All the manual work should be converted into
computerized so that the load of employees
should decrease.
 The database should be stored in computer
rather than in register/manually
 Easy to store information and fast accessing of
information.
 Centralized management reporting & decision
support.
 Accurate and timely control program.
 To make it easy for fast processing and
modification.
 List of accounts of all customers is available.
 Easy retrieval of accounts.
 To make the Railway system is interactive.
 Quick feed back
 Searching of data is easy
 Passengers don’t have to wait for a long time.
 Information is accurate
 It is a fast process
 Data efficiency is more
 Processor : Pentium IV 2GHz and Above
 RAM : 1GB
 Monitor : VGA Color Monitor
 Printer
 Operating System : Windows XP onwards
 Developing Tool : VB (front end)
 Database : MS-ACCESS (back end)
 Data Redundancy
 Difficulty in accessing the Data
 RESERVATION FORM :
This form is used for the reservation of ticket. The
main advantage of the form is that it has the
easiest of the user interface. This makes it user
friendly and easy to use. It has Passenger’s name,
address, contact no, source and destination station
name and codes.
 CANCELLATION FORM :
This form consists of cancelation. the user
interface is again easy. One just needs the PNR
number to cancel a ticket.
 FARE RECORDS :
This form is used for the fare between two station
with a specific class.
 TRAIN ENQUIRY:
Train enquiry is used for knowing available trains
between two stations. We need to provide source and
destination names or codes and then we will be given
the train names between those two stations.
 RESERVATION ENQUIRY:
This form is used to know if there is any seat
available in a train. Here we need to provide date,
train no, source and destination stations.
 SEAT DETAILS:
This form is used to know about the seat later using
our PNR no.
 The data flow diagram is a graphical
representation that depicts information flow
and the transforms that are applied as data
moves from input to output.
1) Context level or 0-level DFD
2) 1-level DFD
3) 2-Level DFD
 An entity relationship diagram (ERD) shows
the relationships of entity sets stored in a
database. An entity in this context is a
component of data. In other words, ER
diagrams illustrate the logical structure of
databases.
 At first glance an entity relationship diagram
looks very much like a flowchart. It is the
specialized symbols, and the meanings of
those symbols, that make it unique.
 a class diagram in the Unified Modeling
Language (UML) is a type of static structure
diagram that describes the structure of a
system by showing the system's classes, their
attributes, operations (or methods), and the
relationships among objects.
 Class diagrams can also be used for data
modeling. The classes in a class diagram
represent both the main elements,
interactions in the application, and the
classes to be programmed.
 In the diagram, classes are represented with
boxes that contain three compartments:
 1)The top compartment contains the name of the
class. It is printed in bold and centered, and the
first letter is capitalized.
 2)The middle compartment contains the
attributes of the class. They are left-aligned and
the first letter is lowercase.
 3)The bottom compartment contains the
operations the class can execute. They are also
left-aligned and the first letter is lowercase.
 Use case diagrams are usually referred to as behavior
diagrams used to describe a set of actions (use cases) that
some system or systems (subject) should or can perform
in collaboration with one or more external users of the
system (actors). Each use case should provide some
observable and valuable result to the actors or other
stakeholders of the system.

Use case diagrams are in fact twofold - they are
both behavior diagrams, because they describe behavior of
the system, and they are also structure diagrams - as a
special case of class diagrams where classifiers are
restricted to be either actors or use cases related to each
other with associations.

 A state diagram, also called a state
machine diagram or statechart diagram, is an
illustration of the states an object can attain
as well as the transitions between those
states in the Unified Modeling Language
(UML)
 In this,a state defines a stage in the evolution
or behavior of an object, which is a specific
entity in a program or the unit of code
representing that entity
 Activity diagrams are graphical representations of workflows of
stepwise activities and actions with support for choice, iteration
and concurrency.
 Activity diagrams are constructed from a limited number of
shapes, connected with arrows.[4] The most important shape
types:
 rounded rectangles represent actions;
 diamonds represent decisions;
 bars represent the start (split) or end (join) of concurrent
activities;
 a black circle represents the start (initial node) of the workflow;
 an encircled black circle represents the end (final node).
 Arrows run from the start towards the end and represent the
order in which activities happen.
 A sequence diagram is an interaction diagram that shows how
objects operate with one another and in what order. It is a
construct of a message sequence chart.
 A sequence diagram shows object interactions arranged in time
sequence. It depicts the objects and classes involved in the
scenario and the sequence of messages exchanged between the
objects needed to carry out the functionality of the scenario.
Sequence diagrams are typically associated with use case
realizations in the Logical View of the system under
development. Sequence diagrams are sometimes called event
diagrams or event scenarios.
 A sequence diagram shows, as parallel vertical lines (lifelines),
different processes or objects that live simultaneously, and, as
horizontal arrows, the messages exchanged between them, in
the order in which they occur. This allows the specification of
simple runtime scenarios in a graphical manner.
 A collaboration diagram resembles
a flowchartthat portrays the roles, functionality
and behavior of individual objects as well as the
overall operation of the system in real time.
Objects are shown as rectangles with naming
labels inside. These labels are preceded by
colons and may be underlined. The relationships
between the objects are shown as lines
connecting the rectangles. The messages
between objects are shown as arrows connecting
the relevant rectangles along with labels that
define the message sequencing.
 Component diagram is a special kind of diagram in UML.
The purpose is also different from all other diagrams
discussed so far. It does not describe the functionality of
the system but it describes the components used to make
those functionalities.
 Thus from that point of view, component diagrams are
used to visualize the physical components in a system.
These components are libraries, packages, files, etc.
 Component diagrams can also be described as a static
implementation view of a system. Static implementation
represents the organization of the components at a
particular moment.
 A single component diagram cannot represent the entire
system but a collection of diagrams is used to represent
the whole.
 Deployment diagram is a structure diagram which
shows architecture of the system as deployment
(distribution) of software artifacts to deployment
targets.
 Artifacts represent concrete elements in the physical
world that are the result of a development process.
Examples of artifacts are executable files, libraries,
archives, database schemas, configuration files, etc.
 Deployment target is usually represented by
a node which is either hardware device or some
software execution environment. Nodes could be
connected through communication paths to create
networked systems of arbitrary complexity.
 WEBSITES:
 www.google.com
 www.wikipedia.org
 www.indianrail.gov.in