Project Title

 AIRPORT FLIGHT SCHEDULE SYSTEM

Presented To

 Mam Sadaf Anwar

Group Members

 RAJA HAMZA TARIQ (143)

 BILAL ABBAS (142)
 MOHAMMAD SIRAJ (126)
CONTENTS

 Introduction
 Functional Requirements
 Non Functional Requirements
 Language and tools
 Use case diagram
Introduction

This is the flight schedule software for airport. This is for the accuracy
of work. Time efficiency is created. This software handle air traffic of
airport. Maintain record of flights, passengers and fuel etc.
Administrator easily handle all the records. Privacy is maintained in
AFSS, data is secured. Information of passengers not accessible to
anyone without administrator. Only next 24 hour status of flights are
accessible to website administrator.
Functional Requirements

 Store takeoff and landing flights data with date and time.

 Store data related to flights e.g. passengers traveled in a flight, flight registration
number etc.

 Store route of flights and destination.

 Automatically warning is issued when weather is not suitable.

 Automatic message is created if route and time is same for two flights.

 Fuel consumption for every flight is stored.

 Data stored separately for international and domestic flights and passengers.
Non Functional Requirements

 Privacy requirement

 Availability requirement

 Capacity requirement

 Backup and recovery requirement

 Performance requirement

 Security requirement

 Reliability requirement

 Maintainability
Language and Tools

 Java language is used for coding.

 Used tool net beans in java for fulfilling the requirements.

 SQL database system is used for storing all the data.

UML diagrams

 UML stands for Unified Modeling Language which is used in object oriented
software engineering. Although typically used in software engineering it is a rich
language that can be used to model an application structures and behaviour.
 There are basically two types of UML diagrams

1. Structural diagrams
2. Functional diagrams
Structural diagrams

Structural diagrams are those diagrams which basically show structure of a system or
software. It basically show the things in the system being modeled. Some structural
diagram of AFSS are:-
1. Class Diagram
2. Component Diagram
3. Deployment diagram
Class Diagram

Manage
1
Airport
+Airport_Name: String
1..*
Manage
Flight
+Plane_number:String
+Flight_destination: String
+Flight_time: Double
+Flight_number: String
International Flight
Domestic Flight
+City_Name: String
+Country_Name: String
Class Diagram
Flight Timing
+Plane_Number: String
+Flight_Number:String
Total_Passengers()
*
Weather & Route
+Wind_Pressure: Double
+Humidity_percentage: Double
+Weather_Forecast:String
Route_Avalibility( ): String
Passengers
1
* -Passengers_Name: String
+Passengers_Type: String
Total_Passengers(): Integer
+City_Name
Component Diagram
 Create
Administrator Reports
Reports

DBA

Manager

Flight Timing
Component Diagram

Passengers
Get Timing

Website
Weather & Route
Administrator

Database
Advantages / Disadvantages and Uses
of Component Diagram

 Component Diagram is useful when we have to make design of some device,

which has input output socket e.g. Camera, Mobile phones.
 It is not useful for designing of some software like web page, application etc.
 In our system AFSS, component diagram is not useful for better understanding
because AFSS is a software in which only data is needed.
 It represent the implementation of system.
Deployment Diagram
AFSS: DBA

<<artifact>> <<artifact>>
Flight Timing Create Report

<<artifact>>
Fuel Usage

Database

AFSS: Controller

<<artifact>> <<artifact>>
Plane Avalibilty Route C onfigurati on
Advantages / Disadvantages and Uses of
Deployment Diagram
 In deployment diagram, three dimensional rectangle is used to represent node.
 Deployment diagram is structural diagram. It is used to create architecture of some
system, e.g. architecture of computer which has processor, RAM, Hard disk etc.
 Deployment diagram is not useful for AFSS because AFSS is a software.
 It show clear architecture of system when some architectural design is created.
Behavioral Diagrams

 Behavioral diagram show the behavior of a system. It show how system behave in
a particular situation. It show what happen in a system. Some behavioral diagram
of AFSS are:-
1. Use case Diagram
2. Activity Diagram
3. State Transition Diagram
4. Sequence Diagram
5. Collaboration Diagram
Use case
log in

<<include>>
<<extend>>

Home page
bad pin

Store flight data

passengers data

take off and landing store route of flight fuel consumption

flight with date
and time
<<extend>>

warning!!
route already in use

fuel report
Maintinance
<<include>>
passengers and total
create report
flights report
Discription

 In this use case diagram only one administrator handle all the records.
 Administrator log in firstly which is non functional requirement.
 After log in home page is appeared.
 Administrator enter data on required field and automatically message is issued if
data is already in use.
 Administrator is also responsible for maintaining and creating reports.
 Start

login

valid

Enter Flight Data

fork
Activity Diagram

Flight Timing Flight Route

Plane Number issue

Time Checking With Check Route

Other Flights Avalibilty
Not Available
Not Available

Bad

Time
Weather

Available

Check Weather

Join

Enter Passengers
Data

End
State Transition Diagram
Start

Idle transaction Login

Getting Pin

Validation transaction Flight Data

validate pin timing and route Getting data

Passenger Data
exit
Getting Data
 pd:
Administrator lg: login fd: flight_data
Passengers_data

1: Pin Entered

2: Bad Pin

loop
Sequence Diagram

Flight_timing=true
3: Flight Timing Entered

4: Time Already exist

loop

flight_route=true

5: Route Entered

6: Route already exist

5: Passenger Data entered

Collaboration Diagram
Create_Report()

DBA Reports Passengers

AFSS
Management
System

Flight Schedule Fuel Usage

Flight Route
Advantages / Disadvantages and Uses
of Collaboration Diagram

 Collaboration diagram is the interaction diagram which show the interaction

between the entities.
 It show the functionality and behaviour of individual object as well as overall
operation of the system.
 It is suited in AFSS to show relationship between flights, planes, passengers,
timing& route etc.
 Collaboration Diagram harder to keep track of the flow of control.