Article | REF: SE2510 V2

Standardization with regard to the operational safety of computer software

Author: Patrice KAHN

Publication date: October 10, 2012 | Lire en français

You do not have access to this resource.
Click here to request your free trial access!

Already subscribed? Log in!

Automatically translated using artificial intelligence technology (Note that only the original version is binding) > find out more.

    A  |  A

    Overview

    ABSTRACT

    This document presents a detailed and up to date panorama of the standardization in Software Dependability (Reliability, Availability, Maintainability and Safety (RAMS)) and an expert view on the applicability and the application of the principle standards. It then describes the similarities and differences by covering the major areas in which the failure of software can have serious consequences. It also addresses the certification of critical software.

    Read this article from a comprehensive knowledge base, updated and supplemented with articles reviewed by scientific committees.

    Read the article

    AUTHOR

    • Patrice KAHN: Consultant - Founding manager of KSdF-Conseil - Associate Professor at ISTIA (Engineering School of the University of Angers)

     INTRODUCTION

    Standardization in the field of software dependability (SdF) is the answer to two successive questions facing the various fields in which software plays an important role in terms of the safety of people and property.

    Why do we need to standardize software SoTL?

    To say that software has been omnipresent in the systems that surround us for many years now is almost an understatement. The stocktaking exercise necessitated by Y2K fears highlighted this trend, which has continued unabated ever since.

    The functions performed by such software are becoming increasingly critical in terms of the safety of people, the environment and property, and it is vital for all those involved (designers/developers, purchasers, control bodies, operators/users) to have the greatest possible control over the operation and malfunctions of these software-intensive systems.

    To achieve, or attempt to achieve, such a goal, it became necessary to try and standardize the practices to be implemented. This awareness has developed on a field-by-field basis, in parallel with the increasing preponderance of software in the field in question.

    What are the general standardization principles for software dependability?

    Whereas the quality approach must find an optimum between under-quality and over-quality, the SoF approach can be a permanent bidding war for a single objective: zero defects.

    This objective, which we know to be unattainable, and above all virtually unprovable in view of the increasing size of software, is increasingly being replaced by a more controlled objective: zero risk.

    In this context, the main aim of SoTL standardization is to identify the nature and consequences of risks, and, depending on the level of risk identified, the properties to be respected, the methods imposed or strongly recommended, and the evidence expected of their application, with the main aim of ensuring that customers, certification bodies and project managers are able to control all these risks.

    You do not have access to this resource.

    Exclusive to subscribers. 97% yet to be discovered!

    You do not have access to this resource.
    Click here to request your free trial access!

    Already subscribed? Log in!


    The Ultimate Scientific and Technical Reference

    A Comprehensive Knowledge Base, with over 1,200 authors and 100 scientific advisors
    + More than 10,000 articles and 1,000 how-to sheets, over 800 new or updated articles every year
    From design to prototyping, right through to industrialization, the reference for securing the development of your industrial projects

    KEYWORDS

    normative approach   |   standards   |   railways   |   medicine   |   car   |   aeronautics   |   electronic programmable system   |   functionnal safety


    This article is included in

    Software technologies and System architectures

    This offer includes:

    Knowledge Base

    Updated and enriched with articles validated by our scientific committees

    Services

    A set of exclusive tools to complement the resources

    Practical Path

    Operational and didactic, to guarantee the acquisition of transversal skills

    Doc & Quiz

    Interactive articles with quizzes, for constructive reading

    Subscribe now!

    Ongoing reading
    Standardization for software dependability