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 articleAUTHOR
-
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.
Exclusive to subscribers. 97% yet to be discovered!
Already subscribed? Log in!
KEYWORDS
normative approach | standards | railways | medicine | car | aeronautics | electronic programmable system | functionnal safety
Standardization for software dependability
Article included in this offer
"Safety and risk management"
(
459 articles
)
Updated and enriched with articles validated by our scientific committees
A set of exclusive tools to complement the resources
Bibliography
- (1) - - Directive 93/42/EEC du 14 juin 1993, publiée au journal officiel des Communautés européennes n° L 169, 12 juil. 1993.
- (2) - MISRA - Guidelines for the use of the C language in vehicle based software. - MISRA (2008).
Exclusive to subscribers. 97% yet to be discovered!
Already subscribed? Log in!