173501-Rabia Muneer-Online Reservation System - PIA

SEPTEMBER 22, 2019
Online Airline Reservation

System (PIA)
SOFTWARE DESIGN DESCRIPTION DOCUMENT
VERSION: 1.0
RABIA MUNEER 173501

SESSION: 2017-2019
Khawaja Fareed post Graduate College, Rahim Yar Khan
i
Revision History
Date Description Author Comments
9/22/2019 Version 1.0 Rabia Muneer
Document Approval
The following Software Requirements Specification has been accepted and approved by the
following:
Signature Printed Name Title Date
Sir Usman Ghani Supervisor, CSIT 21306 9/22/2019
ii
Table of Contents
1. INTRODUCTION .............................................................................................................................. 1
1.1 Purpose...................................................................................................................................... 1
1.2 Scope ......................................................................................................................................... 1
1.3 Overview ................................................................................................................................... 1
1.4 Reference Material .................................................................................................................... 1
1.5 Definitions and Acronyms ........................................................................................................ 2
2. SYSTEM OVERVIEW...................................................................................................................... 2
2.1 Assumption ............................................................................................................................... 2
2.2 Technology to be used .............................................................................................................. 2
2.3 Design language ........................................................................................................................ 3
2.4 Application overview ................................................................................................................ 3
2.5 General constraints.................................................................................................................... 3
2.6 System Environment ................................................................................................................. 3
3. SYSTEM ARCHITECTURE............................................................................................................ 4
3.1 Web Architecture ....................................................................................................................... 4
3.2.1 Architectural Design .............................................................................................................. 4
3.1.1.2 Block Diagram ..................................................................................................................... 5
3.2 Decomposition Description ...................................................................................................... 5
3.2.1 Use Cases ............................................................................................................................... 6
3.2.1.1 Registration .................................................................................................................................................... 6
3.2.1.2 Login .................................................................................................................................... 7
iii
3.2.1.3 Search Flight ........................................................................................................................ 8
3.2.1.4 Make Reservation ................................................................................................................ 9
3.2.1.5Modify Reservation ............................................................................................................ 10
3.2.1.6 Cancel Reservation ............................................................................................................ 11
3.2.1.7 Payment ............................................................................................................................. 12
3.2.1.8 Add Flight Information ...................................................................................................... 13
3.2.1.9 Modify Flight Information ................................................................................................. 14
3.2.1.10Delete Flight Information ................................................................................................. 15
3.2.1.11 Add Customer Information .............................................................................................. 16
3.2.1.12Update Customer Information .......................................................................................... 17
3.2.1.13Delete Customer Information ........................................................................................... 18
3.2.1.14 Contact Us........................................................................................................................ 19
3.2.1.15Feedback ........................................................................................................................... 20
3.2.1.16 view Schedule .................................................................................................................. 21
3.2.1.17Logout ............................................................................................................................... 22
3.2.2 Sequence Diagrams.............................................................................................................. 23
3.2.2.1Login ................................................................................................................................... 23
3.2.2.2 Make Reservation .............................................................................................................. 24
3.2.2.3 Modify Reservation ........................................................................................................... 25
3.2.2.4 Cancel Reservation ............................................................................................................ 26
3.2.2.5 Add Custromer Information ............................................................................................... 27
3.2.2.6 Modify Custromer Information.......................................................................................... 28
3.2.2.7 Delete Custromer Information ........................................................................................... 29
iv
3.2.3 State-Transition Diagrams (STD) ........................................................................................ 30
3.2.3.1 Login .................................................................................................................................. 30
3.2.3.3 Update Reservation ............................................................................................................ 31
3.2.3.4Cancel Reseevation ............................................................................................................. 32
3.2.4 Activity Diagram ................................................................................................................. 33
3.2.4.1 Login .................................................................................................................................. 33
3.2.4.3Cancel Reseevation ............................................................................................................. 35
3.2.4.3 Modify Reservation ........................................................................................................... 36
3.2.4.3 Flight .................................................................................................................................. 37
3.2.4.4 Payment ............................................................................................................................. 38
3.2.5 Class Diagram ....................................................................................................................... 39
3.2.5.1Login ................................................................................................................................... 39
3.2.5.2Booking ............................................................................................................................... 40
3.2.5.3Airline ................................................................................................................................. 41
3.2.5.4Flight ................................................................................................................................... 42
3.2.5.5Ticket Management ............................................................................................................ 43
3.2.5.6Reservation ......................................................................................................................... 44
3.2.5.7Payment .............................................................................................................................. 45
3.2.5.8Entire System ...................................................................................................................... 46
3.3 Design Rationale ..................................................................................................................... 47
4. DATA DESIGN ......................................................................................................................... 47
v
4.1 Data Description ..................................................................................................................... 47
4.1.1 Data Object .......................................................................................................................... 47
4.1.1. Administrator ....................................................................................................................... 47
4.1.2. Login .................................................................................................................................... 48
4.1.3. Customer .............................................................................................................................. 48
4.1.4. Payment ............................................................................................................................... 48
4.1.5. Ticket ................................................................................................................................... 48
4.1.6. Booking ................................................................................................................................ 49
4.1.7. Flight .................................................................................................................................... 49
4.1.8. Airline .................................................................................................................................. 49
4.1.9. Schedule ............................................................................................................................... 49
4.1.10. Passenger ........................................................................................................................... 50
4.1.11 Seat...................................................................................................................................... 50
4.1.12 Reservation ......................................................................................................................... 50
4.1.2 ER Diagram .......................................................................................................................... 51
4.2 Data Dictionary ....................................................................................................................... 52
4.2.1. Administrator ...................................................................................................................... 52
4.2.2. Airline .................................................................................................................................. 52
4.2.3. Booking ................................................................................................................................ 53
4.2. 4. Customer ............................................................................................................................. 53
4.2.5. Flight .................................................................................................................................... 54
4.2.6. Login .................................................................................................................................... 54
4.2.7. Payment ............................................................................................................................... 55
vi
4.2.8. Passenger ............................................................................................................................ 55
4.2.9 Reservation .......................................................................................................................... 56
4.2.9. Schedule ............................................................................................................................... 56
4.2.10 Seat..................................................................................................................................... 57
4.2.10. Ticket ................................................................................................................................. 57
5. COMPONENT DESIGN ..................................................................................................................... 58
5.1 Administrator ........................................................................................................................... 58
5.2 Login ........................................................................................................................................ 64
5.3User ........................................................................................................................................... 68
5.4 Customer .................................................................................................................................. 70
5.5 Payment ................................................................................................................................... 76
5.6 Booking .................................................................................................................................... 78
5.7 Flight ........................................................................................................................................ 80
5.8 Ticket ....................................................................................................................................... 83
5.9 Passenge .................................................................................................................................. 85
5.10 Airline .................................................................................................................................... 88
5.11 Reservation ............................................................................................................................ 90
6. HUMAN INTERFACE DESIGN ........................................................................................................... 93
6.1 Overview of User Interface ..................................................................................................... 93
6.2 Screen Images ......................................................................................................................... 93
6.2.1. Homepage ............................................................................................................................ 93
6.2.2. Registration .......................................................................................................................... 94
6.2.3. Login .................................................................................................................................... 95
vii
6.2.4. Add Customer Detail ........................................................................................................... 96
6.2. 5.Flight Detail ......................................................................................................................... 97
6.2.6. Online Reservation............................................................................................................... 98
6.2.7. Reservation Form ................................................................................................................. 99
6.2.8. Online Transaction ............................................................................................................. 100
6.2.9. Flight Status ....................................................................................................................... 101
6.2.10. Web Check In .................................................................................................................. 102
6.2.11. Cancel Reservation .......................................................................................................... 102
6.2.12. Contact Us........................................................................................................................ 103
6.1.13 Feedback ........................................................................................................................... 104
7. REQUIREMENTS MATRIX ....................................................................................................... 105
viii
Online Airline Reservation System (PIA)
1. INTRODUCTION
1.1 Purpose
The main purpose of Software Design Documents is to design all main components
and its sub components on Online Airline Reservation System. Designer of the site and
coder also used SDD to develop this project, so SDD is most important during development.
Tester and Management of the proposed software also use the Software Design Documents.
The SDD shows how the software system will be structured to satisfy the requirements
identified in the software requirements specification. This document exclusively depict the
system at architectural level including subsystems and their services, hardware mapping,
data management, access control, global software control structure and boundary conditions
. Its intended audience is the project manager, project team, and development team.
1.2 Scope
The software is developed can be used to provide the facility for the customer to book
the ticket online and to check the availability of tickets. It saves time as it allows online
process as users has no to longer wait in a line to reserve the flights. It is
automatically generated by the server. In the past people as to walk into travel agency or
this company ticket counter to buy the tickets. And also to check the flight timings . This
problem is reduce by introduce this problem solution "The Online Airline Reservation
System". The software is to reduce the errors come in the airline reservation process and
make it easy for the customers to book the flights as while they require such that they can
use this project to make reservations, modify reservations or cancel a particular reservation.
The project is to build a plan, change and performance of an Online Airline Reservation
System. This project is useful for the flight management team and as well as to the
passengers or customer
1.3 Overview
First section contain introduction of the project, second section of SDD contain
system overview, in this section describe overall system in high level definition. Third
section contains system architecture of the project; main components and its sub components
are define in section three. Four sections contain data design in this section design the
system using Entity Relationship Diagram and Data Flow Diagram etc. Selection five
contains component design, in which different comments are design. Section six of the SDD
contains Human Interface Design and Last section contains the Requirements Matrix.
SDD Document 1.0 Page |1 9/22/2019
1.4 Reference Material

IEEE standard 830-1998 recommended practice for Software Requirements Specifications
Description.
1.5 Definitions and Acronyms

OARS Online Airline Reservation System
SDD Software Design Document
PIN Passenger Identification Number
GUI Graphical User Interface
SRS System Requirement Specification
DB Database
PHP Personal Home Page
UML Unified Modeling Language
HTML Hyper Text Markup Language
2. SYSTEM OVERVIEW
2.1 Assumption
A laptop or desktop computer, internet connection and Browser are compulsory. All
the things are important to use reservation Site Properly. The project should be completed
within specified time period including Planning, Designing, Development, Testing and
Deployment. The project should be completed within specified budget. In this web
application the user assumes that the site will produce 100% accurate result because
accuracy is most important factor of any system.
2.2 Technology to be used

OARS require the support of additional software to for completion. It requires
MySQL to stores important data of airline system to maintain reservation system. Because
MySQL is an open source product and easy to used. OARS will require bootstrap 3 for
design purpose. Bootstrap contains CSS, HTML, J-Query and JavaScript functions.
Bootstrap will be used to front end design. OARS use local web server for testing to include
Apache Web Server 2.0, PHP 5.0 and MySQL. The system is coded with PHP
programming. Get-Hub also used for store our project coding online on the internet.
Technology play important role in every field of life. The developer of the application will
require a local web server because MySQL server is costlier and is not affordable for him or
her.
2.3 Design Language
UML is used for to graphical representation of the project. Entity Relationship
diagram, Data Flow Diagrams, Class Diagrams, Activity Diagrams, Sequence Diagrams and
State Machine Diagrams also used during development of Web Based Crime Control
System.
2.4 Application Overview
The main objective of this application is that when any user enters into site. User can
get information about Admin, User, reservation detail and other necessary details which help
full to the user. OARS provide the online reservation facility for the customer, customer can
get detailed about reservation scheduled, customer can check eligibility criteria for
reservation and customer can access their account to view their prospective.
Online Airline Reservation System (OARS) can be run on window and android OS. It is
easy the task of Airline Reservation System. This project also gives an opportunity to user
that user can give feedback and suggestion about our site so that admin must consider these
suggestions. Admin must have account. He can change delete and post information about
reservation.
2.5 General Constraints

It is a web access for all customer and member function. It is a user friendly website.
In Software constraints included operating system –windows/Linux, data base-MY SQL,
Web server-XAMP and platform-PHP. The designer will also need a vector and/or raster
image editor such as Adobe® Illustrator/InkScape or Adobe® Photoshop/GIMP. For
publishing the application the provider must have Apache Web Server 2.0, PHP 5.0, and
MySQL 5.1 or higher and have the ability to include WordPress® Blog.
2.6 System Environment

OARS will be able to run on all versions of Windows operating system. It will also
run on android operating system. User can utilize service of OARS on android mobile phone
easily via web services.

3. SYSTEM ARCHITECTURE
3.1 Web Architecture

The OARS will run on a client-server system architecture where the client will
connect to a web server using a current internet browser and TCP/IP connection. The web
server is maintained by the Apache® web server. The web server will communicate with a
MySQL database and interact with Google® Maps API using client and server side scripting.
Web Application communication with Web Server, Web Server further communicate with
Database to save data into database or get data from database.
Internet
Web Application
Web server
Database
3.2.1 Architectural Design

OARS contain different modules. These modules are combined to provide services to
user. OARS include various modules such Registration, reservation, airlines, ticket
management, services, passenger, employee. Registration modules manage information about
registration and login .Reservation modules manage the reservation information such as make
reservation, cancel reservation and modify reservation. Airlines modules provide the
information about airline system such as their schedule and their services. Ticket modules

provide information about ticket and their payment information. Passenger modules contain
information about passenger such as name, address, email etc. Employee module provide
information about employee that work in airline system such as manager, worker etc. All
these modules are combined to achieve entire functionality of OARS.
User User User User User User User
Registratio Airline Ticket Service Reserva Payme Administ

n/Login s Manageme s tion nt rator
nt
OARS
Web Server
My SQL
3.2 Decomposition Description
3.2 Decomposition Description

Registration process of the OARS is use to register new people like customer and
administrator etc and log in is used to access his/her account. User of the site is mostly
customer and other people who want to get information from any flight. Different
documents like word file, power point, PDF file is stored on OARS which help user to
provide his/her information.

3.2.1 Use Cases

This section contains use cases of the Online Airline Reservation System (OARS).
3.2.1.1 Registration
System
Registration
User User
Name Description
Actor User
Goal It will register a new user into database.
Pre-condition User wants to register in OARS.
Actor Steps 1. User click on reservation menu.
2. User enters email and password.
3. User can do future work.
System Steps 1. System show login page
2. System will check in database and log him
in.
Post-condition User successfully registered in OARS.

3.2.1.2 Login
System
Login
User User
Name Description
Actor User
Goal User login in OARS.
Pre-condition User want to login in OARS.
Actor Steps 1. User open OARS site.
2. User select sign up option
3. User fills up user name, contact number,

address, and set password.
System Steps 1. System will register him.
Post-condition User successfully registered.

3.2.1.3 Search Flight
System
login
<<include>>
search for flight
User User
<<include>>
logout
Name Description
Actor User
Goal It helps us for searching our concern flight.
Pre-condition User should open the home page for searching flight.
Actor Steps 1. User click on search flight option.
2. User enters source and destination for search
flight.
System Steps 1. System show him match flight detail.
2. System will display concern flight.
Post-condition Users successfully search the concern flight.

3.2.1.4 Make Reservation
System
login
<<include>>
Make Reservation
User User
<<include>>
logout
Name Description
Actor User
Goal It helps us for making reservation.
Pre-condition User wants to make reservation.
Actor Steps 1. User will login.
2. User select type of Class.
3. Users enter the destination.
System steps 1. System will check his authority.
2. System will check the availability of that
option.
3. System will check the availability of flight.
Post-condition Reservation has been made and database should be update.

3.2.1.5 Modify Reservation
System
login
<<include>>
Modify Reservation
User User
<<include>>
logout
Name Description
Actor User
Goal User can modify his reservation if he commits
some mistake.
Pre-condition User wants to modify reservation.
2. User select edit option.
3. Users will change his flight detail.
System Steps 1. System verifies him from database.
2. System will display him his detail saved in
database.
3. System updates the database and show message.
Post-condition The user successfully modifies the reservation.
SDD Document 1.0 P a g e | 10 9/22/2019

3.2.1.6 Cancel Reservation
System
login
<<include>>
Cancel Reservation
User User
<<include>>
logout
Name Description
Actor User
Goal It helps the user to cancel his reservation.
Pre-condition User wants to cancel his reservation.
2. User select update option.
3. Users will change his flight detail
System Steps 1. System verifies him from database.
2. System gives him a warning message.
3. System updates the database and show
message.
Post-condition System should cancel reservation after check
database record.

3.2.1.7 Payment
System
confirm order
<<include>>
payment
User User
Name Description
Actor Customer
Goal Customer can be paying their bill by credit card or check.
precondition After confirm their reservation will be paying their bills.
description The customer can be pay their bill after confirm their reservation.
1. Click on payment option.
Steps 2. Processing and find the Option.
3. Display the option.
Post condition They can be paying their bill at a time.

3.2.1.8 Add Flight Information
System
login
<<include>>
Add Flight Information
Administrator Administrator
<<include>>
logout
Name Description
Actor Administrator
Goal If the administrator wants to add flight
information into database.
Pre-condition The administrator wants to add flight
information.
System steps 1. Administrator login in OARS site.
2. Administrator adds new flight information.
3. Select the new flight of OARS site
Post-condition The administrator successfully adds new
schedule in the database.

3.2.1.9 Modify Flight Information
System
login
<<include>>
Modify Flight Information
<<include>>
logout
Name Description
Actor Administrator
Goal If the administrator wants to update flight
Pre-condition The administrator wants to update flight
information.
Actor steps 1. Administrator login in OARS site.
2. Administrator updates information.
3. Select the flight to update of OARS site
Post-condition The administrator successfully updates flight in
the database.

3.2.1.10 Delete Flight Information
System
login
<<include>>
Delete Flight Information
<<include>>
logout
Name Description
Actor Administrator
Goal If the administrator wants to delete flight
Pre-condition The administrator wants to delete flight
information.
2. Administrators delete information.
3. Select the flight to delete of OARS site
Post-condition The administrator successfully deletes flight in
the database.

3.2.1.11 Add Customer Information
System
login
<<include>>
Add Customer Information
<<include>>
logout
Name Description
Actor Administrator
Goal If the administrator wants to add customer
Pre-condition The administrator wants to add customer
information.
2. Administrator adds new customer
information.
3. Select the new customer of OARS site
Post-condition The administrator successfully adds new
customer information in the database.

3.2.1.12 Update Customer Information
System
login
<<include>>
Modify Customer Information
<<include>>
logout
Name Description
Actor Administrator
Goal If the administrator wants to update customer
Pre-condition The administrator wants to update flight
information.
2. Administrator updates flight information.
3. Select the new flight of OARS site
Post-condition The administrator successfully updates customer information
into the database.

3.2.1.13 Delete Customer Information
System
login
<<include>>
Delete Customer Information
<<include>>
logout
Name Description
Actor Administrator
Goal If the administrator wants to delete customer
Pre-condition The administrator wants to delete customer
information.
2. Administrator deletes customer information.
3. Select the delete flight of OARS site
Post-condition The administrator successfully deletes customer information
from the database.

3.2.1.14 Contact Us
System
login
<<include>>
Contact Us
User User
Name Description
Actor User
Description User can also contact us by this contact us page user

can get all the detail about contact mobile no , fax no ,
email and address
Pre condition User wants to contact with OARS.
Steps 1. User can click on the contact us. And then all the
detail of contact is available on site.
2. User can note them and contact us by any way
Post-condition After check detail user can approach us.

3.2.1.15 Feedback
System
login
<<include>>
Feedback
User <<include>> User
logout
Name Description
Actor User
Description Customer first login and after login he can sent feedback to system.
Precondition Customer wants to send Feedback.
Actor steps 1. User can click on the feedback option.

2. User entered his email.
3. Then on textbox user entered his feedback and click on the send
Option.
System Steps After feedback user can get response by administrator.
Post Condition Feedback has been sent successfully.

3.2.1.16 View Schedule
System
View Schedule
User User
Actor Administrator
Pre-condition User wants to login to view schedule.
Post-Condition The user successfully views the schedule in the database.
Description In this site user able to view the schedule on database if successfully login.
Steps 1) User login the site.

2) User view schedule option.
3) Select the cities.

3.2.1.17Logout
System
login
<<include>>
logout
User User
Name Description
Actor User
Goal User session will destroy and it will bring
user to main page.
Pre-condition User want to logout.
Actor Steps 1. User login.
2. User select logout option.
System steps 1. System verifies him from database.

2. System will close session and home page
will display.
Post-condition User successfully logout and home page will
be display.

3.2.2 Sequence Diagram
3.2.2.1 Login
: Customer : Login
1 : Login()
2 : verify information()
3 : validateSuccessfully()
4 : errorMessageInvalid()
5 : forgetPassword()
6 : getSecretInformation()
7 : passwordInforamationCorrect()
8 : errorMessageIfIncoerrect()
9 : resetPassword()
10 : verifypassword()
11 : resetSuccessfullyIfValid()
12 : errorMessageIfInValid()

: passenger : ReservationSysten : ReservationManager : ReservationList
1 : makeReservation()
2 : enterPin()
3 : verifyPin()
4 : valid()
5 : askForDestination()
6 : destination()
7 : reserve()
8 : addReservation()
9 : makeReservationSuccessfully()

: Passenger : Clerk : Ticket
1 : requestmodifyresrvation()
2 : ModifyForm()
3 : modifylReservation()
4 : confirm()
5 : createModifyTicket()
6 : modifyForm()
7 : modifyReservation()
8 : ModifyReservationSuccessfully()

: Passenger : Clerk : Ticket
1 : requestForm()
2 : cancellationForm()
3 : cancelTicket()
4 : confirm()
5 : createTicket()
6 : modifyForm()
7 : deleteTicket()
8 : addToAvailable()
9 : calculateFIneAndRefundBalance()

3.2.2.5 Add Customer Information
: User Admin : Database
1: Give personal detail ()
2: Provide Information ()
3: Re-Enter information if not valid ()
4: Valid Information ()
5: Add Customer Information ()
6: Add information successfully ()

3.2.2.6 Update Customer Information
: User Admin : Database
5: Modify Customer Information ()
6: Modify information successfully ()

3.2.2.7 Delete Customer Information
: User : Admin : Database
5: Delete Customer Information ()
6: Delete information successfully ()

3.2.3 State-Transition Diagrams (STD)
3.2.3.1 Login

3.2.3.3 Update Reservation


3.2.4 Activity Diagram
3.2.4.1 Login
Enter Login ID
validate login Id
invalid
Invalid user
valid
Check availability of seats
is available
Yes
No
Invalid Info
Display Reservation Form

User LoginID Authentication
if valid
Yes No
Display Reservation Form Request For Reservation Invalid user
Submit reservation form verify reservation detail
is valid
Yes
No
Invalid Info
Reservation Successfully

Login
validate login Id
invalid
Invalid user
valid
Request cancel reservation verify detail
is valid
Yes
No
Invalid Info
cancel Successfully

Login
validate login Id
invalid
Invalid user
valid
Request modify reservation verify detail
is valid
Yes
No
Invalid Info
modify reservation Successfully

3.2.4.5 Flight
Enter Flight ID
verification
Exit
Reserve
Flight status Flight Detail
Display Message

3.2.4.6 Payment
Receive Payment Validate Credit Card
Rejected Accepted
Finalize Reservation

3.2.5 Class Diagram

3.2.5.1 Login
Login
-email_Id: int
User Database
-name: string
-name: string -password: int -databaseName: string
-email_Id: int
+login() -password: int
-password: int
+resetPassword() +insertRecord()
+login() +forgetPassword() +updateRecord()
+searchSeats() 0..* 0..* +logout() +deleteRecord()
+logout() +getemailID() +saveRecord()
+selectSeats() +setemailID() +searchRecord()
+giveSuggestion() +getName() +insertTable()
+setName() +updateTable()
+getPassword() +deleteTable()
+setPassword()
Customer
Adminintrator maintain
-name: string
-phone_No: int -email_Id: int
-email: string -name: string
-password: int -password: int
-gender: string
+registration()
+login() +login()
+logout() +cancelReservation()
+visitWebsite() +verifyReservation()
+search() +maintainRecord()
+makeReservation() +changeSchedule()
+confirmReservation() +updateSchedule()
+payment() +addDetail()
+getServices() +viewDetail()
+updateProfile() +searchDetail()
+editAccount() +updateDetail()
+deleteAccount() +deleteDetail()
+createAccount() +updateNotice()
+searchAccount() +changePolicies()
+getBookingStatus() +logout()
+pickUpInformation()

3.2.5.2 Booking
User
Booking
-name: string PassengerCatalog
-bookingId: int 1
-email_Id: int
-password: int -bookingDate: date 0..* +getPassenger()
-bookingDescription: string
+login() -bookingTitle: string
+searchSeats()
+logout() +addBooking()
+selectSeats() +editBooking() Database
+giveSuggestion() +searchBooking()
+deleteBooking() -databaseName: string
-password: int
1
+insertRecord()
+updateRecord()
Customer +deleteRecord()
+saveRecord()
-name: string Flight +searchRecord()
-phone_No: int -number: int +insertTable()
-email: string -departure: string +updateTable()
-password: int 1..*
-arrival: string +deleteTable()
+registration() -price: int
+login() Booking 1..* +addFlight()
+logout() +editFlight()
0..*
+visitWebsite() +deleteFlight()
+search() +updateFlight()
+makeReservation()
+confirmReservation()
+payment()
from to
+getServices()
+updateProfile()
+editAccount() Airline
+deleteAccount() Airport
-airlineName: string
+createAccount() -name: string -flightNumber: int
+searchAccount() -country: string +countryName: string
+getBookingStatus() -code: int
+pickUpInformation() +addDetail()
-fee: float
+updateDetail()
+deleteDetail()

3.2.5.3 Airline
Airline
-airlineName: string
-flightNumber: int
-countryName: string
Country +addDetail()
-countryCode: int +updateDetail()
-countryName: string +deleteDetail()
0..1
origin FlightDescription Aircraft

Airport *
1
-flightName: string * -registrationNumber: int
-airportName: string -flightNo: int -manufacturer
destination 1
-airportCode: int -modelNumber: int
1 * +scheduleDepartTime()
+scheduleDuration()
1
* 0..1
Direction Flight
-originAirportCode: int -number: int
+destinationAirportCode: int -departure: string FlightStatus
-arrival: string -flightStatusId: int
-price: int -name: string
+addFlight()
+editFlight()
+deleteFlight()
+updateFlight()
FlightSchedule
-flightNumber: int
-scheduleId: int
+source: string
-destination: string
-arrivalTime: Date
+depatureTime: Date

3.2.5.4 Flight
Customer Passenger
Order
-name: string -name: string
-phone_no: int -number: int -phone_no: int
-address: string -price: float 1..* -address: string
-email: string -payment -password: string
0..1
-password: string +Order() +updatePersonalInformatrion()
+registration() +setState() +signup()
+login()
1..* +getPrice() +deleteAccount()
+logout() 0..1 +updateAccount()
1..*
+viewWebsite()
+search()
+makeReservation()
+payment()
+getServices() 0..1
+editAccount()
+updateProfile() ScheduleFlight Schedule
+Search() -scheduleData: string -scheduleId: int
user +deleteAccount() -capacity: string -name: string
+email_Id: int +createAccount() -passengers: int 0..1 1..*
+name: string +searchAccount() +addFlight()
-currentPrice: float
+password: int +getBookingStatus() +deleteFlight()
+pickUpInformation() +updateFlight()
+searchSeats()
+selectSeats()
+giveSuggestion()
Flight Airport
-number: int -name: string
Adminintrator -departure: string -code: int
-email_Id: int -arrival: string 1..*
-location
-name: string -price: int 0..1
+getPrice()
-password: int +addFlight()
-gender: string +editFlight()
+addSeats() +deleteFlight()
+cancelReservation() +updateFlight()
+addDetail()
1
+updateDetail()
+changeSchedule()
maintan
+updateSchedule() Database TimingList
+updateSeats()
-databaseName: string -flightName: string
+login()
-email_Id: int 1 1 -time: date/time
+logout()
-password: string -source: string
+insertTable() -destination: string
+updateTable()
+insertRecord()
+updateRecord()
+deleteRecord()
+maintainRecord()

3.2.5.5 Ticket Management
Customer
-name: string
-phone_no: int
-address: string
-email: string Ticket
-password: string Seat CancelTicket
-ticketNo: int
+registration() -sourceLocation: string -ConfirmationNo: int -confirmationNo: int
+login() -destinationLocation: string -seatNo: int -cancellationDate: Date
+Logout() -passengerNumber: int -name: string -deduction: float
+visitWebsite() books 1..* -ticketTitle: string -age: int -amount: float
+search() -confirmationNo: int
+makeReservation() 1..*
+confirmReservation() +addTicket()
+payment() +editTicket() Flight
+getServices() +searchTicket() -number: int
+updateProfile() +deleteTicket() -departure: string
+editAccount() -arrival: string
+deleteAccount() -price: int
+createAccount()
User +searchAccount() +addFlight()
visits +editFlight()
+getBookingStatus()
-email_Id: int +deleteFlight()
-name: string 1 +updateFlight()
-password: int
Database 1 *
+searchSeats()
-databasename: string
+selectSeats()
-email_Id: int
+giveSuggestion() Adminintrator -password: int
1
-email_Id: int +insertTable()
-name: string +updateTable()
1 Schedule
-password: int
-gender: string maintains +deleteTable() -scheduleID: int
+insertRecord()
+updateRecord() -source: string
+login() 1
+deleteRecord() -destination: string
+cancelReservation()
-departureTime: DateTime
+verifyReservation()
-arrivalTime: DateTime
+maintainRecord() 1 1
+changeSchedule()
+updateSchedule() TimingList
+addDetail() -flightName: string
+deleteDetail() -time: date/time
+updateDetail() -source: string
+updateNotice() -destination: string
+changePolicies()
+logout()

3.2.5.6 Reservation
Adminintrator
-email_Id: int
-name: string
-password: int
-gender: string user
+addSeats() +email_Id: int
+cancelReservation() +name: string
+addDetail() +password: int
+updateDetail() +searchSeats()
+changeSchedule() +selectSeats()
+updateSchedule() +giveSuggestion()
+updateSeats()
+login()
+logout()
maintain
Customer
Database
-name: string
-databaseName: string -phone_no: int
-email_Id: int -address: string
-password: string -email: string
Payment
+insertTable() -password: string
+updateTable() +registration() -amount: float
+insertRecord() +login() -date: Date
pays -detail: string
+updateRecord() +logout()
+deleteRecord() +viewWebsite() +netBanking(): float
+maintainRecord() +search() +payOnline(): float
+makeReservation()
+payment()
+getServices()
Agent +editAccount() ConfirmReservation
+updateProfile()
-name: string +Search() -confirmationId: int
1..*
-email_Id: int +deleteAccount() -ticketNo.: int
1..*
-password: string request
+createAccount() -date: Date
+searchAccount() -payment: float
1 +getBookingStatus()
1
1
1
Gets Reservation
Ticket books
Request
-reservationId: int
-ticketNo: int -reservationDate: date
Refund
-sourceLocation: string -reservationTicket: string
1
-destinationLocation: string -account: float -reservationdescription: string
-passengerNumber: int -customerId: int -reservationtitle: string
-ticketTitle: string +refundAmount() +addReservation()
+addTicket() 1..* +editReservation()
+editTicket() 1 reserve +searchReservation()
+searchTicket() +deleteReservation()
1 +saveReservation()
+deleteTicket()

3.2.5.7 Payment
User Adminintrator
-email_Id: int -email_Id: int
-name: string -name: string
-password: int -password: int
-gender: string
+searchSeats()
+selectSeats() +login()
+giveSuggestion() +cancelReservation()
+verifyReservation()
+maintainRecord()
+changeSchedule()
+updateSchedule()
Customer +addDetail()
-name: string +deleteDetail()
-phone_no: int +updateDetail()
-address: string +updateNotice()
-email: string +changePolicies()
-password: string +logout()
maintain
+registration()
+login()
+Logout() Payment Database
+visitWebsite()
+search() -amount: int -databasename: string
+makeReservation() * -date: date -email_Id: int
+confirmReservation() 1 -detail: string -password: int
+payment() +payOnline() +insertTable()
+getServices() +netBanking() +updateTable()
+updateProfile() +deleteTable()
+editAccount() +insertRecord()
+deleteAccount() +updateRecord()
+createAccount() +deleteRecord()
+searchAccount()
+getBookingStatus()
Credit Check
Cash -number: int -name: string
-type: string -bankID: int
+cashTendered
-expDate: date +accountNo.: int
+return()
+authorized() +authorized()
+deduction()
+addCreditInformation() +addCheckInformation()
+takePayment()
+deleteCreditInformation() +deleteCheckInformation()
+updateCreditInformation() +updateCheckInformation()

3.2.5.8 ENTIRE SYSTEM
Registration user PassengeCatalog

Login
-name: string -email_Id: int
-phone_no: int -email_Id: int -name: string 0..* 1 +getPassenger()
-address: string -name: string -password: int
Adminintrator
-password: string -password: int
+searchSeats()
0..* +selectSeats() -email_Id: int
+updatePersonalInformatrion() +login()
-name: string
+signup() +resetPassword() 0..* +giveSuggestion()
-password: int
+deleteAccount() +forgetPassword()
-gender: string
+updateAccount() +logout()
+getName() +getemailID() +login()
+setName() +setemailID() +cancelReservation()
+getPhoneNo.() +getName() +verifyReservation()
+setPhoneNo.() +setName() +maintainRecord()
+getAddress() +getPassword() +changeSchedule()
+setAddress() +setPassword() Customer +updateSchedule()
+getPassword() +addDetail()
-name: string
+setPassword() +updateDetail()
-phone_no: int
+searchDetail()
-address: string
+deleteDetail() TimingList
-email: string
Flight +updateNotice()
-password: string -flightName: string
+changePolicies()
-number: int -time: date/time
+registration() +logout()
-departure: string -source: string
+login()
-arrival: string FlightCatalog -destination: string
+logout() 1
-price: int maintain
0..* 1 +getFlight() +viewWebsite() 1
+addFlight() +search()
1
+editFlight() +makeReservation()
1
+deleteFlight() +confirmReservation() Database
+updateFlight() +payment() visits
1
+getServices() -databaseName: string
1..* -email_Id: int
1 +updateProfile()
+editAccount() -password: string
1 +deleteAccount()
+insertTable()
1..* +createAccount() +updateTable()
0..* +searchAccount() 1..* +insertRecord()
Booking +getBookingStatus() +updateRecord()
+pickUpInformaton() +deleteRecord()
-bookingId: int
books
-bookingDate: date
-bookingdescription: string 1..*
-bookingtitle: string Ticket
+addBooking() -ticketNo: int
+editBooking() -sourceLocation: string
+searchBooking() -destinationLocation: string
+deleteBooking() -passengerNumber: int
-ticketTitle: string
+addTicket()
+editTicket()
+searchTicket()
+deleteTicket()

3.3 Design Rationale

An OARS is developed with modular strategies. In modular programming equivalent
coding, testing is perform the result in quick development. Because system develop in
smaller modules is to handle, code, test and maintain. In OARS MySQL database is used to
defend the advantage of Airline System because it is open source and free of cost and php
script is used to connect to database. In Online Airline Reservation System we use HTML,
PHP, and MY SQL database. Client side technology HTML, SERVER side technology
PHP, both is efficient, and open ended. We use SQL database because it’s free, efficient and
open ended.
4. DATA DESIGN
4.1 Data Description
In OARS data is preserved using MySQL database. Data about student, teacher,
admin, admission, attendance, courses, exam and result is stored in MySQL database using
PHP script. MySQL database is used to store all the information of Online School
Management system. PHP script is used to manipulate the information, get information from
the database or put information into database a local web server also used with PHP script.
Data delete and update through PHP script. Data stored on Local server.
4.1.1 Data Objects
4.1.1.1 Administrator
Email Id Email id of admin that will be used for login to system.
Password Password of the administrator to access the system.
Admin name It indicates the name of administrator.
Gender Gender of administrator MALE/FEMALE.

4.1.1.2. Login
Email Id Email id of admin/customer that will be used for login to system.
Password Password of the administrator/customer.
Name Indicate the name of administrator/customer
4.1.1.3. Customer
Name Indicate the name of the customer.
Phone No Phone number is used for communication with student.
Address Show the present address of customer.
Email Id Email id of customer that will be used for login to system.
Password password of user used to login in application and password used to

secure form unauthorized user.
4.1.1.4. Payment
Amount Payment of ticket that will be pay by the customer.
Date It defines the date of the payment.
Detail ]It defines the detail of the payment system by cash and by credit card.
4.1.1.5. Ticket
Ticket No Define the ticket number that provides to the customer.
Source Location It indicates the source location.
Source Location It indicates the destination location.
Passenger Define the passenger number who got the ticket.
Number

4.1.1.6. Booking
Booking id It indicate the booking Id.
Booking date It defines the booking date of flight booked by the customer.
Booking It defines the Booking description of the Flight.
Description
Booking title Defines the booking title.
4.1.1.7. Flight
Flight Number Defines the flight number that indicates the flight.
Departure Define the departure time of flight.
Arrival Defines the arrival time of the flight.
Price It define the price of the ticket according to flight.
4.1.1.8. Airline
Airline Name Indicate the name of the airline system that may be unique.
Flight No It indicates the flight number of airline system

Country Name It indicates the country name from which passenger travel.
4.1.1.9. Schedule
ID It indicates the schedule Id that must be unique.
Flight Time It defines the flight time of the flight.
Date It define the flight date and schedule of flight.

4.1.1.10. Passenger
Name Indicate the name of the passenger.
Phone No. Phone number is used for communication with student.
Address Show the present address of passenger.
Password Password of user used to login in application and password used to

keep secure form unauthorized user.
4.1.1.11 Seat
Confirmation It indicates confirmation no. of ticket that give to passenger after
making reservation.
No.
Seat No. It indicates the seat no. of Airline that the passenger reserves.
Name Show the name and no of the seat.
Age It indicates the age of the passenger that make reservation.
4.1.1.12 Reservation
ReservationID Indicate the name of the reservation Id.
ReservationDate It indicates the reservation date of ticket.
ReservationTicket It indicates the reservation ticket of booking.
Reservation It indicates the description of the reservation system. It also

describes the description of payment.
Description
ReservationTitle It indicates the reservation title of ticket.

4.1.2 ER Diagram of Online Airline Reservation System

4.2 Data Dictionary
4.2.1. Administrator
Parameter Parameter Type
Email Id Int
Password String
Admin name String
Gender String
4.2.2. Airline
Airline Name String
Flight No Int
country Name string

4.2.3. Booking
Booking id Int
Booking date Date
Booking Ticket String
Booking Description String
Booking title String
4.2.4. Customer
Name String
Phone No Int
Address String
Password String

4.2.5. Flight
Flight Number Int
Departure String
Arrival String
Price Float
4.2.6. Login
Email Id String
Password Int
Name String

4.2.7. Payment
Amount Float
Date Date
Detail String
4.2.8. Passenger
Name String
Phone No Int
Address String
Password Int

4.2.9 Reservation
ReservationID Int
ReservationDate Date/Time
ReservationTicket string
Reservation String
Description
ReservationTitle String
4.2.10. Schedule
ID Int
Flight Time Date/Time
Date Date

4.2.11 Seat
Confirmation No. Int
Seat No. Date/Time
Name String
Age Date
4.2.12. Ticket
Ticket No Int
Source Location String
Destination Location String
Passenger Number Int

5. COMPONENT DESIGN
5.1 Administrator
Class Name Administrator

Administrator is a user of OARS who is responsible for add,
Description
delete, update etc.
Attribute Name Attribute Description
adminName:
It indicates the name of administrator.
emailId: Email id of admin that will be used for login to system.
password:
Password of the administrator to access the system.
gender:
Gender of administrator MALE/FEMALE.
Operation(methods) Description
logIn() An Operation that is used for login Admin.
Pseudo Code:
1.Start
2. login( int Email _Id, string password)
{
3. Input Email Id and password from user.
4.Validation information
5.Successfully login
else
6.Show error message
}
7.End
makeReservation() An operation that is used for make reservation by Passenger.
Pseudo code:
1.Start

2. make reservation (int Id, int password)

{
3 Input name, Id, password, phone no.
4.Validation of entered data
5. Database connection is created.
6. Administrator must be login for make reservation.
7.create Account
8. Successfully make reservation.
else
9.Error message
}
10.End
cancelReservation() An operation that is used for cancel reservation by Passenger.
Pseudo code:
1.Start
2. cancel reservation (int Id, int password)
{
6. Administrator must be login for cancel reservation.
7.create Account
8. Successfully cancel reservation.
else
9.Error message
}
10.End
confirmReservation() An operation that is used for confirm reservation by Passenger.
Pseudo code:
1.Start
2. confirm reservation (int Id, int password)
{


6. Administrator must be login for confirm reservation.
7.create Account
else
9.Error message
}
10.End
maintainRecord() An operation that is used for maintain record by Passenger.
Pseudo code:
1.Start
2. maintain Record (int Id, int password)
{
6. Administrator must be login for maintain record.
7.create Account
8. Successfully maintain record.
else
9.Error message
}
10.End
updateSchedule() An operation that is used for update schedule by Passenger.
Pseudo code:
1.Start
2. update Schedule(int Id, int password)
{
6. Administrator must be login for update Schedule.

7.create Account
8. Successfully update schedule.
else
9.Error message
}
10.End
changeSchedule() An operation that is used for change schedule by Passenger.
Pseudo code:
1.Start
2. change Schedule(int Id, int password)
{
6. Administrator must be login for change Schedule.
7.create Account
8. Successfully change schedule.
else
9.Error message
}
10.End
updateNotice() An operation that is used for update Notice by Passenger.
Pseudo code:
1.Start
2. update Notice (int Id, int password)
{
6. Administrator must be login for update Notice.
7.create Account
8. Successfully update Notice.
else

9.Error message
}
10.End
changePolicies() An operation that is used for change Policies by Passenger.
Pseudo code:
1.Start
2. change Policies (int Id, int password)
{
6. Administrator must be login for change Policies.
7.create Account
8. Successfully change Policies.
else
9.Error message
}
10.End
addDetail() An operation that is used for add detail by admin.
Pseudo code:
1.Start
2. add Detail(int Id, , int password)
{
3 Input id, password
6.Add record
7.Successfully add detail
else
8.Error message
}
9.End
updateDetail() This operation is used for update detail.

Pseudo Code:
2. update Detail(int Id, , int password)
{
3 Input id, password
6.update record
7.Successfully update detail
else
8.Error message
}
9.End
deleteDetail() This operation is used for delete detail.
Pseudo Code:
1.Start
2.delete Detail(int ticket Id)
{
3 Input Id, password.
6.if detail available
7.delete detail
8. Show message successfully delete detail.
else
9.Error message
}
}
10.End

5.2 Login
Class Name Login
Description The login class is responsible for the login the user.
name: It indicates the name of user or administrator.
emailId: Email id of admin or user that will be used for login to system.
password: Password of the administrator or user to access the system.
registration() An Operation that is used for registration.

Pseudo Code:
1.Start
2. registration ( int Email _Id, string password)
{
5.Successfully registered.
else
}
7.End
login() An Operation that is used for login.
Pseudo Code:
1.Start
{

else
}
7.End
viewWebsite() An Operation that is used for view Website.
Pseudo Code:
1.Start
2. view Website ( int Email _Id, string password)
{
5. Successfully view website.
else
}
7.End
Pseudo code:
1.Start
{
7.create Account
else
9.Error message
}
10.End


Pseudo code:
1.Start
{
7.create Account
8. Successfully confirm reservation.
else
9.Error message
}
10.End
Payment() An operation that is used for payment.
Pseudo code:
1.Start
2. payment (int Id, int password)
{
6. Administrator must be login for make payment.
7.create Account
8. Successfully pay payment.
else
9.Error message
}
10.End

This is the description of the method used to forget password.

resetPassword() Pseudo code:
1.Start
2. reset Password(int Id, , int password)
{
3 Input id, name, password
6.Add record
7.Successfully reset password
else
8.Error message
}
9.End
This is the description of the method used to forget password
forgetPassword() Pseudo Code:
1.Start
2.forget Password(int Id, , int password)
{
6.Add record
7. Successfully recover password if forget.
else
8.Error message
}
9.End
An Operation that is used for logout.
logout () Pseudo Code
1.Start
2. logout( int Email _Id, int password)
{


5.Successfully logout.
else
}
7.End
5.3 User
Class Name User
Description The login class is responsible for the login the user.
name: It indicates the name of user or administrator.
emailId: Email id of admin or user that will be used for login to system.
password: Password of the administrator or user to access the system.
searchSeat() An Operation that is used for search seat.

Pseudo Code:
1.Start
2. search Seat( int email, int password)
{
4. User login for search seats.
5. User Successfully search seat.
else


}
7.End
selectSeat() This is the description of the method used to select seat.
Pseudo code:
1.Start
2. select Seat(int Id, , int password)
{
6. User login for search seats before selecting.
7. User Successfully select desired seat.
else
8.Error message
}
9.End .
give_Suggestion() This is the description of the method used to select seat.
Pseudo code:
1.Start
2. give Suggestion(int Id, , int password)
{
5. User login for giving suggestion.
7. User Successfully login and give suggestion.
else
8.Error message
}
9.End .

5.4 Customer
Class Name Customer
Description Customer is a user of OARS who is responsible for add, delete,

update account etc.
name: It indicates the name of Customer.
Email Id: Email id of Customer that will be used for login to system.
Password: Password of the Customer to access the system.
Phone No.: Phone no. of the customer to contact with customer.
registration() An Operation that is used for registration customer.

Pseudo Code:
1.Start
2. registration( int Email _Id, string password)
{
else
}
7.End
logIn() An Operation that is used for login customer.
Pseudo Code:
1.Start

{
else
}
7.End
Pseudo code:
1.Start
{
7.create Account
else
9.Error message
}
10.End
cancelReservation() An operation that is used for cancel reservation by Passenger.
Pseudo code:
1.Start
2. cancel Reservation (int Id, int password)
{
7.create Account


else
9.Error message
}
10.End
Pseudo code:
1.Start
{
7.create Account
else
9.Error message
}
10.End
payment() An operation that is used for payment.
Pseudo code:
1.Start
2. payment (int Id, int password)
{
6. Administrator must be login for make payment.
7.create Account
8. Successfully pay payment.
else
9.Error message

}
10.End
getServices() An operation that is used for get services by Passenger.
Pseudo code:
1.Start
2. get Services(int Id, int password)
{
6. Administrator must be login for gets services of websites.
7.create Account
8. Successfully update schedule.
else
9.Error message
}
10.End
updateProfile() An operation that is used for update profile by Passenger.
Pseudo code:
1.Start
2. update profile(int Id, int password)
{
6. Administrator must be login for update profile.
7.create Account
8. Successfully update profile.
else
9.Error message
}
10.End

editAccount() An operation that is used for edit account by customer.

Pseudo code:
1.Start
2. edit Account(int Id, , int password)
{
6.edit Account
7.Successfully edit Account
else
8.Error message
}
9.End .
createAccount() An operation that is used for create account by customer.
Pseudo code:
1.Start
2. create Account(int Id, int password)
{
6. Customer must be login for create account.
7.create Account
8. Successfully create Account.
else
9.Error message
}
10.End
deleteAccount() An operation that is used for delete account by customer.
Pseudo code:
1.Start
2. delete Account(int Id, , int password)

{
6.delete Account
7.Successfully delete Account
else
8.Error message
}
9.End
searchAccount() An operation that is used for search account by customer.
Pseudo code:
1.Start
2. search Account(int Id, , int password)
{
6. Customer must be login for search account.
7. search Account
8. Successfully search Account.
else
9.Error message
}
10.End .
getBookingStatus() An operation that is used for get booking status by Passenger.
Pseudo code:
1.Start
2. get Booking Status(int Id, int password)
{

6. Administrator must be login for gets Booking Status.

7.create Account
8. Successfully get Booking Status.
else
9.Error message
}
10.End
pickUpInformation() An operation that is used for pick up information by Passenger.
Pseudo code:
1.Start
2. pick Up Information (int Id, int password)
{
6. Administrator must be login for pick up information.
7.create Account
8. Successfully pick up information.
else
9.Error message
}
10.End
5.5 Payment
Class Name Payment
Description Customers pay payment after making reservation or booking ticket.
amount It indicates the amount of seat reservation.

date It indicates the date for which the user booked seat.
detail It contains the detail about the payment.
payOnline () An operation that is used for payment by online.

Pseudo code:
1.Start
2. pay Online(int Id, , int password)
{
6. User must login before payment by online.
7. User pays payment online Successfully.
else
8.Error message
}
9.End .
netBanking() An operation that is used for payment by check.
Pseudo code:
1.Start
2. net Banking(int Id, , int password)
{
6. User must login before payment by check.
7. User pays payment Successfully.
else
8.Error message
}

9.End.
5.6 Booking
Class Name Booking
Description It contain all the information about booking such as add booking
information, delete booking information, edit booking information,
search booking information etc.
bookingId: It indicates the booking Id of booking.
bookingDate: It indicates the date for which the users make booking.
bookingDescription It contains the detail about booking.
bookingTitle It indicates the booking title of booking.
addBooking () An operation that is used for add booking information.

Pseudo code:
1.Start
2. add Booking(int Id, , int password)
{
6. Admin must be login for edit booking Information.
7. add Booking
8. Successfully add booking information.

else
9.Error message
}
10.End .
deleteBooking () An operation that is used for delete booking information.
Pseudo code:
1.Start
2. delete Booking(int Id, , int password)
{
6. Admin must be login for deleting booking Information.
7.delete Booking
8.Successfully delete Information
else
9.Error message
}
10.End .
edit Booking() An operation that is used for edit Booking by customer.
Pseudo code:
1.Start
2. edit Booking(int Id, int password)
{
6. Admin must be login for edit booking Information.
7. Edit booking Information.
8. Successfully edit booking Information.
else
9.Error message
}

10.End
An operation that is used for search booking information.
search_Booking () Pseudo code:
1.Start
2. search Booking(int Id, , int password)
{
6. Admin must be login for search booking Information.
7. Search booking Information.
8. Successfully Search booking Information.
else
9.Error message
}
10.End .
5.7 Flight
Class Name Flight
Description It contain all the information about Flight such as add Flight, delete
Flight, edit Flight, search Flight etc.
number: It indicates the flight number that indicates the flight..
departure: Define the departure time of flight.
arrival: Defines the arrival time of the flight.

addFlight () An operation that is used for add Flight information.

Pseudo code:
1.Start
2. add Flight (int Id, , int password)
{
6. Admin must be login for add Flight Information.
7. add Flight
8. Successfully add Flight information.
else
9.Error message
}
10.End .
deleteFlight () An operation that is used for delete Flight information.
Pseudo code:
1.Start
2. delete Flight (int Id, , int password)
{
6. Admin must be login for deleting Flight Information.
7.delete Flight
8.Successfully delete Flight Information
else
9.Error message
}
10.End .

An operation that is used for edit Flight information by customer.

edit_Flight() Pseudo code:
1.Start
2. edit Flight (int Id, int password)
{
6. Admin must be login for edit Flight Information.
7. Edit Flight Information.
8. Successfully edit Flight Information.
else
9.Error message
}
10.End .
An operation that is used for search Flight information.
search_Flight () Pseudo code:
1.Start
2. search Flight (int Id, , int password)
{
6. Admin must be login for search Flight Information.
7. Search Flight Information.
8. Successfully Search Flight Information.
else
9.Error message
}
10.End .

5.8 Ticket
Class Name Ticket
Description It contain all the information about Ticket such as add Ticket, delete
Ticket, edit Ticket, search Ticket etc.
ticketNo: Define the ticket number that provides to the customer.
source It indicates the source location.
destination It indicates the destination location.
passengerNumber Define the passenger number who got the ticket.
addTicket () An operation that is used for add Ticket information.

Pseudo code:
1.Start
2. add Ticket (int Id, , int password)
{
6. Admin must be login for add Ticket Information.
7. add Ticket
8. Successfully add Ticket information.
else
9.Error message
}
10.End .

deleteTicket () An operation that is used for delete Ticket information.

Pseudo code:
1.Start
2. delete Ticket (int Id, , int password){
6. Admin must be login for deleting Ticket Information.
7.delete Ticket
8.Successfully delete Ticket Information
else
9.Error message}
10.End.
editTicket() An operation that is used for edit Ticket information by customer.
Pseudo code:
1.Start
2. edit Ticket (int Id, int password)
{
6. Admin must be login for edit Ticket Information.
7. Edit Ticket Information.
8. Successfully edit Ticket Information.
else
9.Error message
}
10.End
searchTicket() An operation that is used for search Ticket information.
Pseudo code:
1.Start
2. search Ticket (int Id, , int password)
{


6. Admin must be login for search Ticket Information.
7. Search Ticket Information.
8. Successfully Search Ticket Information.
else
9.Error message
}
10.End.
5.9 Passenger
Class Name Passenger
Description Passenger is a user of OARS who is responsible for make, delete,

update Reservation etc.
name: It indicates the name of passenger.
emaild: Email id of passenger that will be used for login to system.
password: Password of the passenger to access the system.
phoneNo .: Phone no. of the passenger to contact with passenger.


Pseudo code:
1.Start
2. make Reservation(int Id, , int password)
{
6. make Reservation
7.Successfully make Reservation
else
8.Error message
}
9.End .
deleteReservation () An operation that is used for delete reservation by Passenger.
Pseudo code:
1.Start
2. delete reservation (int Id, , int password)
{
6.delete reservation
7.Successfully delete reservation
else
8.Error message
}
9.End .

An operation that is used for update reservation by Passenger.

update_Reservation Pseudo code:
() 1.Start
2. update reservation (int Id, int password)
{
6. Passenger must be login for update reservation.
7.create Account
8. Successfully update reservation.
else
9.Error message
}
10.End .
An operation that is used for cancel reservation by Passenger.
cancel_Reservation Pseudo code:
() 1.Start
2. cancel reservation (int Id, int password)
{
6. Passenger must be login for cancel reservation.
7.create Account
else
9.Error message
}
10.End

5.10 Airline
Class Name Airline
Description It contains the information about airline system.
airlineName It indicates the airline name of airline system.
date It indicates the date for which the user booked seat.
flightNumber It indicates the flight number of airline.
addDetail () An operation that is used for add detail.

Pseudo code:
1.Start
2. add Detail (int Id, , int password)
{
6. Admin must be login for add detail.
7. Add airline detail.
8. Successfully add airline detail.
else
9.Error message
}
10.End .

updateDetail() An operation that is used for update detail.

Pseudo code:
1.Start
2. add Detail (int Id, , int password)
{
6. Admin must be login for update detail.
7. Update airline detail.
8. Successfully update airline detail.
else
9.Error message
}
10.End .
deleteDetail() An operation that is used for delete detail of airline.
Pseudo code:
1.Start
2. add Delete (int Id, , int password)
{
6. Admin must be login for delete detail.
7. Delete airline detail.
8. Successfully delete airline detail.
else
9.Error message
}
10. End.

5.11 Reservation
Class Name Reservation
Description It contain all the information about Reservation such as add

Reservation, delete Reservation, edit Reservation, search
Reservation etc.
reservationID It indicates the reservation id of reservation.
reservationDate It defines the reservation date of flight booked by the customer.
reservationTicket It indicates the reservation ticket information.
reservationDescription Define the passenger number who got the ticket.
reservationTitle Defines the reservation title.
addReservation() An operation that is used for add Reservation information.

Pseudo code:
1.Start
2. add Reservation (int Id, , int password)
{
6. Admin must be login for add Reservation Information.
7. add Reservation
8. Successfully add Reservation information.
else
9.Error message
}

deleteReservation() An operation that is used for delete Reservation information.

Pseudo code:
1.Start
2. delete Reservation (int Id, , int password)
{
6. Admin must be login for deleting Reservation Information.
7.delete Reservation
8.Successfully delete Reservation Information
else
9.Error message
10.End
.
}
searchReservation() An operation that is used for search Reservation information.

Pseudo code:
1.Start
2. search Reservation (int Id, , int password)
{
7. Search Reservation Information.
8. Successfully Search Reservation Information.
else
9.Error message
}

10.End .
save_Reservation() An operation that is used for save Reservation information.

Pseudo code:
1.Start
2. save Reservation (int Id, , int password)
{
7. Save Reservation Information.
8. Successfully Save Reservation Information.
else
9.Error message
}
10. End.

6. HUMAN INTERFACE
NTERFACE DESIGN
6.1 Overview of User Interface
Describe the functionality of the system from the user’s perspective.
6.2 Screen Images
6.2.1 Home page

This screen displays the home page of airline reservation system.

6.2.2 Registration Form

This screen used to capture information necessary for registration in Online Airline
Reservation System.
Registration
First Name First Name
Second Name Second Name
Email ID @gmail.com
Register Cancel
Register Cancel
Contact No. 0000-0000000
6.2.2 Login
Gender Gender
Password **********
Confirm Password **********
I accept all terms and condition
Register Cancel

6.2.3 Login
It will be first screen when user opens DBMS to login to DBMS application in Online Airline
Reservation System.
Login
For User
Username Username
Password **************
Not a member yet? Register
For Administrator
Username Username
Password ***************
Not a member yet? Register
Login Cancel

6.2.3 Add Customer Detail
Add customer detail screen display the customer detail that needed for making reservation.
Add Customer Details
Customer ID Customer ID
Customer Name Customer Name
Father Name Father Name
Choose Image
Gender Gender
D.O.B MM/DD/YY
Save
Save
Address Colony/street/House No

6.2.4 Flight Detail

It will display the flight detail when the user want to make reservation in Online Airline
Reservation System.
Search
Flight Details
Flight No. Flight No
Flight Name Flight Name
Source ----Select Location-----
Destination ----Select Location----
Departure Departure Date
Arrival Time Arrival Date
Flight Class ----Select Class----
Flight Charges Flight Charges
Seats ----Select Seats------
Add Flight Update Delete

6.2.5 Online Reservation

It will be the screen of Online reservation that display the information how to make online
reservation.
Online Reservation
Journey Type One-Way Multi-Way
Departure City ---Select Location---
Arrival city ---Select Location---
Departure Date YY/MM/DD
No. of Travellers
Total Adults
Adults (18 yrs)
Infants (Below 2 yrs) Total Infants
Children (02-17yrs) Total Children
-------Select Class-------
Cabin
Search Flight Cancel
Search Flight Cancel

6.2.6 Reservation Form

It will be screen when user opens DBMS to Makes reservation in Online Airline Reservation
System.
Reservation Form
First Name First Name
Last Name Last Name
Date of Birth YY/MM/DD
Gender Male Female
Seat
6.2.6 Reservation Form Request Select Seat

Emergency Contact Detail
Contact No. Contact Us

EmailId
Email ID
6.2.7 Online Transaction
Processed to payment Back

6.2.7 Online Transaction

It is used to view online transaction System of reservation
Online Transaction
Payment Mode -- Select Payment Mode---
Card Member Card Member
CVV CVV
Card Boulder’s Name Name
Card Boulder’s Contact Contact No.
Expire Date DD/MM/YY
I accept all terms and conditions
Make payment Cancel

6.2.8 Flight Status

It is used to view status of Flight and display the date and time of flight.
Flight Status
Flight Number Flight Number
DD/MM/YY
Departure Date
Notify me using voice call Yes No
Click Status Cancel

6.2.9 Web Check In

It is used to view web check in process.
Web Check In
Ticket Number Ticket Number
Print Bonding Pass Skip
6.2.10 Cancel Reservation

It is used to view the process of cancel Reservation.
Cancel Reservation
Ticket Number Ticket Number
Cancel Ticket Back

6.2.11 Contact Us
It display all the contact detail about Airline Reservation System
Contact Us
Email ID @gmail.com
6.2.12 Feedback
Phone No 0000
0000-0000000
Password *************
Can also contact with:

6.2.13 Feedback
The user gives feedback through this Screen image.
Feedback
Email ID @gmail.com
Password **************
Do you want to give Feedback? Yes No
OK Cancel

7. REQUIREMENTS MATRIX
Component Registra Login Flight Confir Search Reservation Databas Payment

Requirement tion m e
from SRS
(Use case)
UC 3.2.1.1

UC 3.2.1.2

UC 3.2.1.3

UC 3.2.1.4

UC 3.2.1.5

UC 3.2.1.6

UC 3.2.1.7

UC 3.2.1.8


Component Login Flight Feedback Schedule Customer Database Logout

Requirement
from SRS
(Use case)
UC 3.2.1.9

UC 3.2.1.10

UC 3.2.1.11

UC 3.2.1.12

UC 3.2.1.13

UC 3.2.1.14

UC 3.2.1.15

UC 3.2.1.16

UC 3.2.1.17


173501-Rabia Muneer-Online Reservation System - PIA

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

173501-Rabia Muneer-Online Reservation System - PIA

Uploaded by

Copyright:

Available Formats

SEPTEMBER 22, 2019

Online Airline Reservation

RABIA MUNEER 173501

9/22/2019 Version 1.0 Rabia Muneer

Signature Printed Name Title Date

Sir Usman Ghani Supervisor, CSIT 21306 9/22/2019

1.2 Scope ......................................................................................................................................... 1

1.3 Overview ................................................................................................................................... 1

1.4 Reference Material .................................................................................................................... 1

1.5 Definitions and Acronyms ........................................................................................................ 2

2.1 Assumption ............................................................................................................................... 2

2.2 Technology to be used .............................................................................................................. 2

2.3 Design language ........................................................................................................................ 3

2.4 Application overview ................................................................................................................ 3

2.5 General constraints.................................................................................................................... 3

2.6 System Environment ................................................................................................................. 3

3.1 Web Architecture ....................................................................................................................... 4

3.2.1 Architectural Design .............................................................................................................. 4

3.1.1.2 Block Diagram ..................................................................................................................... 5

3.2 Decomposition Description ...................................................................................................... 5

3.2.1 Use Cases ............................................................................................................................... 6

3.2.1.1 Registration .................................................................................................................................................... 6

3.2.1.2 Login .................................................................................................................................... 7

3.2.1.4 Make Reservation ................................................................................................................ 9

3.2.1.5Modify Reservation ............................................................................................................ 10

3.2.1.6 Cancel Reservation ............................................................................................................ 11

3.2.1.7 Payment ............................................................................................................................. 12

3.2.1.8 Add Flight Information ...................................................................................................... 13

3.2.1.9 Modify Flight Information ................................................................................................. 14

3.2.1.10Delete Flight Information ................................................................................................. 15

3.2.1.11 Add Customer Information .............................................................................................. 16

3.2.1.12Update Customer Information .......................................................................................... 17

3.2.1.13Delete Customer Information ........................................................................................... 18

3.2.1.14 Contact Us........................................................................................................................ 19

3.2.1.16 view Schedule .................................................................................................................. 21

3.2.2 Sequence Diagrams.............................................................................................................. 23

3.2.2.2 Make Reservation .............................................................................................................. 24

3.2.2.3 Modify Reservation ........................................................................................................... 25

3.2.2.4 Cancel Reservation ............................................................................................................ 26

3.2.2.5 Add Custromer Information ............................................................................................... 27

3.2.2.6 Modify Custromer Information.......................................................................................... 28

3.2.2.7 Delete Custromer Information ........................................................................................... 29

3.2.3.1 Login .................................................................................................................................. 30

3.2.3.2 Make Reservation .............................................................................................................. 31

3.2.3.3 Update Reservation ............................................................................................................ 31

3.2.3.4Cancel Reseevation ............................................................................................................. 32

3.2.4 Activity Diagram ................................................................................................................. 33

3.2.4.1 Login .................................................................................................................................. 33

3.2.4.2 Make Reservation .............................................................................................................. 34

3.2.4.3Cancel Reseevation ............................................................................................................. 35

3.2.4.3 Modify Reservation ........................................................................................................... 36

3.2.4.3 Flight .................................................................................................................................. 37

3.2.4.4 Payment ............................................................................................................................. 38

3.2.5 Class Diagram ....................................................................................................................... 39

3.2.5.5Ticket Management ............................................................................................................ 43

3.2.5.8Entire System ...................................................................................................................... 46

3.3 Design Rationale ..................................................................................................................... 47

4. DATA DESIGN ......................................................................................................................... 47

4.1.1 Data Object .......................................................................................................................... 47

4.1.1. Administrator ....................................................................................................................... 47

4.1.2. Login .................................................................................................................................... 48

4.1.3. Customer .............................................................................................................................. 48

4.1.4. Payment ............................................................................................................................... 48