Knowledge of development and programming (for Module 2)

Project managers, quality managers, designers, developers, verifiers, validators

• Identify the normative requirements for specifying, defining the HW/SW architecture and controlling safe systems and software
• Present best practices for the specification, architecture and design of Systems, Hardware and Software
• Master the techniques of testing and validation of systems, hardware and software

Experts in Operational Safety

Projected and printed PowerPoint presentation, practical case study, exercises, role-playing, theoretical example, video material…

Evaluation at the beginning and end of the course, quiz…

5 working days before the start of the course (if OPCO funding)

This training is based on a strong feedback from the implementation of the Safety of Life requirements for embedded systems and software developed for critical applications. The main contribution of this training lies in our ability to provide a detailed level of information on the understanding of the specificities of this standard.

MODULE 1 – DAY 1

• Introduction to Functional Safety
• Overview of IEC 61508
• Technical requirements IEC 61508-1
• The analysis phases
• Concept and overall definition of the field of application
• Hazard and risk analysis
• Overall safety requirements
• Allocation of global safety requirements (HW/SW architecture)
• The operation phases
• The realisation phases
• Other requirements IEC 61508-1

MODULE 1 – DAY 2

• Technical requirements IEC 61508-2
• Safety integrity of the hardware
• Architectural constraints on safety integrity
• Quantification of random hardware failures
• Systematic failures
• Avoidance and control of systematic failures
• Systematic capability
• Proof that the material is “Proven in Use
• Behaviour of the system on detection of a fault

MODULE 2 – DAY 1

• Introduction to IEC 61508-3
• Development process (PAQL)
• Software specification (best practice)
• Software architecture (best practices, defect detection and protection techniques)
• Software design (good practice)
• Design rules to be favoured at the architecture, detailed design and coding levels (modularity, defensive programming, COTS, etc.)
• C language programming rules (functions, instructions, data)
• Code presentation rules for quality (readability, traceability…)
• Presentation of a static analysis tool

MODULE 2 – DAY 2

• Presentation of test activities (organisation, structural and functional test coverage)
• Verification of the software (document analysis, traceability, cross-referencing, static analysis, etc.)
• Low-level testing (unit testing, software/software integration testing)
• High-level testing (software/hardware integration testing, validation testing)
• Software safety analysis (LCC, AEEL, test review…)
• Tools used (static code analysis, unit and integration tests, modelling, configuration management, compilers, traceability, etc.)
• Classification of tools

• Date sur demande, toute l'année