Functional safety of electrical/electronic/programmable electronic safety-related systems – Part 3-3: Object-oriented software in safety-related systems
Introduction: This document addresses specific concepts associated with object-oriented (OO) software. It deals only with OO software in general without referencing any specific language. Each of the concepts is discussed under separate clauses, one addressing fundamentals – i.e. benefits, disadvantages and counter-measures to the disadvantages, the others detailing guidance on the attributes to be satisfied in safety-related systems, according to the systematic capability to be achieved. It is useful to consider addressing the language-specific best practice contained in guidelines, coding rules, handbooks etc. for each OO language. If an object-oriented module is modified, it is proposed that the entire module conform to the guidance within this document. Further, it is useful to consider assessing the interfaces, interactions and side effects on unchanged modules to determine that there is no impact on other unchanged modules and their integration. See also IEC 61508-3:2010, Annex D. This document is intended as a supplement to the existing requirements in the IEC 61508 series which continue to apply.
Scope: This part of IEC 61508, which is a Technical Report, makes a proposal as to which topics to consider and which methods and techniques to use when designing object-oriented software to ensure suitable quality for use in functional safety applications. Object-oriented languages are perceived as "state-of-the-art" nowadays. Such languages seem to be excluded from use by several statements in IEC 61508-3. However there are additions in some tables such as in IEC 61508-3:2010, Table B.1, where notes are added under which their use might be justified. Such exceptions that would allow, for example, dynamic objects, name the main concerns such as memory allocation and predictable timing issues and guide the user to safe use of object-oriented languages. These considerations are taken up in this document to specify methods and techniques that allow the reduction of systematic faults to the levels required by the respective systematic capabilities. This document is not intended to replace any part of IEC 61508-3. Rules that exist in IEC 61508-3 are valid here as well and are not repeated, including rules that concern: the software life cycle, involvement of the assessor, modularization, principle of information hiding, proving and conventional testing, basic aspects of documentation, low coupling and high cohesion, responsibilities and training of people, operational experience as described in IEC 61508-4 and IEC 61508-7.
Contents:
- FOREWORD
- INTRODUCTION
- Scope