Abstract
DataComm is a program that will enhance existing communications between the air traffic controller and the pilot by sending digital messages to supplement the existing voice communications. With more reliance on DataComm as the FAA's Next Generation systems become fielded, ensuring the communications is reliable, accurate, and most importantly safe becomes increasingly critical. RTCA DO-278 provides the guidelines for communications, navigation, surveillance, and air traffic management systems software integrity assurance. It doesn't guarantee that the software developed in accordance with these guidelines is safe but if followed it ensures that the processes are in place to properly plan, develop and verify the software. Lockheed Martin is in the process of integrating DataComm with the En Route Automation and Modernization (ERAM) program and is developing the program in compliance with DO-278. This brings challenges as well as opportunities with the increasing reliance on commercial off the shelf (COTS) software. These challenges and some insight into developing systems to the standards of DO-278 will be discussed.
- RTCA SC-167. 1992. Software Considerations in Airborne Systems and Equipment Certification, December 1, 1992.Google Scholar
- RTCA SC-190. 2002. Guidelines for Communication, Navigation, Surveillance, and Air Traffic Management (CNS/ATM) Systems Software Integrity Assurance, March 5, 2002.Google Scholar
Index Terms
Systems software integrity assurance
Recommendations
Systems software integrity assurance
SIGAda '10: Proceedings of the ACM SIGAda annual international conference on SIGAdaDataComm is a program that will enhance existing communications between the air traffic controller and the pilot by sending digital messages to supplement the existing voice communications. With more reliance on DataComm as the FAA's Next Generation ...
Software safety: relating software assurance and software integrity
The overall safety integrity of a safety critical system, comprising both software and hardware, is typically specified quantitatively, e.g., in terms of failure rates. However, for software, it is widely accepted that there is a limit on what can be ...
Issues in the application of software safety standards
SCS '05: Proceedings of the 10th Australian workshop on Safety critical systems and software - Volume 55The application of software safety standards as part of the development of safety critical software is usually considered an essential element of any safety program. Yet it is fairly rare for safety practitioners to step back and critically evaluate ...







Comments