The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.03 - May-June (2013 vol.30)
pp: 67-72
Yogananda Jeppu , Moog India Technology Centre
ABSTRACT
Aerospace or flight control systems software development follows a rigorous process according to the RTCA DO-178B standard, yet software errors still occur. A review of the mistakes found during flight control test activities spanning 23 years reveals that the same mistakes tend to recur repeatedly. Moreover, we haven't yet learned everything about the mistakes that can be made in flight controls; new mistakes continue to pop up.
INDEX TERMS
Aerospace control, Software reliability, Digital filters, Air traffic control, Safety, Mathematical model, Air safety, safety-critical software, software and system safety, test design, certification, software engineering
CITATION
Yogananda Jeppu, "Flight Control Software: Mistakes Made and Lessons Learned", IEEE Software, vol.30, no. 3, pp. 67-72, May-June 2013, doi:10.1109/MS.2013.42
REFERENCES
1. N.G. Leveson, Engineering a Safer World: Systems Thinking Applied to Safety, MIT Press, 2012.
2. Y.V. Jeppu, K. Karunakar, and P.S. Subramanyam, Flight Clearance of Safety Critical Software Using Non Real Time Testing, tech. report AIAA-2002-5821, Am. Inst. Aeronautics and Astronautics, 2002.
3. Std. DO-178B/C, Software Considerations in Airborne Systems and Equipment Certification, RTCA, 2011.
4. C. CU et al., “A New Input-Output Based Model Coverage Paradigm for Control Blocks,” Proc. 2011 IEEE Aerospace Conf., IEEE, 2011; doi:10.1109/AERO.2011.574 7530.
8 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool