No abstract

SUMMARYStatic code analysers help in exposing internal code quality problems. For higher effectiveness, they must be pressed into use early during the development of code. They must support the formulation of new coding constraints with relative ease to better cope with variations in coding standards. We present the design of a static analyser that addresses these twin objectives. Our system provides interactive feedback to programmers on the non-conformances that occur in response to the changes made to the code. Its rule construction framework empowers programmers to define new conformance rules, which can come into effect immediately after creation. The tool has been realized as an Eclipse plug-in for the analysis of C, C++ and Java sources. Central to its design is the concept of reusing a set of primitive checks by composing them to form new rules. This renders rule construction accessible to programmers, lowers dependence on tool smiths and accelerates the enforcement of custom checks. We also present our experience in defining rules drawn from an industry standard rule set based on this approach.

Airports face financial constraints in the use of services of air traffic control (ATC) towers. The remote air traffic control system (RATCS) is anticipated to be an economical and safe alternative to a control tower. RATCS is a concept intended to supply ATC to an airport by providing communication, navigation, and surveillance from a remote location. This study aims to gain insights about RATCS by conducting a review of existing studies, airport visits, discussions with RATCS technology providers, RATCS demonstration visits, and questionnaire surveys and interviews of controllers. A major inference from nontowered airport visits is that the introduction of RATCS will present many challenges such as pilot readiness to be supervised by RATCS, differences in local conditions, and significant limitations in available infrastructure. The knowledge gained through airport–demonstration visits and meetings with RATCS providers assisted in designing a questionnaire survey and interview. The number of surveys and interviews was limited; hence, conducting a comprehensive quantitative evaluation from responses was difficult. Nevertheless, controllers who participated in the study developed a consensus. The survey outcomes showed that controllers had concerns about RATCS functionality for communication or coordination between controllers and for ATC in high traffic conditions. The controllers provided favorable responses toward new features of RATCS, such as infrared cameras, high-definition monitors, target tracking functionality, and runway overlays. Potential advantages of RATCS anticipated by some controllers include systems with replay capabilities, situational awareness capabilities in low-visibility conditions, and surveillance capabilities of ground operations.

No abstract