Standards, draft standards, and guidelines that provide requirements for the assurance of high integrity software are studied. The focus is on identifying the attributes necessary in such documents for providing reasonable assurance for high integrity software, and on identifying the relative strengths and weaknesses of the documents. The documents vary widely in their requirements and the precision with which the requirements are expressed. Security documents tend to have a narrow focus and to be more product oriented, while safety documents tend to be broad in scope and center primarily on the software development process. It is found that overall there is little relationship between the degree of risk and the rigor of applicable standards. Recommendations are provided for a base standard for the assurance of high integrity software.<>


    Access

    Check access

    Check availability in my library

    Order at Subito €


    Export, share and cite



    Title :

    An analysis of selected software safety standards


    Contributors:
    Wallace, D.R. (author) / Kuhn, D.R. (author) / Ippolito, L.M. (author)


    Publication date :

    1992-08-01


    Size :

    1306122 byte




    Type of media :

    Article (Journal)


    Type of material :

    Electronic Resource


    Language :

    English



    Methodology for Software Safety Standards

    Herrmann | Online Contents | 1996


    `Harmonisation of defence standards for safety-critical software'

    Marshy, D. W. R. / ERA Technology | British Library Conference Proceedings | 1997


    The Need for Safety-Related Software Development Standards

    Ward, D.D. / Society of Automotive Engineers; Transportation Electronics Association | British Library Conference Proceedings | 2008



    The impact of safety-critical systems standards on avionics software

    Canning, A. A. / ERA Technology | British Library Conference Proceedings | 1992