Seminar on Building for Safety Certification (Biel/Bienne) - 22.5.12
Overview
In addition to the usual software delivery challenges of cost, features and schedules, industrial and medical device manufacturers must contend with specifying and validating their products’ functional safety, usually with the demanding goal of achieving certification by regulatory agencies.
Designing a functionally safe solution adds new requirements in various stages of product development. Special attention on functional safety at earlier stages of development will have the greatest impact, beginning with the critical step of selecting the right hardware and OS platform as a solid foundation.
Speaker biographie
Chris Hobbs is a kernel developer at QNX, specializing in "sufficiently-available" software: software created with the minimum development effort to meet the availability and reliability needs of the customer; and in producing safe software (in conformance with IEC61508 SIL3).
Chris Hobbs earned a B.Sc., Honours in Pure Mathematics and Mathematical Philosophy at the University of London's Queen Mary and Westfield College.
The changing
nature of safe software What has changed over the last 10 years and, implicitly, how has QNX
responded to the changes?
09.50
Functional Safety
and Risk Analysis Standards like 61508 (industrial automation), 51028 (railways) address
functional safety and downplay risk analysis. Standards like 62304 (medical)
address risk and specifically don’t talk functional safety. Standards like
26262 (automobiles) address both functional safety and risk. What are the
differences and why have they arisen?
10.20
Break
10.40
Implications
of developing a safe product.
How safe is “safe enough”? What is the role of the Safety Engineer?
The standards “recommend” and “highly recommend” certain development processes.
How does one get started on this type of development? The standards “recommend”
and “highly recommend” certain techniques and tools (e.g., semi-formal methods,
deep static analysis, recovery blocks, safety bag). What are the important
ones? How practical are they? This section would include demonstrations.
12:15
Lunch
13.30
Building the
Safety Case What goes into a Safety Case? How can it be structured?
14.30
Combining Safe
Components in a Design – first part Demonstration of how to create a system satisfying, e.g., IEC61508 SIL3,
from components including COTS/SOUP.
15:20
Break
15.30
Combining Safe
Components in a Design – second part
17.00
Closing
Triadem Mail Hide
Seminar on Building for Safety Certification (Biel) - 22.5.12
Producing safe software in conformance with IEC61508 SIL3 (industrial automation), EN 51028 (railways) and IEC 62304 (medical).
Date: Mai 22nd 2012
Cost: CHF 250 (lunch included)
