Implementation of Implementation of Distributed Air Traffic Control Simulator Distributed Air Traffic Control Simulator

Ranko Radovanović, Miloš Cvetanović, Zaharije RadivojevićSchool of Electrical Engineering, Belgrade University

13th Workshop “Software Engineering Education and Reverse Engineering”

Bansko, Bulgaria26-31 August 2013

13th Workshop SEE and RE 2/17

AgendaAgenda

• Simulation related courses• Bachelor thesis • Structure of traffic control simulator• Implementation details• Conclusions

13th Workshop SEE and RE 3/17

MotivationMotivation

• Defining set of bachelor thesis based on simulator design

• Courses related to simulator design are in 6th semester (of 8 semesters)– Computer Architecture and Organization 2– Concurrent and Distributed Programming

• Modifying requirements for particular student based on the developed core

• Balancing with different techniques necessary for the project

13th Workshop SEE and RE 4/17

Computer Architecture and Computer Architecture and Organization 2Organization 2• Type: Mandatory course (now elective)• Starts: 6 semester• Prerequisites: Basics of Computer Engineering, Computer

Architecture, Computer Architecture and Organization 1• Class hours: 2+2+1• Format:

– Midterm 20– Laboratory 20– Project 40– Final 20

• CE ~100 students

13th Workshop SEE and RE 5/17

Concurrent and Distributed Concurrent and Distributed ProgrammingProgramming• Type: Mandatory course• Starts: 6 semester• Prerequisites : Operating Systems,

Object Oriented Programming• Class hours: 2+2+1• Format:

– Midterm 40– Laboratory 20 or– Project 20 (Distributed Processing, single student)– Final 40

• CE ~110 students

13th Workshop SEE and RE 6/17

Existing simulators limitationsExisting simulators limitations

• Single or limited number of sectors• Static roll handling

(computer IP addresses must be known in advance)• No interactions (standalone)• No pilot application• Platform dependence

13th Workshop SEE and RE 7/17

Simulator requirementsSimulator requirements

• Modularity• Multiple implementations• Creating scenarios (exercises)• Controllability (Start/pause/stop option)• Platform independence• Realistic • Unlimited number of sectors• Using standard hardware• Scalability

13th Workshop SEE and RE 8/17

Control systemControl system

•

13th Workshop SEE and RE 9/17

Outline of the simulator architectureOutline of the simulator architecture

•

13th Workshop SEE and RE 10/17

Automatic coordinationAutomatic coordination

• Communication between two control applications by using central serer

• Using European stand OLDI type of messages• Centralized application where server sends

coordinates messages to clients

13th Workshop SEE and RE 11/17

Automatic coordination – request Automatic coordination – request sendingsending•

13th Workshop SEE and RE 12/17

Automatic coordination – request Automatic coordination – request sendingsending•

13th Workshop SEE and RE 13/17

Automatic coordination-request Automatic coordination-request receivingreceiving•

13th Workshop SEE and RE 14/17

Pilot applicationPilot application

• Controls airplanes using standard models (changeable)

• Planes are in separate threads (changeable)• Communication with central server

13th Workshop SEE and RE 15/17

Pilot applicationPilot application

•

13th Workshop SEE and RE 16/17

ScalabilityScalability

• Simulator was tested using optimal number of sectors (4 sectors – 8 clients)

• Number of airplanes was 16 to 64 in sectors

• Processor utilization (5 до 10%), • Memory utilization (~ 4MB) • Network utilization (0.1 mbps).

• Core classes for support in simulator design• Support for laboratory exercises• Modular and extendable structure• Interdisciplinarity

13th Workshop SEE and RE 17/17

ConclusionConclusion

Thank you!Thank you!

Radivojevic Zaharije