You are on page 1of 13

EX.

NO: 6
DATE: ONLINE RAILWAY RESERVATION SYSTEM

AIM

To develop UML diagrams for an online railways reservation system.

PROBLEM STATEMENT

The existing railway reservation system has many drawbacks associated in it. In order to
overcome these, the proposed e-ticketing system would be a breakthrough.
From the normal procedure of the queue system this will help people to book tickets at anytime
and anywhere when there is an access to the internet. The traveller can book a ticket at a click of
a mouse saving the time and money for the travelling. It has also become a hassle free
transaction for both the railway and the traveller.
The online reservation system involves three main factors the database, online operator ( API-
Application Programming Interface ) and a database scheduler. The database scheduler updates
the database, the online operator accepts and confirms the booking and updates the database.
E-tickets are impossible to lose because they reside in a computer database network . For this
reason, they are hard to steal as only a person with the proper identification can actually use the
e-ticket.
DESCRIPTION:

Initially the customer has to create an ID in the E- ticketing portal, so that the user can
log into the system for reservation. An online manager will maintain a database.
To do login process the customer has to fill a registration form that contains the username,
password, first name , last name, gender, DOB, occupation , e-mail id, contact number,
nationality , address,. After submitting the form to the server the user can access the portal for
booking tickets.
ADMINISTRATOR LOGIN:

The administrator has the authority to modify the database.the administrator has to enter
the user name and password created inorder to access the database.The database has information
about train number,train name,train timing,from and to places,number of compartments,number
of seats available in different coaches.

SOFTWARE REQUIREMENT SPECIFICATION

TABLE OF CONTENTS

1.0 INTRODUCTION
Purpose.
1.1 Scope.
1.2 Overview .
1.3 Reference.

2.0 OVERALL DESCRIPTION


2.1 Product Perspective.
2.2 Product function.
2.3 User Characteristics.
2.4 Constraints.
2.5 Assumptions.
2.6 Dependencies.
3.0 SPECIFIC REQUIREMENT
3.1 Functional requirement.
3.2 Non-Functional Requirement.
3.3 Design Constraints.
3.4 Database requirement .

1.0 INTRODUCTION

1.1 PURPOSE

The purpose of this document describes the software requirements for the Online Reservation
System. This specification is written after the recommendations of the IEEE standard 830-1993
[3] as approved by the IEEE Standards Board on December 2, 1993.

1.2 SCOPE

The system is designed to provide an electronic version of the railway passenger


reservation system which has a user-friendly graphical interface and will be more cost
effective compared to the traditional reservation system.

The objectives for the online reservation system are:


To provide existing clerks with a new environment in which to make reservations for
railroad travel.
To provide an avenue for customers to get their tickets in a more convenient way.
To regain control of the railway ticket sales to avoid scalping and overselling of tickets.
To implement a prototype of a scaled down version of the final system to test the solution
and further develop requirements.
To collect statistics in a more efficient manner for future railroad development and
construction.
To increase efficiency of railroads.

Chapter 2 of the SRS is a brief description of the characteristics of the software to be built,
its functions, its users, its constraints and its dependencies.
Chapter 3 is about specific requirements, such as functional requirements, external
interface requirements, performance requirements, and also design constraints and quality
characteristics.
Finally, chapter 4 includes all the supporting information, such
as the Table of Contents, the Appendices, and the Index.

1.4 REFRENCES

Pressman, Roger (2010). Software Engineering: A Practitioner's Approach.


Boston: McGraw Hill.Karl E Weigers (2009) Software Requirements.
www.irctc.co.in
www.indianrailway.gov.in
www.trainenquiry.com

2.0 OVERALL DISCRIPTION

2.1 PRODUCT PERSPECTIVE


The concept of e-ticketing is rising with the growing technology and fast moving
world.
Majority of the people today prefer e-tickets because it saves time that earlier
people used to waste by standing in long queues and just a print out can be used
as a ticket.
To book an e-ticket, you need to first register yourself for free with the particular
website .
The website is the site for online booking and checking the status of the running
trains as well as availability of the wait listed tickets.
The user selects train that he/she wishes to travel in and check the availability
status of that particular train and makes the reservation.
Not only reservation even cancellation can be made online.
Booking an e-ticket is very simple and the most growing mode of making railway
reservation, which also avoid standing in a Q & time saving.
USE CASE DIAGRAM

DESCRIPTION:

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral
diagram defined by and created from a Use-case .A use case diagram is a representation of a
user's interaction with the system and depicting the specifications of a use case. A use case
diagram can portray the different types of users of a system and the various ways that they
interact with the system. This type of diagram is typically used in conjunction with the textual
use case and will often be accompanied by other types of diagrams as well. a use case diagram is
not a standalone model, but one that can be used in conjunction with other models as well.
PROCEDURE:

The first use case diagram is online registration. The online registration is the entire user
login. The actors in the system are passenger, Railway department, Railway database
.The flow of control is the entire website, username, password and the response will be
the train details.
The second use case diagram is the reservation. Reservation is the user login. The actors
in the diagram are passenger and railway department. The flow of control is the entering
date, time, selection of train and no .of seats and confirmation.

USE CASE DIAGRAM:


ACTIVITY DIAGRAM

DESCRIPTION:

Activity diagrams are graphical representations of workflows of stepwise activities and actions
with support for choice, iteration. In the Unified Modeling Language, activity diagrams can be
used to describe the business and operational step-by-step workflows of components in a system.
An activity diagram shows the overall flow of control. Activity diagrams are constructed from a
limited number of shapes, connected with arrows.

PROCEDURE:

The user enters the website and enter the user name and password.
If it is valid then user checks the availability of train, if available, select the train and
makes the payment.
If the login is belongs to the administrator then it will give a authenticity to edit and
modify the details of the train
Then the user enter the credit card details if valid, payment is done with successful
transaction is made to the railway department
CLASS DIAGRAM

DESCRIPTION:

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 the classes.

PROCEDURE:

The first task to generate the classdiagram is to identify the main classes required for the
domain. After identifying the classes,the attributes and the functions required for each
class is defined.
After all the classes ,their attributes along with their datatype and functions are defined
,they are put in a orded to form a complete class diagram.
In this case ,we have six classes such as Passenger, Ticket, Administrator,
Railway_system , Train , Credit_card.

CLASS DIAGRAM
INTERACTION DIAGRAM

DESCRIPTION:

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.
PROCEDURE:
The main objects for the sequence diagram are defined and each object contains a time
line.
In this case of railway reservation, there are five objects with which the sequence,
Railway database, Bank,

STATE CHART DIAGRAM

DESCRIPTION

State chart diagram is one of the five UML diagrams used to model dynamic
nature of a system. The state of an object depends on its current activity or condition .It shows
the possible states of an object.

PROCEDURE
The initial state in the state chart diagram is a login state where the user used to login
to the page using user name and password .
According to the validation of user name and password the state may vary
If the login is valid it enters the next state else it will be exit..
If the login it belong to administrator it is redirected to next state where the
administrator will update and modify the details of train in the database.
If the user login a valid then they can check for the availability of seats. If the seats
are available then they proceed to next state else they will exit
Once there is a available of seats then the user make the payment for the ticket.
Once the payment is confirmed then the ticked will be reserved in the next state .

STATE CHART DIAGRAM

COLLABRATION DIAGRAM

DESCRIPTION

A Communication diagram models the interactions between objects or parts in terms of


sequenced messages. collaboration diagram focuses on object roles instead of the times that
messages are sent .

PROCEDURE
The collaboration diagram contain the class roles like administration , user, railway
system, railway database ,bank.
The administration roles to railway system role has a function of entering the website
and entering the login.
Then from railway system to railway database , the database validate the login for both
user and the administrator.

COLLABRATION DIAGRAM

COMPONENT AND DEPLOYMENT DIAGRAM

DESCRIPTION
COMPONENT DIAGRAM

Components are wired together by using an assembly connector to connect the


required interface of one component with the provided interface of another component
An assembly connector is a "connector between two components that defines that one
component provides the services that another component requires. An assembly connector is a
connector that is defined from a required interface or port to a provided interface or port.

DEPLOYEMENT DIAGRAM
A deployment diagram in them UML models the physical deployment of
artifacts on nodes. The nodes appear as boxes, and the artifacts allocated to each node appear as
rectangles within the boxes. Nodes may have sub nodes, which appear as nested boxes. A single
node in a deployment diagram may conceptually represent multiple physical nodes, such as a
cluster of database servers

PROCEDURE

COMPONENT DIAGRAM

The diagram contain the system as a user and a component as a railway system and bank
The user interacts with a railway system in bidirectional way .The interaction involves
checking of availability of ticket , reserving ticket and making payment.
The user interacts with the bank system in which the user enters the credit card
details.The banks informs the user on successful transaction.

DEPLOYEMENT DIAGRAM
This diagram contains the interfaces namely user interface , railway system interface and
bank interface.
The user interface is linked with railway system interface to check the train information.
The user interface is linked with bank system interface to make payment.

COMPONENT DIAGRAM
DEPLOYMENT DIAGRAM

CODE GENERATED FOR ADMINSTRATOR CLASS


#ifndef ADMINISTRAOR_H_HEADER_INCLUDED_AE9F83FC
#define ADMINISTRAOR_H_HEADER_INCLUDED_AE9F83FC
//##ModelId=51601BD1016E
class ADMINISTRAOR
{ public: //##ModelId=51601C0700D2
Enter_login();

//##ModelId=51601C17034B
Update_train();
//##ModelId=51601C2000B9
Modify_train();

//##ModelId=51601BEA0029
Integer Login_ID;
private: //##ModelId=51601BFC0209
String Password;
};
#endif /* ADMINISTRAOR_H_HEADER_INCLUDED_AE9F83FC */

RESULT :-Thus the online railway reservation system is developed


using UML diagrams.