AN AIRPORT SIMULATION

A Multi- Threaded Airport Simulation

Aim: to create a Multi- Threaded Airport Simulation

Actors:

ATC Controller

Use Cases

1. ATC Controller
2. Decision Support System
3. Planning
4. Emergency
5. Sensor
6. Gateway
7. Runway
8. Terminal
9. Available
10.Waiting Queue

Algorithmic Procedure:

STEP 1: Start the application

STEP 2: Create the require actors and use cases in the browser
window
STEP 3: Go to new use case view and then click the use case view and
Open a new package
STEP 4: Rename the new package with the package with required
Names
STEP 5: Create two packages actor and use case

Overview
 A critical step of the project is to design a modeling and
simulation infrastructure to experiment and validate the proposed solutions
The ever growing demand of air transport shows the vulnerability of
the current air traffic management system: Congestion, time delays,
etc.particularly in poor whether conditions.
The project is focused on controller and pilot assistance systems for
approach and ground movements. The critical step of the project was to
design an airport modeling and simulation infrastructure to improve the
safety and efficiency of ground movements in all whether conditions. It
simulates the arrivals and departures at an airport in a time sequence.
During every minute, planes may enter the systems, they may land, they
may take off, or they may crash. The project must keep track of planes,
assign planes to runways, execute the take offs and landings, and keep track
of status of each plan, runway and terminal.
So the finally made computer software should model various
aspects of the total airports operation-connecting airside and landside,
literally from the airspace to the curb.
As part of case study, following analysis diagrams will be created
1. Use cases for the system.
2. Class diagram for initially identified classes.
3. Activity diagram to show flow for each use case.
4. Sequence and Collaboration diagram.
5. State chart diagram shows states before and after each action.

Conceptualization

Assumptions;
 All take offs take the same amount of time and all landings take the
same amount of time (through these two times may be different).
 Planes arrive for landing at random times, but with a specified
probability of a plane arriving during any given minute.
 Planes arrive for take off at random times, but with a specified
probability of a plane arriving during any given minute
 Landings have priorities over takeoffs.

 Planes arriving for landing have a random amount of fuel and they will
crash if they do not land before they run out of fuel.

Input will be:

 The amount of time needed for one plane to land.
  The amount of time needed for one plane to takeoff.
 The probability of a plane entering the landing queue in any given
minute.
 The probability of a plane entering the takeoff queue in any given
minute.
 The maximum minutes until a plane waiting to land will crash.
 The statues of each runway, plane and terminal.

The Output of the program will be:

 Total simulation time.
 The number of planes that takeoff in the simulated time.
 The number of planes that landed in the simulated time.
 The average time a plane spent in the takeoff queue.
 The average time a plane spent in the landing queue.
 Updated status of each runway, plane, and terminal.

Key terms:
 Aircraft simulation.
 Airport: runways, terminals, planes, control room.
 Aircraft: passengers, model no. cockpit, pilots.
 Function points:
1. Transmit/receive signals.
2. Pilot sends signals for takeoff/landing.
3. Loop
- Check status of each runway.
- Finalize a free runway.
- Assign the runway to the plan.
4. Update status of runway and terminal.
5. Get the plane landed safely.
6. Check if time left for next departure.
7. Loop
- Check the status of each terminal.
- Validate if terminal suitable for particular aircraft.
- Assign terminal to aircraft.
8. Get the plane parked in the terminal.
9. Update status of terminal.

Requirement Analysis:

Textual Analysis:
 This covers the requirements and diagrams of the project. The
complete simulation of airport control system as follows
Actors:
These are who are involved in interaction of the whole process.
1. Technical head: He is the person who supervises the controls the
ground traffic on runway. He checks the status of runways and assigns
the free runways and terminals for takeoff and landing.
2. Pilot: He is the person who controls the aircraft. He transmits or
receives signals regarding the free runways, and terminal from the
control room. He is responsible for the safe landing or takeoffs the
planes.

Use cases:
The steps involved in the whole process are indicated as use cases.
 Transmit/receive signals.
 Check availability of runways.
 Land the plane.
 Check if time left for next departure.
 Check for free terminal.
 Update status of runway, terminal.
1. Transmit/receive signals: The pilot in the aircraft transmits signals
for requesting a free runway to takeoff or land. The control room on
the ground receives these signals from the aircrafts.
2. Check availability of runway: The status of each runway in the
airport is checked if it’s free and its going to be free until the particular
aircraft is landed or takeoff. If this is going to be free then runway
number is transmitted to the pilot on aircraft.
3. Land the plane: The plane is landed safely on the airport as per
directions given by the control room regarding runway and timings.
4. Check if time left for next departure: If the plane leaves
immediately after landing then assign again a runway for takeoff. If
there is still time then the plane has to be parked in a terminal.
5. Check availability of terminals: the status of each terminal is to be
checked to find a free terminal. It should be checked whether that
particular model of plane fits into that terminal. Then that particular
terminal has to be assigned to the plane.
6. Update Status: the status of runway and terminal are to be set to be
using while using them. The status has to be immediately changed as
 soon as the work is complete. This should be supervised carefully to
avoid collisions and crashes of aircrafts.

Classes:
The classes contain the attributes and operations related to them the
main classes classified in this solution are:
1. Control Room: he is the person who supervises the controls the
ground traffic on runway. He checks the status of runways and assigns
the free runways and terminals for takeoff and landing.
2. Plane Cockpit: He is the person who controls the aircraft. He
transmits or receives signals regarding the free runways and terminals
from the control room. He is responsible for the safe landing or takeoff
of the plane.
3. Runway: This is the part the planes use to land or takeoff only one
plane can use runway at a time to takeoff or land.
4. Terminal: This is the place where the planes are parked until the next
departure. The terminal is to be parked in it.
5. Takeoff/land: The leaving of planes is called takeoff and coming back
to runway is called landing. The runway is used for either purpose.

Diagrams:
Class Diagram
A Class is a standard UML construct used to detail the
pattern from which objects will be produced at run time. A class is a
specification- an object is an instance of a class. Classes may be inherited
from other classes, have other classes as attributes, delegate responsibilities
to other classes and implement abstract interfaces.
Classes of airport simulation are:
Class Attributes Operations
Control Room -Technical head +Receive signals from
-No of staff planes()
-systems to control +Check for free
runway()
+Send runway no()
+Check for next
departure()
+Look for free
terminal()
+Send terminal no to
plane()
+Get plane parked()
Takeoff/Landing -Runway no +Update status of
 -Flight no runway after each take
-Status of or landing()
-Time taken
Plane Cockpit -No of pilots +Send signal to ground
-Flight no station()
-Destination +Receive runway no()
-Timings +Land on runway()
+Request terminal if
time left for next
departure()
+Receive terminal no()
+Get the plane parked
in the terminal()
Terminal -No of runways
-Size of terminal --------------------
-Flight model which fits -----
in
-Status of terminal
Runway -No of runways +Update status of
-Length of runway runway after each
Status of runway takeoff/landing()
-Free timings
-Runway no

Use Case Diagram

The use case model describes the proposed functionality of

the system. A use case represents a discrete unit of interaction between a
user and the system. A use case is a single unit of meaningful work. Each
use case has a description which describes the functionality that will be built
in a proposed system. A use case may ‘include’ another use case
functionality or ‘extend’ another use case with its own behavior.
Actors Use cases
Technical head .Transmit/Receive signals
.Look for free runway
.Check whether conditions
.Give directions to aircraft
.Look for free terminal
.Get the plane parked in the free
Terminal pilot .Transmit/Receive signals
.Land or takeoff the plane
Safely .Give acknowledgment about the
timings to control

Terminal .Get the plane into the free

Sequence diagram

UML provides a graphical means of depicting object interactions

over time in sequence diagrams. These typically show a user or actor
and the objects and components they interact with in the execution of
a use case.
1. Technical head: He is the person who supervises the controls the
ground traffic on runway. He checks the status of runways and
assigns free terminals for takeoff and landing.
2. Pilot: He is the person who controls the aircraft. He transmits or
Receives signals regarding the free runways and terminal from the
control room. He is responsible for the safe landing or takeoff the
planes.

Objects
1. Runway: This is the path the plane uses to land or takeoff. Only
one plane can use a runway at a time takeoff or landing.
2. Takeoff/Landing: The leaving of plane is called takeoff and
coming back to runway is called landing. The runway is used for
either purpose.
3. Whether Conditions: The whether department decodes the
atmospheric data files from the current whether conditions and
sends them to the control room. The systems in the control room
checks whether the condition is suitable for landing the planes.
4. Terminal: This is the place where the planes are parked until the
next departure. The terminal differs in size and shape. The plane
suitable for that particular terminal is to be parked in it.
 5. Cockpit: He is the person who controls the aircraft. He transmits
or receives signals regarding the free runways and terminal fro the
control room. He is responsible for the safe landing or takeoff of
the planes.

Collaboration Diagram

Collaboration names a society of classes, interfaces and

other elements that work together to provide some cooperative behavior
that is bigger than the sum of all its parts. Collaboration diagram
emphasis is based on structural organization of the objects that send and
receive messages.

Activity Diagram

An activity diagram is essentially a fancy flowchart. Activity

diagrams and state chart diagrams are related. While a state chart diagram
focuses attention on an object undergoing a process (or on a process as an
object), an activity diagram focuses on the flow of activities involved in a
single process.
The activity diagram shows the how those
activities depend on one another. Activity diagrams can be divided into
object swim lanes that determine which object is responsible for which

activity. A single transaction comes out of each activity, connecting it to the

next activity.

State Chart Diagram

Objects have behaviors and state. The state of an object

depends on its current activity or condition. A state chart diagram shows the
possible states of the object and the transitions that cause a change in state.
The initial state (black circle) is a dummy to start the action. Final states are
also dummy states that terminate the action.

Component Diagram

A component is a code module. Component diagrams are

physical analogs of class diagram. Each component belongs on a node.
Components are shown as rectangles with two tabs at the upper left.
Deployment Diagram

Deployment diagram shows the physical configurations of

software and hardware.

Class Diagram
Use Case Diagram
 send/receive signal

check availability of run awy

send/receive run way num

land / aircraft

send / receive terminals

numbers Plane cockpit
Control room

check free terminals

send / receive terminal

numbers

park aircraft

update status of runway

Sequence Diagram
 Airport Simulation

p:prane T:terminal R:runway W:WeatherD

: control room
Cockpit ept
1: request signal

2: send signal

3: Check Weather conditions

4: send acknowledgement

5: check avaliable for run way

6: wait signal

7: send signal

8: send ack

9: update runway status

10: if time is for next dep send req

11: if terminal is free send terminal no

12: send terminal

13: land aircraft

14: update status of terminal

Collaboration Diagram
 p:prane
Cockpit 10: if time is for next dep send req
1: request signal
11: if terminal is free send terminal no
6: wait signal
7: send signal 14: update status of terminal
8: send ack
12: send terminal
13: land aircraft

T:termin
: control room
al
5: check avaliable for run way
9: update runway status

2: send signal

4: send acknowledgement

R:runwa
y 3: Check Weather conditions

W:Weather
Dept

Activity Diagram

Runway allocation for takeoff Activity Diagram

 landing

give aircraft
info to lock s/m

lock system
checking for ks

no all locks are locked

yes
acquire landing priority
area lock

acquire
runway lock landing on
another runway

aircraft at acquire
take off area terminal lock

if the aircraft is at takeoff area then

release terminal and taxiing locks acquire
while moving from takeoff area taxiing lock
release takeoff area lock and acquire
runway lock
move to the terminal gate and
release terminal and taxiing
lock

Runway allocation for takeoff Activity Diagram

 takeoff

acquire terminal lock

give aircraft
info to lock s/m

checks
for locks

if locks are available

acquire takeoff
area lock

acquire
taxiing lock

aircraft at acquire
takeoff area runway lock

use the runway for takeoff and release

if the aircraft is at the takeoff runway lock
area then release terminal and
taxiing lock while moving from
takeoff area release takeoff area
lock and acquire runway lock

State Chart Diagram

 wait for weather req runway status wait for
conditions running status

req runway no

wait for
runway no

avail not avail

wait for terminal if time left land on

status runway

avail
not avail

wait for
terminal no

not avail
avail

halt

Component Diagram
 terminal
lock.java

central
landing.jav
server java
a

takeofflock
.java

taxiinglock.
central server java
.class / .dll

terminalloc
k.class

landing.cla
ss

takeofflock
.class

taxiinglock.
class

airport.db
central
database

priority.db
Deployment Diagram

<<DATA BASE>>
central database

<<SERVER>>
central server

<<WIRELESS COMMUNICATION>>

<<DEVICE>>
<<DEVICE>> <<DEVICE>> <<DEVICE>> control manager
aircarft controlor lockmanager taxiing
manager

Result
The various UML diagrams were drawn for AIRPORT SIMULATION
SYSTEM application and the corresponding code was generated.