• DocumentCode
    2795675
  • Title

    Software safety analysis: using the entire risk analysis toolkit

  • Author

    Guthrie, Vernon H. ; Parikh, Piyush B.

  • Author_Institution
    ABA Consulting, Knoxville, TN, USA
  • fYear
    2004
  • fDate
    26-29 Jan. 2004
  • Firstpage
    272
  • Lastpage
    279
  • Abstract
    When an accident occurs, it is common to attribute the accident to a failure in the system. Therefore, precautions must be taken to design the system to provide safeguards that supports the system even when failures occur. The problem, however, is that accident occur where there is no failure in the system (i.e., the software, hardware, and humans "work" as they are supposed to). The flaw is in the design oversight for specific high-risk situations. It is up to the decision maker to: (a) ensure that adequate design and safety checks have been performed before the system is put into operation (b) ensure that a comprehensive risk analysis is conducted to examine both the design element malfunctions and the design oversights to determine the loss sequences (c) be satisfied that the loss sequences are understood with adequate confidence that the system risk is at or below the risk acceptance criteria.
  • Keywords
    risk analysis; software reliability; systems analysis; risk analysis toolkit; software safety analysis; systems design; Accidents; Failure analysis; Fault trees; Hardware; Humans; Risk analysis; Software design; Software performance; Software safety; Software systems;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Reliability and Maintainability, 2004 Annual Symposium - RAMS
  • Print_ISBN
    0-7803-8215-3
  • Type

    conf

  • DOI
    10.1109/RAMS.2004.1285460
  • Filename
    1285460