Reusable Avionics Software Evolution of the Flight Management System

摘要

In the early 80's avionics software applications were designed for specific applications. Software development process technology was just beginning to evolve along with the applications. Very little thought was given to assuring that the designs were both reusable and partitionable. Changes or enhancements to these designs for follow on applications tended to be costly due to regression concerns and re-certification activities. The more complex the software the higher the costs. At the same time customers were demanding enhanced avionics for lower prices than what they paid for the original development. Changes needed to be justified from a cost/benefit basis before they would pay the price for a change.rnAs we pushed into the 90's customer's demands coupled with vendor's experiences with modification of software and evolution of software development processes has brought the concept of re-usable and partitioned software development to the fore front. The challenge was further complicated by the desire for commonality across aircraft types for avionics operation.rnThis paper will look at the reuse evolution of the Honeywell Flight Management System software (FMS) from the Boeing 757/767 and Airbus A310 development of the 1980's to the advanced designs of the Airbus A340 and Boeing 777 of the 1990's. This paper will explore the lessons learned and the future challenges for the development, modification and maintenance of software in a reusable environment.