Airline Reservation System

Session : BSIT Fall 2015-2019

Project Advisor: Maam Aqsa Mehmood

Submitted By

Aqsa Muzammil 01

Iqra Fatima 25

33
Saira Iftikhar

Department of Computer Science & Information Technology

GSCWU Bahawalpur

© Department of Computer Science & Information Science.

1
 STATEMENT OF SUBMISSION

This is certify that Aqsa Muzammil Roll No. 01 ,Iqra Fatima Roll No. 25 and Saira
Iftikhar Roll No.33 successfully completed the final project named as: Airline
Reservation Sysrtem, at the Department of Computer Science & Information
Technology, GSCWU Bahawalpur, to fulfill the requirement of the degree of BS in
Information Technology.

______________________ _____________________
Project Supervisor Project Coordination Office
Ma’am Aqsa Mehmood

_____________________________ ________________________
External Examiner Head of Department

Acknowledgement

© Department of Computer Science & Information Science.

2
We truly acknowledge the cooperation and help make by Ma’am Aqsa Mehmood,
Department of Computer Science & Information Technology, GSCWU. She has been a
constant source of guidance throughout the course of this project. We are thankful to our
friends and families whose silent support led us to complete our project.

1- Saira Iftikhar
2- Iqra Fatima

Date: June,25,2019

© Department of Computer Science & Information Science.

3
Contents
CHAPTER 1: FINAL PROJECT PROPOSAL..............................................................6
1. INTRODUCTION:........................................................................................................6
1.2. PROJECT TITLE:.........................................................................................................6
1.3. PROJECT OVERVIEW STATEMENT:.............................................................................6
1.4. PROJECT GOALS & OBJECTIVES:..............................................................................8
1.5. HIGH-LEVEL SYSTEM COMPONENTS:.........................................................................8
1.6. LIST OF OPTIONAL FUNCTIONAL UNITS:....................................................................9
USABILITY: THE SYSTEM SHOULD BE DESIGN IN FRIENDLY MANNER SO IT WILL EASY
FOR USER TO RESERVE THE TICKET................................................................................10
AVAILABILITY: THE WEBSITE SHOULD BE PROVIDE 24-HOUR SERVICES.......................10
PERFORMANCE: THE ADMIN SHOULD USE NEW FEATURE TO DESIGN THE WEBSITE FOR
BETTER PERFORMANCE...................................................................................................10
1.7 APPLICATION ARCHITECTURE:...............................................................................10
1.8. GANTT CHART:.......................................................................................................11
OUR SYSTEM WILL HOPE FULLY BE COMPLETED IN THE PROPOSED GANTT CHART
SHOWN AS FOLLOW:.......................................................................................................11
1.9. HARDWARE AND SOFTWARE SPECIFICATION:.......................................................11
1.10. TOOLS AND TECHNOLOGIES USED WITH REASONING:..........................................11
CHAPTER 2: FIRST DELIVERABLE.........................................................................12
2.1. INTRODUCTION........................................................................................................12
2.2. PROJECT/PRODUCT FEASIBILITY REPORT...............................................................12
2.2.1. Technical Feasibility.......................................................................................12
2.2.2. Operational Feasibility...................................................................................13
2.2.3. Economic Feasibility.......................................................................................13
2.2.4. Schedule Feasibility........................................................................................13
2.2.5. Specification Feasibility..................................................................................14
2.2.6. Information Feasibility....................................................................................14
2.2.7. Motivational Feasibility..................................................................................14
2.2.8. Legal & Ethical Feasibility.............................................................................14
2.3. PROJECT/PRODUCT SCOPE......................................................................................14
2.4. TOOLS AND TECHNOLOGY WITH REASONING:........................................................14
2.5. RISK LIST:...............................................................................................................15
2.6. PRODUCT FEATURES/ PRODUCT DECOMPOSITION.................................................15
CHAPTER 3: SECOND DELIVERABLE FOR OBJECT ORIENTED
APPROACH.....................................................................................................................16
3.1 INTRODUCTION:........................................................................................................16
3.1.1 Systems Specifications......................................................................................16
3.1.2. Identifying External Entities............................................................................19
3.1.3. Context Level Data Flow Diagram:................................................................19
3.1.4. Capture "shall" Statements:............................................................................20
© Department of Computer Science & Information Science.
4
 3.1.5. Allocate Requirements:...................................................................................20
3.1.6. Prioritize Requirements:.................................................................................21
3.2 Usecase Diagram:...............................................................................................24
CHAPTER 4: THIRD DELIVERABLE FOR OBJECT ORIENTED APPROACH
...........................................................................................................................................30
4.1. INTRODUCTION:.......................................................................................................30
4.3. SYSTEM SEQUENCE DIAGRAM................................................................................30
4.5. COLLABORATION DIAGRAM....................................................................................37
4.5.1. Contents of Collaboration Diagrams..............................................................38
CHAPTER 5: 2ND & 3RD DELIVERABLE FOR STRUCTURED APPROACH. .40
5.1. INTRODUCTION:.......................................................................................................40
5.2. DATA FLOW DIAGRAM (FUNCTIONAL MODEL).......................................................40
5.3.Design Class Diagram……………………………………………………………..40
Chapter 6: 4th Deliverable (User Interface Design)...........................................................43

© Department of Computer Science & Information Science.

5
Chapter 1: Final Project Proposal

1. Introduction:
Airline reservation systems is the passenger service systems, which provides the facility
to direct contact with the passenger. User access an airline inventory through and
availability display. It contains all offered flies particular city with their available seats in
different booking classes.
The need of the system we realized because of some issues .we had to go there where we
want to reserve our tickets, it is time consuming, wastage of fuel, and travel agent had the
difficult task of looking into separate books for reservation

1.2. Project Title:

“AIRLINE RESERVATION SYSTEM”

1.3. Project Overview statement:

Minimize repetitive work done by the system administrator and reservation clerks.
Reduce effort and frustration for travelers in scheduling a trip, especially by reducing the
search effort for the flight they need to take. Reduce redundancy in the information
required from the customers in order for them to buy tickets, create user accounts etc.
Check the validity of input data and give a feedback to the user in case of errors or
inconsistency. Make it easy for travelers to check the ticket status or make changes to
their trip. Check the validity of input data and give a feedback to the user in case of errors
or inconsistency. The system shall also give the user an option to cancel a confirmed
ticket or a blocked ticket.

© Department of Computer Science & Information Science.

6
Project Overview Statement Template

Project Title:
“AIRLINE RESERVATION SYSTEM”

Project Manager: Mam Aqsa Mehmood

Project Members:

Name Registration # Email Address Signature

Aqsa Muzammil 2015-WU-BS-162 aqsa4286r@gmail.com
Iqra Fatima 2015-WU-BS-184 mehakfatima538@gmail.com
Saira Iftikhar 2015-WU-BS-192 hadiya.chaudhary130@gmail.co
m

Project Goal:
Airline reservation system will contain the detail about flight schedule and its fare , passenger reservation
and tickets records.

Objectives:
Sr.#
1 The main objective is to make the airline information system online based

2 Data will be stored in organized form

3 To reduce the number of the registers and documents

4 Easy to maintain the records

5 Searching of any record will be very easy and fast

6
Project Success criteria:

Assumptions, Risks and Obstacles:

Organization Address (if any):

Type of project: Research Development

Target End users:
Airline Company
Development Technology: Object Oriented Structured
Platform: Web based Distributed
Desktop based Setup Configurations
Other_____________________

© Department of Computer Science & Information Science.

7
Approved By:
Date:

1.4. Project Goals & Objectives:

Goals:
Airline Reservation system is to help the customers in reserving Air tickets through
online system. Airline reservation system will contain the detail about flight schedule and
its fare tariffs, passenger reservation and tickets records. An airlines inventory contains
all flight with their available seats.
Objectives:
The objective of the project are as follows:
 The main objective is to make the airline information system online based
 Data will be stored in organized form.
 To automate the maintenance of records
 To automate the searching of any record.
 To enable the passengers to make quick reservation in an automated way.
 Maintain customer information in case of emergency, e.g. flight cancellation due
to inclement weather.
 User shall be able to update his profile
 User can access the arrival and departure time of different flights according to the
destination points.
 User can book the ticket and after booking they will get Tentative receipt of
booking and after payment can take print of ticket
 Administrator can Modify and update the records about flight and reservation

1.5. High-level system components:

Main functional units of AIRLINE RESERVATION SYSTEM
 Admin module
 User module
 Flight detail
 Book ticket
Administrator module:
Admin have provision to view all schedule about flight and reservation. First admin
enter their name and id then only they can access and have complete control related to
flights, confirmed tickets, or unconfirmed tickets etc.

User module:
Register himself with the system by providing personal information or log into the
system as a guest.

© Department of Computer Science & Information Science.

8
Flight Details:
The module is used to view the flight details and information seats in the flight.

Book Tickets:
This module is used to book the ticket after checking the availability.

1.6. List of optional functional units:

1.6.1 Functional Requirements:
The requirement for this system are:

Home page:
In the HOME page we have included the navigation material of Airline Reservation
System.
Search flight:Search option is given to user by using textbox to search the related flight.

Log In/Admin: This page gives you access to enter in the system as Admin or a user.
For Booking of seats user need to sign up in the system.

Contact: In contact section we have provide contact detail of the Airline Company.

Checking Availability: user can check either flight is available or not.

Making Reservation: After checking availability User can Reserve the ticket.

Update Profile: The user to update his profile at any time.

View Ticket Status: A user to view all information about his trip.

1.6.2 Non Functional Requirements:

© Department of Computer Science & Information Science.

9
 Usability: The system should be design in friendly manner so it will easy for user to
reserve the ticket.

Availability: The website should be provide 24-hour services.

Performance: The admin should use new feature to design the website for better
performance

1.7 Application Architecture:

Our system may have 3 tier architecture linked together over the internet.it is a
distributed system network shown below:

© Department of Computer Science & Information Science.

10
1.8. Gantt Chart:

Our system will hope fully be completed in the proposed Gantt chart shown
as follow:

1.9. Hardware and Software Specification:

Hardware specifications:
 Processor: 1.7
 RAM 2GB
 Hard disk capacity: 320GB
Software specifications:
 .Net Framework
 Visual studio

1.10. Tools and technologies used with reasoning:

The tools or software used to develop the website are:

 Dreamweaver
 SQL server
 Visual studio
The languages that are used in making the website are
Back end language
 Asp.net core(Entity Framework)
 SQL(database)
Front end language
 HTML
 CSS
 JAVA SCRIPT
 BOOTSTRAP

© Department of Computer Science & Information Science.

11
Chapter 2: First Deliverable

2.1. Introduction
First deliverable is all about planning and scheduling of project. This deliverable must
contain following artifacts:

a. Project Feasibility
b. Project Scope
c. Project Costing
d. Task Dependency Table
e. Critical Path Method Analysis (CPM Analysis)
f. Gantt Chart
g. Introduction to team members
h. Tasks and member assignment table
i. Tools and Technologies
j. Vision Document
k. Risk List
l. Product Features

2.2. Project/Product Feasibility Report

The project should b developed such that the necessary functions and performance is
achieved within the constraints. The project is developed within latest technology.
Through the technology may become obsolete after some period of time the system may
still be used. So, there are minimal constraints involved with this project. This system has
been developed by using Html, CSS, JavaScript and .NET core the project is technically
feasible for development. We have study the existing computer systems (Hardware &
Software) of the concerned department and have determined whether these technical
resources are sufficient for the proposed system or not. We have found out thus, that the
project is technically much feasible. In short,we are using all the tools and technologies
that are available in market. The hardware and software requirements are:
Operating system: windows, Linux.

2.2.1. Technical Feasibility

The technical issues raised during the feasibility stages of investigation include the
following:
 Does the necessary technology exist to do what is suggested?

© Department of Computer Science & Information Science.

12
  Does the proposed equipment have the technical capacity to hold he data
required to use the new system?
 Will the proposed system provide appropriate response to inquiries, regardless of
the number or location of users?
 Can the system be upgraded if developed?
 Are there technical guarantees of accuracy, reliability, ease of access and data
security?
The current system developed is technically feasible. It is a web based user interface.
It provides an easy access to user. It provides the technical guarantee of accuracy
reliability and security. The software and hardware requirements for the development of
this project are not and already available in the market as free as open source.
2.2.2. Operational Feasibility
Operational feasibility aspects of the project are to be taken as an important part of the
project implementation. Some of the important issues raised are to test the operational
feasibility of the project include the following:
 Is there sufficient support for the management from the users?
 Will the system be used and work properly if it is being developed and
implemented?
 Will there be any resistance from the user that will undermine the possible
application benefits?
The managements issue and user requirements have been taken into consideration So,
there is no question of resistance from the user that can undermine the possible
application benefits
2.2.3. Economic Feasibility
The system can be developed technically and will be used if installed must still be a
good investment for the organization. In the economic feasibility, the development cost in
creating the system is evaluated against the ultimate benefits derived from the new
system. Financial benefits must equal or exceed the cost. The system is developed as a
part of project work, there is no manual cost to spend for the proposed system.
Additionally all the resources are available, it is an indication that the proposed system is
economically feasible.
2.2.4. Schedule Feasibility
The developer is aware about the importance of schedule and loyalty to deadlines,
beacause delay in a project leads to failure. Therefore, in order to complete it with time in
hand, a timeline in the form of Gantt chart has to include

© Department of Computer Science & Information Science.

13
2.2.5. Specification Feasibility
Operational feasibility is the measure of how well a proposed system solves the problem.
The proposed system will fulfill the demand of the customer and management
2.2.6. Information Feasibility
The feasibility of information must be assessed regarding its completion, reliability, and
meaningfulness.
2.2.7. Motivational Feasibility
It will provide the user friendly interface so user can easily use the system which may
develop the interest of the user for the system.
2.2.8. Legal & Ethical Feasibility
No patent or copyright violation and no privacy policy violation. Our project has no
activity that can be unethical. We are not using any pirated tool in our project.

2.3. Project/Product Scope

The scope of our proposed system is to book the flights online and receive tickets 3 hours
before the flight departure.

2.4. Tools and Technology with reasoning:

Hardware:
A minimum computer system that will help you access all the tools in the
system is a Pentium 166 or better.
8GB RAM or better.
Software:
o Visual studio
o Dreamweaver
o Asp.Net core
o Entity Framework

© Department of Computer Science & Information Science.

14
2.5. Risk List:
The possibility of suffering harm or loss in terms of danger is called risk. Regarding the
importance of risks a list is to be maintained. Risk list is a sorted list of known, open risks
to the project, sorted in decreasing order of importance, associated with specific
mitigation or contingency actions.
Purpose
The Risk List is designed to capture the perceived risks to the success of the project. It
identifies, in decreasing order of priority, the events that could lead to a significant
negative outcome. It serves as a focal point for project activities and is the basis around
which iterations are organized
The Risk List is maintained throughout the project. It is created early in the Inception
phase, and is continually updated as new risks are uncovered and existing risks are
mitigated or retired. At a minimum, it is revisited at the end of each iteration, as the
iteration is assessed.

2.6. Product Features/ Product Decomposition

 ARS main page
 Log in/Admin
 Flights detail
 Contact us
 Manage tickets
 My profile
 Admin panel
 Add flight
 Confirmed Ticket
 View Users

© Department of Computer Science & Information Science.

15
Chapter 3: Second Deliverable For Object Oriented Approach

3.1 Introduction:
Requirements engineering process provides the appropriate mechanism for understanding
what the customer wants, analyzing need, assessing feasibility, negotiating a reasonable
solution, specifying the solution unambiguously, validating the specification and
managing the requirements as they are transformed into an operational system. The task
of capturing, structuring, and accurately representing the user's requirements so that they
can be correctly embodied in systems which meet those requirements (i.e. are of good
quality).

 Requirements elicitation
 Requirements analysis and negotiation
 Requirements specification
 System modeling
 Requirements validation
 Requirements management

Here, requirements specification is to be discussed. Requirements specification would

lead to the following four steps:
 Identify external interfaces
 Development of context diagram
 Capture “shall statements
 Allocate requirement
 Prioritize requirements
 Development of requirements traceability matrix
3.1.1 Systems Specifications
The system specification is the behavior and feature of the system which is being
developed.
Introduction
Airline reservation systems are the passenger service systems, which provide the facility
to direct contact with the passenger. User accesses an airline inventory through and
availability display. It contains all offered flies particular city with their available seats in
different booking classes.

© Department of Computer Science & Information Science.

16
Existing System
In few countries if a person want to book a flight ticket he use the folloe one of these
thing:
 Manually goes to the airport and book his ticket.
 Download the ticket Form as paper document, filling it manually and submitting
it at Airport.
 Cannot Upload and Download the latest Update.
 Cancelation of the ticket is not possible in some emergency.
 It provides the less security.

Organizational Chart

© Department of Computer Science & Information Science.

17
Scope of the System
The Airline reservation System is divided in to two phases.
 
Phase I
Phase I includes following business areas:
 Customer Account Maintainance
 Inventory Management
 Available display
 Booking for the ticket

Phase II
Phase II involves complete automation of the reservation of the ticket. Phase II includes
following business areas:
 Add and view Flights
 Add and view Fares
 View and Confirm Tickets
 View and manage Users
 Account setting

Summary of Requirements: (Initial Requirements)

The purposed system must fulfill following requirements as follow:
Customer Account Maintenance:
The proposed system facilitates the administrator to login to login form and makes the
user to book the reservation in Airline either using Domestic or International Flight.
When user clicks the Domestic Flight Domestic Flight table is viewed. If user clicks
International Flight, International Flight table can be viewed. If admin accept the
registration request, login information (Password, Id & role) should be assigned and
mailed to the corresponding user. Administrator has to enter username and password, if
username and password are not matched with the existing username, password it
displays” Invalid username and password” otherwise Domestic and International Flight
booking is viewed.
Inventory Management
Inventory control steers the how many seats are available indifferent booking classes.
It also contains the fare of the different flights. The Inventory Administrator updates the
information of all flight. He can also update the detail about flight and fare and their
schedule.

© Department of Computer Science & Information Science.

18
3.1.2. Identifying External Entities
The Identification of External Entities is done in two phases.

a. Over Specify Entities from Abstract:

On the basis of the Abstract, one might identify the following entities from the
Airline Reservation System:
 Customer Account
 Reserve ticket
 Inventory management
 Credit card
 Check
 Payment
 Invoice
 Account

b. Perform Refinement:
The following entities are related to our proposed system:
 Customer Account
 Reserve ticket
 Inventory Management
 Invoice
 Account

3.1.3. Context Level Data Flow Diagram:

© Department of Computer Science & Information Science.

19
 Zero level Diagram

3.1.4. Capture "shall" Statements:

Para Initial Requirements

#
1.0 A customer “shall” register himself to the system
1.0 A customer “shall” check the require flight seats are either available or not
1.0 A customer “shall” reserve the ticket
1.0 A customer “shall” login to the system and can change his password
1.0 A customer “shall” view his flight detail
1.0 Customer “shall” make payment by hand.
1.0 System “shall” update the customer’s Request
1.0 System “shall” search any customer details
1.0 System “shall” process different types of updating e.g. updating of his personal
info/flight scheduling
1.0 The System “shall” generate an action event for a corresponding administrator when a
request is placed for updating of Flight schedule or customer details etc.
2.0  System “will” generate confirmation receipt and confirm the ticket
2.0 Administrator “shall” accept, reject and temporarily waive the requests on the basis of
credentials provided.
2.0 Corresponding administrator “shall ” view his Action List containing different actions,
and correspondingly process these pending actions
2.0 Administrator “shall” Add Flight Schedule

3.1.5. Allocate Requirements:

Allocate the requirements in the use cases.

Para # Initial Requirements Use Case Name

1.0 A customer “shall” register himself to the UC_Register
sytem  
1.0 A customer “shall” view his details for UC_Register
verification purposes  
1.0 A customer “shall” login to the system and  UC_Login
can change his password
1.0 A Customer “shall” reserve the   UC_Reserve Flight

© Department of Computer Science & Information Science.

20
 ticket/cancellation
1.0 Customer “shall” view the status of their UC_Reserve Flight
reservation

2.0 System “shall” process different types of UC_Add Flight

updating e.g. updating of his personal
info/flight scheduling
2.0 The System “shall” generate an action event UC_AddFlight_Create_Action,
for a corresponding administrator when a
request is placed for updating of Flight
schedule or customer details etc.
2.0  System “will” generate confirmation receipt  UC_Reserve Flight
and conform the ticket
2.0 Administrator “shall” accept, reject and UC_Login
temporarily waive the requests on the basis
of credentials provided.
2.0 Administrator “shall” Add Flight Schedule UC_ AddFlight
3.0

3.1.6. Prioritize Requirements:

Par Rank Initial Use Case ID Use Case Name

a# Requirements
1.0 Highest A customer UC_04 UC_Reserve Flights
“shall” reserve
the ticket
1.0 Highest A customer UC_01 UC_Register
“shall” register
himself to the
system
2.0 Highest System “will” UC_4 UC_Reserve Flight
generate,
confirmation
receipt and
finally will
reserve ticket
2.0 Mediu The System UC_5 UC_Update_request

© Department of Computer Science & Information Science.

21
 m “shall” update
the customer
request
1.0 Mediu The System UC_6  UC_Create_Action
m “shall” generate
an action event
for a
corresponding
administrator
when a request
is placed for
updating of
Flight schedule
or customer
details etc
3.0 Mediu Administrstor UC_7 UC_Login
m “shall”accept,
reject and
temporarily
waive the
requests on the
basis of
credentials
provided.
1.0 Mediu The System UC_5 UC_Add Flights
m “shall” generate
an action event
for a
corresponding
administrator
when a request
is placed for
updating of
Flight schedule
or customer
details etc.
1.0 Mediu Customer UC_04 UC_Reserve Flights
m “shall” view the
status of their

© Department of Computer Science & Information Science.

22
 reservation
R Mediu A customer UC_01 UC_Register
m “shall” view his
details for
verification
purposes
2.0 Mediu User “shall” UC_04 UC_Reserve Flights
m view the status
of their
reservation
1.0 Lowest A customer UC_02 UC_Login,
“shall” login to  
the system and
can change his
password
3.0 Lowest Corresponding UC_05 UC_AddFlights
administrator
“shall ” view his
Action List
containing
different actions,
and
correspondingly
process these
pending actions

3.2 Usecase Diagram:

UC-01: Register:

© Department of Computer Science & Information Science.

23
 Use Case ID UC-01
Name Register
Actor User
Pre-condition System login page will be displayed.
Description The admin user can login to system automatically.
Primary Scenario Action Response
 User click on register  The system loads the
now. page where user will
 User enters its email fill in the details.
and password.  System verifies the
 User will click on given details.
submit button.  System will accept the
request.

Secondary Scenario User has given wrong email.

Exception User is already a member.
Post Condition User has registered successfully.

UC-02: Login:

© Department of Computer Science & Information Science.

24
 Use Case ID UC-02
Name Login
Actor User
Pre-condition System login page will be displayed.
Description User can login to the system successfully.
Primary Scenario Action Response
 User click on  System displays
the login the webpage.
button.  System accepts
 User enters its the given
login ID and details.
password.  System accepts
 User click on the request and
the submit gives access to
button. the system.

Secondary Scenario User enter wrong password.

Exception User doesn’t exist in the system.
Post Condition User logged into the system.

UC-03: Search For Flight

© Department of Computer Science & Information Science.

25
 Domestic

Search flight
International

User

Use Case ID UC-03

Name Search for Flight
Actor Customer
Pre-condition Customer will login successfully using his details.
Description Customer can check flight schedule.
Primary Scenario Action Response
 User click on  System displays
required flight. all flight
schedule
 The system will
display the
required flight
detail

Secondary Scenario Customer can check all flight schedules.

Exception Seats are not available
Post Condition Flights are displayed to the customer.

UC-04: Reserve Flight:

© Department of Computer Science & Information Science.

26
 Domestic

Reserve Flight
International

User

Use Case ID UC-03

Name Reserve for Flight
Actor Customer
Pre-condition Customer will login successfully using his details.
Description Customer can book flight.

Primary Scenario Action Response

 User click on the  System displays
booknow button. the webpage.
 User enters all  System accepts
the details. the given details.
 User click on the  System accepts
submit button. the request and
gives access to
the system.

Secondary Scenario User may enter the missed detail.

Exception User doesn’t exist in the system.
Post Condition User logged into the system.

UC-05: Add Flight:

© Department of Computer Science & Information Science.

27
 Add Flight

Update Flight sehdule

Cancel Flight

View All flight

Admin

Use Case ID UC-05

Name Add Flights
Actor Admin
Pre-condition Admin will login successfully using his details.
Description Admin can add flights.

Primary Scenario Action Response

 Admin click on  System displays
the Add Flight the webpage.
button.  System accepts
 Admin enters the given
all the flight details.
details.  System accepts
 Admin click on the request and
the submit gives access to
button. the system.

Secondary Scenario Admin enter the missed details.

Exception Admin doesn’t exist in the system.
Post Condition User logged into the system.

© Department of Computer Science & Information Science.

28
Chapter 4: Third Deliverable For Object Oriented Approach

4.1. Introduction:
Third deliverable is all about the software design. In the previous deliverable, analysis of
the system is completed. So we understand the current situation of the problem domain.
Now we are ready to strive for a solution for the problem domain by using object-
oriented approach. Following artifacts must be included in the 3rd deliverable.

1. System Sequence Diagram

2. Sequence Diagram
3. Collaboration Diagram
4. Design Class Diagram
5. Data Model

Now we discuss these artifacts one by one as follows:

4.3. System Sequence Diagram

The UML system sequence diagram (SSD) illustrates events sequentially input from our
external source to the system. This SSD will define the system events and operations.
System sequence diagrams are a timeline drawing of an expanded use case. Events are
related by time with the top events occurring first. System events are the important items.
These are events that cause a system response.

4.4. Sequence Diagram

© Department of Computer Science & Information Science.
29
This Sequence diagram depicts the sequence of actions that occur in our system. The
invocation of methods in each object, and the order in which the invocation occurs is
captured in these Sequence diagram. This makes the Sequence diagram a very useful tool
to easily represent the dynamic behavior of a system.

Registeration:

User GUI Controller Database

enter URL

click registration button

website will display

form appear

fill form

verify detail

if valid

Add user
Message
Registered Successfully

if invalid

Message
display error

Figure 1.Registeration

© Department of Computer Science & Information Science.

30
Login:

© Department of Computer Science & Information Science.

31
 User login UI Controller Database

enter login button

enter id&password verify id&password

message if valid

display login successfully

if invalid

invalid message

login invalid

user re-enter again

logout

Figure 2.Login

Search Flight:

© Department of Computer Science & Information Science.

32
 User Search UI Controller

enter search button

search about flight match detail

check flight

if available

display results

select flight

send flight id
match id

fare detail
display fare detail

if unavailable

display error message

Re-enter for search

Figure 3.Search Flight

Flight detail:

© Department of Computer Science & Information Science.

33
 Admin Flight detail Controller Database

enter flight detail

send new flight detail

match the de tail

opt
if detail matche d

store the flight detail

message

new flight is add

display to user

if detail is missing

message

some detail is missing

re_enter deta il

Ctrl + D Loop fragment Show Destruction

Finished with these tips?

Select the Tip Pa ne an d press
Delete
To dup licate a shape, sele ct it and pres s Use the Loop fragment shape for multiple Right-click a lifeline to show its de struction.
Ctr l+D. rep eated messag es.

Figure 4.Flight Detail

Flight id:
Admin Cencellation UI Controller Database

ente r flight id
send flight id
delete flight

message

cancellation done

display to user

Ctrl + D Loop fragment Show Destruction

Finis hed with these tips?

Se lect the Tip Pa ne and press
De lete
To dup lic ate a shape, sele ct it and pres s Use the L oop fragment shape for multiple Right-c lick a lifeline to show its destruction.
Ctr l+D. rep eated messag es.

Figure 5.Flight id

UML Activity diagram:

Registration:

© Department of Computer Science & Information Science.

34
Login:

Search flight:

© Department of Computer Science & Information Science.

35
Flight Detail:

Flight id:

© Department of Computer Science & Information Science.

36
4.5. Collaboration Diagram
This collaboration diagram describes a pattern of interaction among objects; it shows the
objects participating in the interaction by their links to each other and the messages that
they send to each other.

© Department of Computer Science & Information Science.

37
 Admin

Controller

User

4.5.1. Contents of Collaboration Diagrams

Admin:
 Login
 Perform operations
 Logout
 Shows admin penal
 Return result
 Redirect to start page
User:
 User login
 Book ticket
 Logout
 Shows user penal
 Gives ticket id
 Return to start page

Controller:

© Department of Computer Science & Information Science.

38
  Validate admin account
 Update database
 Validate user

© Department of Computer Science & Information Science.

39
Chapter 5: 2nd & 3rd Deliverable For structured Approach

5.1. Introduction:
Analysis & Design Model for object oriented approach:

1. Data Flow Diagram (Functional Model)

5.2. Data flow diagram (Functional Model)

DFD is all about to identify the major processes in your system and develop Data Flow
Diagram up to required level.
DFD Level 1:

User Flight s ehdule Ente r source and destination

Return flight sehedule Flight s ehedule

Ticket
Enter pa ssenger detail
Rese rvation Return total amount
Register Login

Passenger
Sta tus

User detail Enter ticke t id Ticket Details

Cancel Ticket Ente r ticke t id

Refund

Figure 6.Data flow Diagram (Level 1)

© Department of Computer Science & Information Science.

40
DFD LEVEL 2:

User Flight sehdule Enter source and destination

Return flight sehedule Flight sehedule

Ticket
Enter passenger detail
Reservation
Return total amount
Register Login

Passenger
Status

User detail Enter ticket id Ticket Details

Cancel Ticket Enter ticket id

Refund

Figure 7.DFD-Level2

The existing system contain the airline schedule, passenger reservation and
tickets record, reservation for individual passenger and groups of passengers.it
also check the capacity of the tickets whether a require ticket is available or not. If
a require ticket is available then issue a ticket and update the reservation
information

5.3 Design Class Diagram:

© Department of Computer Science & Information Science.

41
 tblFlights
flight_id
source
destination
departure_date
departure_time
arrival_date tblTickets
ticket_id
arrival_time
flight_id
flight_type
user_id
flight_status
adults
flight_name
child
available_seats
total_charges tblUsers
ticket_status user_id

travelling_class first_name
last_name
email
password
phone_no
tblFare cnic
fare_id
tblNotifications
user_type
id
flight_id status
message
adults
time
child
date
ticket_id
seen_status
user_id
tblMails
mail_id
name
subject
email
message
date_stamp
time_stamp

Chapter 6: 4th Deliverable (User Interface Design)

© Department of Computer Science & Information Science.

42
User Interface Design:

Figure 8.Login

© Department of Computer Science & Information Science.

43
 Figure 9.Register

Figure 10.Home

© Department of Computer Science & Information Science.

44
 Figure 11.Home(1)

Figure 12.All Flights

© Department of Computer Science & Information Science.

45
 Figure 13.All Tickets

Figure 14.Contact Us

© Department of Computer Science & Information Science.

46
 Figure 15.Reset Password

Figure 16.Profile

© Department of Computer Science & Information Science.

47
 Figure 17.Book Tickets

Figure 18.Payment Challan

Admin Interface Design

© Department of Computer Science & Information Science.

48
 Figure 19.Login

Figure 20.Dashboard

© Department of Computer Science & Information Science.

49
 Figure 21.Add Flight

Figure 22.View Flight

© Department of Computer Science & Information Science.

50
 Figure 23. Add Fare

Figure 24.View Fare

© Department of Computer Science & Information Science.

51
 Figure 25.View User

Figure 26.Change Password

© Department of Computer Science & Information Science.

52
 Figure 27.Tickets

Figure 28.Notification

© Department of Computer Science & Information Science.

53