ONLINE TICKET BOOKING SYSTEM

SOFTWARE DESIGN DESCRIPTION

SUBMITTED BY, AMMU.C (09BCE333) SHRUTHI.R (09BCE444)

TABLE OF CONTENTS
1.
Introduction 1.1. Purpose 1.2. Scope 1.3. Glossary 1.4. Overview of document Architecture design 2.1.client server model 2.2.manager model 2.3.class diagram

2.

3. Data structure design

3.1. Data field types and sizes.

4. Use case diagram 5. Use case realizations

5.1 Use Case:Login Use Case:New account Use Case:Change password Use Case:Ticket cancellation Use Case:Add bus/train/flight Use Case:Booking ticket 5.2 Collaboration:Add new b/t/f details Collaboration:Ticket cancellation Collaboration:Booking ticket 6. Activity diagram

7.

Interface design 7.1 login page 7.2 registration page 7.3 select comfortable journey 7.4 search bus 7.5 book ticket 7.6 search flight 7.7 admin page 7.8 add bus

TABLE OF FIGURES
Figure 1: Figure 2: Figure 3. Figure 4: Figure 5: Figure 6: Figure 7: Figure 8: Figure 9: Figure 10: Figure 11: Figure 12: Figure 13: Figure 14 : Figure 15: Figure 16: Figure 17: Figure 18: Figure 19: Figure 20: Figure 21: Figure 22: Client Server Model Manager Model Class Diagram Use Case Diagram Sequence Diagram:login Sequence Diagram:new account Sequence Diagram:change password Sequence Diagram:ticket cancellation Sequence Diagram:add bs/train/flight Sequence Diagram:booking ticket Collaboration Diagram: Add new b/t/f details Collaboration Diagram: ticket booking Collaboration Diagram: ticket cancellation Activity Diagram Login Page Registration Page Select Comfortable Journey Search Bus page Book Ticket page Search Flight page Admin Page Add Bus page

Section 1 1. Introduction
The purpose of this document is to analyze the design details, architectures and other various relationships involved in developing the online ticket booking system(OTBS).

1.1 Purpose
The purpose of Software Design Document (SDD) is to describe the design details, architectures and entity-relationships involved in the development of the online ticket booking system. Design Specification includes activity diagrams, to describe activities and flow of data or decisions between activities; sequence diagrams, to model object interactions arranged in time sequence and to distribute use case behavior to classes;state chart diagrams, to describe the dynamic behavior of a system in response to external stimuli; and class diagrams, to depict classes and their interrelationships, to describe structure and behavior in the use cases, to provide a conceptual model of the system in terms of entities and their relationships, and for requirement capture and end-user interaction.

1.2 Scope
This document contains a complete description of the design of Toll Gate System. The basic architecture is a web server from a client server paradigm.The designated administrator in charge of the Online Ticket Booking System will have full access to make changes, as he/she deems necessary. The changes could include, but not limited to,updating system details,sending email if necessary and report generation.

1.3 Glossary

Term Administrator

Definition The person who manages and administrates the toll database and can make required changes. Online Ticket Booking System Collection of all information.

OTBS Database

Member SDD

Users who check or book tickets. Software Design Document

1.4 Overview
The remaining chapters and their contents are listed below Section 2 is the Architectural Design that specifies the design entities that collaborate to perform all the functions included in the system. Each of these entities has an Abstract description concerning the services that it provides to the rest of the system. In turn, each design entity is expanded into a set of lower-level design operations that collaborate to perform its services. Section 3 concerns the Data Structure Design. Section 4 concerns with use case diagram. Section 5 contains the Use Case Realizations. Each Use Case stated in the SRS Section 6 contains activity diagrams. Section 7 discusses the User Interface Design.

Section 2 2. Architectural Design

Client Server Model
CLIENT1 CLIENT2 CLIENT3 CLIENT4

NETWORK INTERFACE

login database

Search available List of b/t/f

registration Became member

Book tickets Available seats

Add new b/t/f database

profile database

2.Manager Model

OTBS INTERFACE

database

Login interface

Registration interface

database

logout
Error message

User login interface

Admin login interface

Que ry to get reg for m

Registration subsystem

Ret urn for m

Error message

profile

profile

Que R et Quer Ret ry to Que ur y to cha ry to n view urn nge vie de repo rep pass ort w ta rt wor ils d

Pas Ret swo Que Rec Quer urn rd ry to eive y to deta cha boo tick add ils et detai nge k
ls

Query to view detail s

Ret urn det ails

Qu ery to mai l

Se nd ma il

Que ry to cha nge pass wor d

Pas swo rd cha nge

Qu ery to ge ner ate rep ort

Ret ur n rep ort

User account details subsyste m

Report subsyste m

Change passwor d

Booking Details subsyste m

Add new b/t/f info system

View reservati on details

email subsyste m

Change passwor d

Report generate

2.1 class diagram

user login -uid : String -password : String +view() +update() customer +name : String -id : Integer +age : Integer +gender : String +email : String +book_ticket() +cancel_ticket() +view_report() Message1 +check_avail() admin -name : String -id : String +update() +view_reserved() +generate_report() +send_email()

add 1..*

book 1..*
tickets +tname : String -tno : Integer -b/t/f no : Integer +pname : String +seat no : Integer +source : String +dest : String +date : Date +time : Date +view_ticket() +mail_ticket()

update 1..*
B/T/F details

have 1..*

+name : String -no : Integer +source : String +dest : String +seat_no : Integer +date : Date +time : Date +get_updates()

Section 3 3.Data structure design

The data is stored in a relational database using Wampserver(MySql). The relations are described by the database administrator . The fields for transmitting to and from the database are given in the following table.

3.1Data field types and sizes ATTRIBUTE NAME Customer_id password Admin_id Password Customer_name Age Gender Email Source Destination B_no/F_no/t_no Ticket_no Ticket_name Date Time Seat_no Bus/train/flight name Passenger_name Passenger_Age ATTRIBUTE TYPE varchar varchar varchar varchar varchar integer char varchar string string varchar integer varchar date date integer Varchar varchar integer SIZE 20 10 20 10 20 2 1 30 20 20 10 5 20 2 20 20 3

Section 4 4. Use Case Diagram

Section 5 5. Use Case Realizations

1.Login

USER enter id,password

OTBS

OTBS DB

verify information

verification success password wrong display

2.New account

user enter the details

OTBS

OTBS DB

store details

return confirmatioan display name

3.Change password

USER

OTBS

OTBS DB

enter username,current/new password verify old/new password

password changed notification notification sent to user

4.Ticket cancellation

CUSTOMER ENTER PNR NO.TNO

OTBS

OTBS D

VALIDATE INFO

validation successful cancel confirmation

5. Add new bus/train/flight

admin

OTBS

OTBS DB

Add new b/t/f/details store the info confirmation success display

6.Ticket booking

customer

OTBS

OTBS DB

SELECT THE TRANSFORMATION SEARCH AVAILABLITY AVAILABLE DISPLAY THE DETAILS BOOK THE TICKET GET PASSENGER INFO,PAYMENT SAVE THE INFO

SEND THE TICKET DISPLAY TICKET

COLLABORATION DIAGRAM
1.Add new b/t/f details

3.confirmation success
OTBS DB OTBS

2.store the info 4.display 1.Add new b/t/f/details

admin

2. booking tickets
3.available 8.send the ticket
OTBS DB OTBS

2.search avilability 7.save the info

6.Get passenger info,payment

4.display the details 9.display ticket

1.select the transformation 5.book ticket

CUSTOMER

3. ticket cancellation

3.Validation successful
OTBS DB OTBS

2.Validate info 4.Confirm cancellation

1.Enter pnr no,tno

CUSTOMER

Section 6 6. Activity Diagram

validate

enter id,password

admin customer
enter id,password

view reserved tickets

update

validate

send mail

add new b/t/f book tickets cancel tickets

select comfertable journey

enter pnr no,tno

view details

validate

invalid

Not avail

check avail

valid avail
enter passenger iinfo cancel confirmation

payment

view booked ticket

Section 7 7. Interface Design

Login Page

New Account

Select Comfortable Journey

Search Bus

Book Ticket

Search Flight

Admin Page

Add Bus