Sei sulla pagina 1di 31

Online Ticket Reservation System

Reg.No:Y10MTCS902

ONLINE TICKET RESERVATION SYSTEM


AIM:
To develop software for Online Ticket Reservation system with various functional and non functional part of design namely, Problem analysis and requirement analysis Use case documentation UML diagram

PROBLEM DEFINITION:
The Online Ticket Reservation System has an online catalog using which the passenger can login, search for Trains, search for Train tickets, and reserve Train tickets online. Reservation manager is used to update the new Train in the database .The Airline reservation system is a new system that replaces the current manual process for searching the Train details. The reservation manager to manage all the Train details as well as professional details. As a manager, we can manage passenger benefits & passenger personnel information under confidentiality and accessibility.

OBJECTIVE OF THE APPLICATION


The ultimate goal of this project is to develop database software that enables enterprise user to reserve the Train tickets, find and retrieve passenger information.

SIGNIFICANCE OF THE APPLICATION


The significance of the project includes the following key features

The passenger can search all the Train details The passenger can book the Train tickets The manager maintaining all passenger details in the database The manager maintaining all the Train details in the database Add and cancel reservation

Online Ticket Reservation System

Reg.No:Y10MTCS902

FUNCTIONAL REQUIREMENTS
Add reservation The reservation manager adds the details of passenger to be added in the database. The reservation manager searches the passenger to be deleted and removes the information about the book from the database. The user select for the particular reservation to view the list of details. The user selects the particular source and destination to view its details The user selects the Train name to view details The user can view the details based on selection.

Cancel reservation Select reservation select source and destination find Train view information

Online Ticket Reservation System

Reg.No:Y10MTCS902

1.USE CASE DIAGRAM

USE CASE TEMPLATE

Online Ticket Reservation System

Reg.No:Y10MTCS902

Use Case ID: Use Case Name: Created By: Date Created: Actors: Description:

1 Check availability of Trains Sajeetharan S April 24,2012 Passenger The passenger can search for their Train and via online catalog, whether Train is available or not available Customer wants to book the ticket. In this case there is no precondition. The reservation system menu will be displayed. The details about the Trains will be displayed. . Last Updated By: Date Last Updated:

Trigger Preconditions: Post conditions:

Normal Flow


None

The Passenger wants to view menu for Trains The System displays the list of available Trains Then Passenger selects one Train from list

Alternative Flows: Exceptions:

1.0 Invalid search


If the Train name is invalid name, system displays error message. None High Passenger None Passenger shall be able to view the Train details, which he had reserved. None None

Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:

USECASE DIAGRAM

Online Ticket Reservation System

Reg.No:Y10MTCS902

IS S U E T IC K E T VIE W R E S E R VAT IO N S T AT U S < < e xte n d s > > VIE W T R AIN S C H E D U L E S < < e xte n d s > > < < e xte n d s > > VIE W T R AIN F AR E

E N Q U IR Y

R E S E R VAT IO N C LERK

USER

R E S E R VE S E AT

C AN C E L L AT IO N

AU T H E N T IC AT E

U P D AT E D ATAB AS E B AN K AD M IN

T R AN S AC T IO N

Online Ticket Reservation System

Reg.No:Y10MTCS902

2.SEQUENCE DIAGRAM

Online Ticket Reservation System

Reg.No:Y10MTCS902

SEQUENCE DIAGRAM:
A sequence diagram is a graphical view of a scenario that shows object interaction in a time-based sequence-what happens first, what happens next. Sequence diagrams establish the roles of objects and help provide essential information to determine class responsibilities and interfaces. A sequence diagram has two dimensions: the vertical dimension represents time; the horizontal dimension represents different objects. The vertical line is called the objects lifeline. The lifeline represents the objects existence during the interaction. Jacobson popularized this form. An object is shown as a box at the top of a dashed vertical line. A role is a slot for an object within a collaboration that describes the type of object that may play the role and its relationships to other roles. (i).LOGIN:

:PASSENGER 1:enter name and password

:LOGIN

:RESERVATIO N CLERK

2:sending name and pwd

3:verify

4:shows home page

Online Ticket Reservation System

Reg.No:Y10MTCS902

(ii).VIEWING DETAILS:

:passenger 1:enter name and pwd

:login

:reservation clerk

2:sending name & pwd 3:verify

4:show home page

5:ask for reservation status 6:show reservation status

7:ask for train schedule

8:show train schedule

9:process completed

Online Ticket Reservation System

Reg.No:Y10MTCS902

(iii).TICKET RESERVATION:

:passenger :1.enter name and pwd

:login

:reservation clerk

:bank admin

2:sending nmae and pwd

3:verfy

4:shows home page 5:book tickets(reserve)

6:verify for tic...

7:ask for account no. 8:enter acc. no. 9:send acc. no9

10:verify

11.successfully verified 12.successfully reserved

13.issue ticket

Online Ticket Reservation System

Reg.No:Y10MTCS902

(iv).TICKET CANCELLATION:

:passenger 1:enter name & pwd

:login

:reservation clerk

10:verify

2:sending name & pwd

3:verify

4:shows home page

5:cancellation 6:ask for details and acc.no

7:enter details and acc.no

8:verify

9:send acc.no

11.successfully verif...

12.successfully cancelled

Online Ticket Reservation System

Reg.No:Y10MTCS902

3.COLLABORATION DIAGRAMS

Online Ticket Reservation System

Reg.No:Y10MTCS902

COLLABORATION DIAGRAMS:
Collaboration diagrams are also relatively easy to draw. They show the relationship between objects and the order of messages passed between objects. These objects are listed as icons and arrows indicate the messages passed between them. The numbers next to the message are called sequence numbers. There are many acceptable numbers in Uml for simple diagrams 1, 2, 3.. and for complex diagrams 1, 1.1, 1.2, 1.3, schema should be used. Collaboration diagrams show objects, their links and their messages. They can also contain simple class instances and class utility instances. Each collaboration diagram provides a view of interactions or structural relationships that occur of objects and object like entities in the current model.

(i).LOGIN:

1: 1:enter name and password :PASSE NGER :LOGIN

4: 4:shows home page 3: 3:verify 2: 2:sending name and pwd

:RESERVATION CLERK

Online Ticket Reservation System

Reg.No:Y10MTCS902

(ii).TICKET RESERVATION:

1 : :1 . e n te r n a m e a n d p w d :pas s en ger : lo g in

5 : 5 : b o o k t ic k e t s (r e s e r ve ) 8 : 8 :e n te r a c c . n o . 4 : 4 :s h o w s h o m e p a g e 7 : 7 : a s k fo r a c c o u n t n o . 1 2 : 1 2 . s u c c e s s fu ll y r e s e r ve d 1 3 : 1 3 . is s u e t i c k e t 2 : 2 : s e n d in g n m a e a n d p w d 3 : 3 : ve rfy 6 : 6 : ve ri fy fo r t ic k e t 1 0 : 1 0 : ve rify

9 : 9 :s e n d a c c . n o 9 : re s e rva t i o n c le r k 1 1 : 1 1 . s u c c e s s fu lly ve rifie d :ban k a d m in

Online Ticket Reservation System

Reg.No:Y10MTCS902

(iii).TICKETCANCELLATION:

1: 1:enter nam e & pwd :pas s en ger :login

5: 5:c anc ellation 7: 7:enter details and ac c .no 4: 4:s hows hom e page 6: 6:as k for details and ac c .no 12: 12.s uc c es s fully c anc elled 2: 2:s ending nam e & pwd

3: 3:verify 8: 8:verify

10:

9: 9:s end ac c .no :res ervation c lerk 11: 11.s uc c es s fully verified 10:verify

Online Ticket Reservation System

Reg.No:Y10MTCS902

(iv).VIEWING DETAILS

1: 1:enter nam e and pwd :pas s en ger :login

5: 5:as k for res ervation s tatus 7: 7:as k for train s c hedule 4: 4:s how hom e page 3: 3:verify 2: 2:s ending nam e & pwd 6: 6:s how res ervation s tatus 8: 8:s how train s c hedule 9: 9:proces s com pleted :res ervation c lerk

Difference between sequence and collaboration: Sequence diagram show time based object interaction while collaboration diagram shows how objects associate with each other. Sequence diagrams are easier to read. Collaboration diagrams use the layout to indicate how objects are statically connected. The create collaboration diagram command creates a collaboration diagram from information contained in the sequence diagram. The create sequence diagram command creates a sequence diagram from information contained in the interaction collaboration diagram.

Online Ticket Reservation System

Reg.No:Y10MTCS902

4.STATE CHART DIAGRAM

Online Ticket Reservation System

Reg.No:Y10MTCS902

STATE CHART DIAGRAM:


State chart diagrams are used to describe the behavior of the system. These diagrams describe all possible states of an object as event occurs. The basic elements are rounded boxes representing the state of the object and arrows indicate the transition to the next state. A State chart diagram is a directed graph of states connected by transitions. A State diagram describes the life history of objects of a given class. A state diagram shows exactly one start state, one or more states, one or more end states and the state transitions between them. At any given time, an object is in particular state. State diagrams represent these states and their changes during time. Every state diagram starts with symbol that represents start state, and ends with symbol for the end state. For example every person can be a newborn, infant, teenager or adult. The UML symbols in a state diagram. The top area stands for the states name, middle area is for state variables, and the bottom is for activities. Transitions are represented with solid arrowhead lines, and circles are for starting and ending state State chart diagrams model the dynamic behavior of individual classes or any other kind of object. They show the sequences of states that an object goes through, the events that cause a transition from one state to another and the actions that result from a state change. State chart diagrams are closely related to activity diagrams. The main difference between the two diagrams is state chart diagrams are state centric, while activity diagrams are activity centric. A state chart diagram is typically used to model the discrete stages of an objects lifetime, whereas an activity diagram is better suited to model the sequence of activities in a process. The representation of the state diagram as follows:

p e rfo rm a c tio n

Online Ticket Reservation System

Reg.No:Y10MTCS902

DIAGRAM:

Login Enter name and password Select the process

decide the process Ticket Reservation no Not yet confirmed Enter the train Date and train no Enter the data... special offers Enter persons detials for special offers for payment Enter the bank account number if cancel For Reservation Crdit the amount verification Print the xerox of ticket Debit the amount no

Ticket Cancellation

Availability checking

take xerox

Online Ticket Reservation System

Reg.No:Y10MTCS902

5.ACTIVITY DIAGRAMS

Online Ticket Reservation System

Reg.No:Y10MTCS902

ACTIVITY DIAGRAMS:
An activity diagram is a variation or special case of a state machine, in which the states are activities representing the performance of operations and the transitions are triggered by the completion of the operations. Unlike state diagrams that focus on the events occurring to a single object as it responds to messages, an activity diagram can be used to model an entire business process. The purpose of an activity diagram is to provide a view of flows and what is going on inside a use case or among several classes. However, activity diagram can also used to represent a classs method implementation. (i).LOGIN:

Online Ticket Reservation System

Reg.No:Y10MTCS902

(ii).TICKET RESERVATION:

Online Ticket Reservation System

Reg.No:Y10MTCS902

(iii).TICKET CANCELLATION:

Online Ticket Reservation System

Reg.No:Y10MTCS902

6.CLASS DIAGRAM

Online Ticket Reservation System

Reg.No:Y10MTCS902

CLASS DIAGRAM:
The UML class diagram, also refereed to as object modeling, is the main static analysis diagram. These diagrams show the static structure of the model. A class diagram a collection of static modeling elements, such as classes and their relationships, connected as graph to each other and to their contents. Class diagram do not show temporal information, which is required in dynamic modeling. Shows a set of classes, interfaces and collaborations and their relationships. Class diagrams address the static design view of a system. Class diagrams that include active classes address the static process view of a system. Object modeling is the process by which the logical objects in the real world are represented by the actual objects in the program. To effectively develop a model of the real world and to determine the objects required in the system, you first must ask what objects are needed to model the system. Answering the following questions will help you to stay focused on the problem at hand and determine what is inside the problem domain and what is outside it: What are the goals of the system? What must the system accomplish? A class diagram is a picture for describing generic descriptions of possible systems. Class diagrams and collaboration diagrams are alternate representations of object models. Class diagrams contain classes and object diagrams contain objects, but it is possible to mix classes and objects when dealing with various kinds of metadata, so the separation is not rigid. Class diagrams are more prevalent than object diagrams. Normally you will build class diagrams plus occasional object diagrams illustrating complicated data structures or message-passing structures.

Online Ticket Reservation System

Reg.No:Y10MTCS902

;
us er nam e : char us er pa s s w ord : char us e r age : int a ddres s : char check availa bility]() book ticket() ca ncel ticke t() C AN C EL R ESERVATION d elete nam e : char d elete inform ation : char cancel() R ESER VATION CL ER K is s u e ticke t() u pd ate details () valida te() ad d res ervation() cancel res ervation()

AU TH EN TIC ATE n am e : char pas s w ord : char lo gin()

BANK
accou nt no : int balance : in t cus to m er nam e : char verify() update ()

AD D RESER VATION a dd nam e : char record info : char a dd res ervation()

CHECK P A SSW ORD INFO name : c har passenger id : char check pass enger info()

DETAILS
train na m e : ch ar train no : in t s chedu le : num view ()

Online Ticket Reservation System

Reg.No:Y10MTCS902

7.COMPONENT DIAGRAM

Online Ticket Reservation System

Reg.No:Y10MTCS902

COMPONENT DIAGRAM:
A component diagram shows the physical dependency relationships (mapping to a file system) between componentsmain programs, subprograms, packages, and tasksand the arrangement of components into component packages. Component diagrams are contained (owned) either at the top level of the model or by a package. This means the diagram will depict the components and packages in which the diagram is contained.

s e rve r. h

s e rve r. ja va

L o g in .h

L o g in .ja va

s e rve r. e x e

A u t h e n t ic a te . h

Au th e n tic a te .ja va

A d d R e s e rva ti o n .h

C a n c e l R e s e r va tio n .ja va

C a n c e l R e s e r va tio n .h C a n c e l R e s e rva tio n .ja va

Online Ticket Reservation System

Reg.No:Y10MTCS902

8.DEPLOYMENT DIAGRAM

Online Ticket Reservation System

Reg.No:Y10MTCS902

DEPLOYMENT DIAGRAM:
A deployment diagram shows processors, devices, and connections. Each model contains a single deployment diagram that shows the connections between processors and devices, and the allocation of its processes to processors. You can create or display the deployment diagram in one of three ways: _ Click Browse > Deployment Diagram. _ On the toolbar, click the deployment diagram icon. _ In the browser, double-click the deployment diagram icon. A deployment diagram shows processors, devices and connections. Each model contains a single deployment diagram which shows the connection between its processors and devices and its allocation from processor to processor. Processor specifications, device specifications and connection specifications enable you to display and modify the respective properties.

FIGURE:DEPLOYMENT DIAGRAM EXAMPLE

Online Ticket Reservation System

Reg.No:Y10MTCS902

user

printer

railway administrator user user

printer printer

railway database

bank admin server bank database system

Online Ticket Reservation System

Reg.No:Y10MTCS902

Potrebbero piacerti anche