• DocumentCode
    1563748
  • Title

    Software Reuse in Safety-Critical Airborne Systems

  • Author

    Wlad, Joe

  • Author_Institution
    Product Manage., LynuxWorks, Inc., San Jose, CA
  • fYear
    2006
  • Firstpage
    1
  • Lastpage
    8
  • Abstract
    Today no formal guidance or standards exist which maximizes the utility of software reuse in any industry. This is especially true in the development of safety-critical software. As a result, the embedded industry has been far from the goal of making reuse a standard practice in software development. A new policy issued by the Federal Aviation Administration (FAA) promises to create a major shift in how software is reused in safety-critical systems. A reusable software components advisory circular published in December 2004, called AC 20-148, details the approach and documentation necessary for systematic reuse of software components that meet the guidelines of RTCA/DO-178B. To fully appreciate the value of a reusable software component (RSC), one must understand the history of safety-critical software standards and development. A brief overview of safety-critical software development and the RTCA/DO-178B standards is given as well as an overview of the Advisory Circular 20-148. A fully time and space partitioned operating system is used as an example in the paper
  • Keywords
    aerospace computing; aerospace safety; operating systems (computers); safety-critical software; software reusability; software standards; Advisory Circular 20-148; FAA; Federal Aviation Administration; RTCA/DO-178B guidelines; embedded industry; operating system; reusable software components advisory circular; safety-critical airborne systems; safety-critical software; software development; software reuse; Computer industry; Documentation; FAA; Guidelines; Programming; Software reusability; Software safety; Software standards; Software systems; Standards development;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    25th Digital Avionics Systems Conference, 2006 IEEE/AIAA
  • Conference_Location
    Portland, OR
  • Print_ISBN
    1-4244-0377-4
  • Electronic_ISBN
    1-4244-0378-2
  • Type

    conf

  • DOI
    10.1109/DASC.2006.313740
  • Filename
    4106346