Article | REF: BM8071 V1

Securing mechatronic systems - Part 2

Author: Jean-Louis BOULANGER

Publication date: January 10, 2011

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

Already subscribed? Log in!


Overview

Français

ABSTRACT

Mechatronic systems are becoming increasingly complex. As a result they induce multiple failures. Securing these systems is aimed at combating these errors and attempting to limit the risk. This article focuses on the software application aspect on which the security relies on quality control. Fault-tolerant programming techniques (redundancy, error detection or defensive programming) are presented. Errors are often due to the artisanal nature of the implementation of a software application, and the use of tools from a development environment that detracts from the software’s inherent complexity.

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

Read the article

AUTHOR

 INTRODUCTION

In this second part [BM 8071] on securing mechatronic systems, we focus on the "software application" aspect (IT component). The risk associated with the hardware architecture (electronic component) was dealt with in the first part [BM 8 070] . For basic concepts and standards applicable to securing mechatronic systems, please refer to [BM 8 070] .

The security of a software application depends primarily on quality control (fault avoidance and elimination). We present :

  • the principles of quality control (ISO 9001:2000) ;

  • some tolerant programming techniques (redundancy, error detection or defensive programming) ;

  • the contribution of formal methods.

Nowadays, anyone can create a software application. The availability of development environments (Case Tools , cf. [Doc. BM 8 070]), offering modeling, verification and automatic code generation, has greatly simplified the development of a software application. But the main feature of software is the presence of bugs. These faults can be systematically executed, and their presence is due to the artisanal nature of software development. The use of development environments gives the impression of industrializing the production of a software application, but this is not the case. In fact, the tools of a development environment are classically developed, and their use tends to make us forget the intrinsic complexity of the software through more or less clear graphical representations. The presence of errors is a fact, and they must be accepted, managed and corrected.

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

This article is included in

Vehicules and mobility

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
Securing mechatronic systems. Part 2