V+TEAM

Ex. No.:
E-TICKETING
Date:

AIM:
To create an automated system to perform E-ticketing.

(I)
PROBLEM STATEMENT

Our project is carried out to develop software for online Railway Reservation System.

This system has various options like reservation, cancellation and to view details about

available seats. Our project mainly simulates the role of a Railway ticket booking officer,

in a computerized way.

The reservation option enables a person to reserve for a ticket at their home itself. All he/

she has to do is to just login and enter the required details. After this the reservation
database is updated with the person details, train name and also the source and

destination place.

The cancellation option enables the passenger to cancel the tickets that has been already

booked by him/her.

The availability option prompts the person to enter train number, train name and date of

travel. After this the availability database is accessed and available positions are

produced.

(II) SOFTWARE REQUIREMENT SPECIFICATION

1.0 INTRODUCTION

The manual system of ticket reservation takes more time and the number of

reservations per day is limited. To increase the efficiency of the process, we go for online

ticket reservation system. This system supports online ticket booking.

1.1
PURPOSE

If the entire process of reservation is done in a manual manner then it would takes
several months for reservation to reach the applicant. Considering the fact that the

number of passenger is increasing every year, an Automated System becomes essential to

meet the demand. So this system uses several programming and database techniques to

elucidate the work involved in this process. As this is a matter of National Security, the
system has been carefully verified and validated in order to satisfy it.

V+TEAM

1.2 SCOPE

personal details and submit the necessary documents (may be by scanning).

railway can use this system to reduce

his workload and process the application in a speedy manner.

passenger and the administrator.

Passenger will come to know their status of application and the date in which
they must subject themselves for manual document verification.

1.3
DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

Passenger
The person that who wishes to obtain the railway ticket.
PNR
Passenger Name Records
HTML
- Markup Language used for creating web pages.
J2EE
Java 2 Enterprise Edition is a programming platform java platform for
developing and running distributed java applications.

HTTP
- Hyper Text Transfer Protocol.
TCP/IP
Transmission Control Protocol/Internet Protocol is the communication
protocol used to connect hosts on the Internet.

1.4 REFERENCES
IEEE Software Requirement Specification format.

1.5
TECHNOLOGIES TO BE USED

1.6 TOOLS TO BE USED

oping UML Patterns)

1.7

OVERVIEW
SRS includes two sections overall description and specific requirements

Overall Description
will describe major role of the system components and inter-
connections.

V+TEAM

Specific Requirements
will describe roles & functions of the actors.
2.0 OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE

This system tries to make the interface as simple as possible and at the same time
not risking the security of data stored in. This minimizes the time duration in which the

user receives the t i cket.

2.2
SOFTWARE INTERFACE
Front End Client
- The passenger and System online interface is built using
JSP and HTML. The Administrators's local interface is built using Java.

Web Server
Apache Tomcat Server (Oracle Corporation)

Back End
- Oracle 11g database
2.3

HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems have
access to the database in the server.

2.4
SYSTEM FUNCTIONS
Secure Registration of information by the Passengers .
System can generate reports from the information and is the only authorized
personnel to add the eligible application information to the database.

Display the requested pages to the user.

Update the database after every successful process.

2.5
USER CHARACTERISTICS
Passenger
- They are the people who desire to obtain the ticket and submit the
information to the database.

2.6 CONSTRAINTS
The passengers require a computer to submit their information.

e of
intrusion in the web world which requires constant monitoring.

required.

V+TEAM

2.7

ASSUMPTIONS AND DEPENDENCIES

The Passengers must have basic knowledge of computers and English
Language.

passengers may be required to scan the documents and send.

(III) USE -CASE DIAGRAM

The online ticket reservation system uses the following use cases:

1. Request for seat availability

2. makeReservation

3. Cancellation
 4. Check status

5. Print ticket

ACTORS INVOLVED:
1) System

2) Passenger

USE-CASE NAME: REQUEST FOR SEAT AVAILABILITY

The passenger can view the train available in the database for deciding which

train ticket he wishes to reserve. The passenger can search the train information based on

journey date, train type and reservation type. The passenger can view the details of flights

such as, train number, source station, destination station, arrival time, departure time, fare

and number of seats available.

USE-CASE NAME: MAKERESERVATION

The user is allowed to reserve a ticket on train as he/she requires on the particular

date and time. The user has to provide details such as name, train number, date of travel,

source station, destination station, proof name and money transaction details.

USE-CASE NAME: PRINT TICKET

The user after booking a ticket can print a copy of the ticket reserved. The user
has to provide the details about ticket number for searching in the database and passenger

name for confirming passenger identity.

USE-CASE NAME: CANCEL TICKET

A passenger can decide to cancel a ticket after the ticket is booked. The passenger
has to provide details about ticket for searching and details about him for confirmation of

identity.

V+TEAM

USE-CASE NAME: CHECK STATUS

The passenger can view the status of the reserved tickets. So the passenger can

confirm his/her travel.

Fig.3.1 USE-CASE DIAGRAM FOR AIRLINE RESERVATION

request for seat availability

cancellation
check status
Passenger
System
print report
makeR eservation
<<include>>

V+TEAM

(IV) ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency. 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. An activity is shown as an rounded box containing the name of the operation.

This activity diagram describes the behaviour of the system.

-Ticketing system.

-Ticketing
DataBase.

Check seat availablity based on

date/ train/reservation type
Is it valid
data?
Show the
error page
No
Display the required
train information
Yes

Fig.4.1 ACTIVITY DIAGRAM [Check Availability]

V+TEAM

Fig.4.2 ACTIVITY DIAGRAM [Ticket Reservation]

Login(username
,password)
Check the data
with database
Is it valid user
Display the
cancellation page
Yes
Select the
passenger details
Perform amount
transaction
is it valid

data?
Store & update
the status
Show the
Confirmation
Print the
ticket
Ask to enter
correct data
No
Show error message
to enter correct data
No
want to

proceed
Yes
No
want to

proceed
Yes
No
Yes

V+TEAM

request to check
pnr status
Enter the PNR
number
Display
the status
Is valid PNR

no?
Invalid PNR
number
No
Yes

Fig.4. 3ACTIVITY DIAGRAM [Check Status]

V+TEAM

Fig.4. 4ACTIVITY DIAGRAM [Ticket Cancellation]

Login(username
,password)
Check the data
with database
Is it valid user
Display the
cancellation page
Select the
passenger details
is it valid

data?
Store & update
the status
Show the
Confirmation
Ask to enter
correct data
Show error message
to enter correct data
want to

proceed
want to

proceed
Yes
Yes
No
No
Yes
No
Yes
No

V+TEAM

(V) CLASS DIAGRAM:

The class diagram, also referred to as object modeling is the main static analysis

diagram. The main task of object modeling is to graphically show what each object will

do in the problem domain. The problem domain describes the structure and the

relationships among objects.

.
The online ticket reservation system makes use of the following classes:
1.

ticketReservation
2.

trainInfo
3.

passengerInfo
4.

seatAvailStatus

1.

TICKETRESERVATION

It consists of twelve attributes and two operations. It records the details of every
ticket booked such as ticket number, passenger ID, source and destination station and etc.

2. TRAININFO

It stores the details of all the trains such as train number, train name, speed, source
and destination stations, etc.

3. PASSENGERINFO
It consists of seven attributes and three operations. This class is used to store
passenger details such as, passenger name, age, address and etc.

4. SEATAVAILSTATUS

This class is used to update the number of seats available for a particular train by

using updateStatus() operation.

V+TEAM

Fig.5.1 CLASS DIAGRAM FOR E-TICKETING

V+TEAM

(VI) INTERACTION DIAGRAM:

A sequence diagram represents the sequence and interactions of a given USE-

CASE or scenario. Sequence diagrams can capture most of the information about the

system. Most object to object interactions and operations are considered events and

events include signals, inputs, decisions, interrupts, transitions and actions to or from

users or external devices.

An event also is considered to be any action by an object that sends information.

The event line represent

performs the operation using a method that the class contains.

This sequence diagram describes the sequence of steps to show

password.

filling details.

ook the tickets.

-Ticketing DataBase verify the filling Details.

-Ticketing DataBase displays the ticket information.

V+TEAM

Fig.6.1.

SEQUENCE DIAGRAM

: Passenger
: Passenger
reserveTicket :
ticketReservation
reserveTicket :
ticketReservation
cancelTicket :
ticketReservation
cancelTicket :
ticketReservation
: seatAvailStatus
: seatAvailStatus
System
System
Login(username,password)
Check given data
Registered user
Display the reservation page
Enter the passenger details
Perform money transaction
Verify given details
request to cancel ticket
Display the cancellation page
Select the passenger details
Verify given details
Update status
Store the details
Updated successfully
Confirm & Display the ticket
Print the ticket
Update status
Store the details
Updated successfully
Ticket cancelled

V+TEAM

Fig.6.2

COLLABORATION DIAGRAM

System
: Passenger
reserveTicket :
ticketReservatio n
can celT icket :
ticketReservatio n
: seatAvailStatu s
7: Verify g iven d etails
17: Verify given d etails
1: L ogin(username,password)
5: Enter the passen ger d etails
6: Perfo rm mo ney transaction
13: Print th e ticket
4: Display the reservation page
12: Con firm & Display the ticket
14: request to cancel ticket
16: Select the passen ger d etails
15: Display the cancellation page
22: Ticket cancelled
2: Check given data
3: Registered u ser
8: Update statu s
11:
9: Sto re the details
19: Store the details
10: Upd ated successfully

20: Upd ated successfully

18: Upd ate status
21:

V+TEAM

(VII) DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the physical

components of a system where the software components are deployed.

Fig.7.1.DEPLOYMENT DIAGRAM
(IX) IMPLEMENTATION OF DOMAIN OBJECTS LAYER AND TECHNICAL

SERVICE LAYER

//Source file: E:\\sugan\\passengerInfo.java

public class passengerInfo

{
private integer passId;

private String PassName;

private integer age;

private string sex;

private integer phoneno;

private String emailid;

V+TEAM

/**

@roseuid 5121D2AB01D4

*/

public passengerInfo()

}
 /**

@roseuid 51188FBF0203

*/

public void addPassenger()

/**

@roseuid 51188FD00148

*/

public void updatePassenger()

/**

@roseuid 51188FD900FA

*/

public void delPassenger()

}
/**
void passengerinfo.updatepass(){

void passengerinfo.addpass(){

void passengerinfo.delpass(){

passengerinfo.passengerinfo() */

//Source file: E:\\SUGAN\\setavailStatus.java

public class setavailStatus

{
private integer transacid;

V+TEAM

private date journeydate;

private integer availableseat;

private string resclass;

 /**

@roseuid 51133F790138

*/

public setavailStatus()

/**

@roseuid 51133CE3002E

*/

public void updatestatus()

//Source file: E:\\saras\\reserve.java

public class reserve

{
private int passid;

private int trainid;

private string source;

private string destina;

private string tclass;

 private int proofid;

private string proofname;

private date date;

private int no.ofSeatsReserved;

private double spare;

private int pnr;

private int reserveid;

public seatAvailableStatus theSeatAvailableStatus;

public trainInfor theTrainInfor;

/**

@roseuid 5110DA9C0232

*/

public reserve()

V+TEAM

/**

@roseuid 5110D2CF0203
 */

public void reserveticket()

/**

@roseuid 5110D562007D

*/

public void cancelticket()

//Source file: E:\\sugan\\trainInfo.java

public class trainInfo

{
private integer trainid;

private string trainname;

private string sourcestn;

private string desstn;

private time depatime;

private time arrivaltime;

private stirng traintype;

private integer distance;

private string speed;

private double fare;

private Integer noOfSeats;

public ticketReservation theTicketReservation;

public seatAvailStatus theSeatAvailStatus;

/**

@roseuid 5121D2AB0186

*/

public trainInfo()

/**

@roseuid 511896750186

*/

public void addTrainInfo()

{
V+TEAM

/**

@roseuid 5118967F0000

*/

public void updateTrainInfo()

/**

@roseuid 511896880186

*/

public void deleteTrainInfo()

}
/**

void trainInfo.deltraininfo(){

void trainInfo.updateinfo(){
 }

void trainInfo.addtrans(){

*/

V+TEAM

(X) IMPLEMENTATION OF USER INTERFACE LAYER

RESULT:

Thus the mini project for airline reservation system has been successfully

executed and codes are generated.