Building ATC Simulator through Scenario-Driven Requirements Engineering

Abstract

The Federal Aviation Administration (FAA) Academy is challenged with limited availability of Air Traffic Control (ATC) training technologies for their trainees. Training is conducted over simulation scenario runs in dedicated ATC lab spaces under the supervision of ATC instructors. Current ATC training tools lack flexibility and cost effectiveness to provide 24/7 service to the trainees as well as providing dynamic fast prototyping environment for scenario development. Due to the number of trainees and cost of operation of ATC labs, trainees can only practice for limited amount of time, hindering their learning experience. Through a recent funded research project, Embry-Riddle Aeronautical University is tasked with building a web-based ATC En route simulator that mimics the FAA En route automation environment, allowing trainees to practice ATC scenarios at their own pace. The proposed simulation technology, namely ATC Scenario Training Technology (ASTT) mimics En route Automation and Modernization (ERAM) functionalities and provides a web-based practice platform to en route trainees. One technique in capturing software requirements is to study various system usage and functionalities scenarios that highlight top-level and low-level details. To apply this approach to ASTT project, a set of en route scenarios were developed and discussed during the requirements elicitation phase. For each given scenario, key elements were highlighted and relationships amongst them were established. Requirement modeling diagrams and documentations were then constructed, fully capturing ASTT details. In this paper, we demonstrate a rather non-traditional requirements engineering approach in extracting information for building an ATC simulator. Similar to the concept of user stories in software development projects, simulation scenarios can be used to extract essential details for designing and building simulators. ASTT requirements modeling and system architecture are discussed in this paper by presenting a sample ATC en route scenario and discussing our approach in extracting requirements details from it.