Code covered by the BSD License  

5.0

5.0 | 1 rating Rate this file 24 Downloads (last 30 days) File Size: 9.89 MB File ID: #39047
image thumbnail

Testing of Safety Critical Control Systems

by

 

14 Nov 2012 (Updated )

This is a presentation on testing of safety critical control systems.

| Watch this File

File Information
Description

This is a presentation on testing of safety critical control systems updated with DO178C and DO331 parts. I have added a few slides on ISO 26262 comparing it with DO178. I have added a dormant error which was found after 12 years in a a flight control system.
 
An insight into the fascinating field of Model Based testing of Safety Critical Control Systems

An insight into the mistakes we make – again and again

A set of Best Practices in this field gleaned from the use of this type of testing on Aircraft Programs in India

Outline

• Safety Critical Control Systems – Brief Overview
• What are the mistakes we normally make? – a look at
the errors made in the various programs since 1988
• DO178B, DO178C and DO331 standard overview. How
are other standards related.
• What are these Models? – a look at how they function
– Algorithms for implementing them
• How do we test these blocks? – a block by block
approach
• Best Practices

Acknowledgements

This file inspired Safety Critical Control Elements Examples.

MATLAB release MATLAB 7.13 (R2011b)
Tags for This File   Please login to tag files.
Please login to add a comment or rating.
Comments and Ratings (1)
18 Aug 2013 Richard Vance

An excellent compilation!

You have shown the lack of focus on cost effective testing. That being the unit testing of algorithms should beat up the algorithms (assume all data values +-infinity to verify goodness. It is too expensive to find these faults in system testing. This presentation did a great service in presenting the objectives by phase and revealing a very weak design and development phase and really most of the objectives focused on verification (by test). You don't build a bridge then test it.. Its too late in the cycle. We need a far more rigorous in-development simulation and test program.. Kudos to developers that find their own weakness. Let's make sure the bridge is not just good but robust before building it.

Updates
02 Aug 2013

I have corrected the slides based on comments received. I have included a new error that was detected. The reference section is updated. I have added a few slides on other safety standards.

01 Apr 2014

I have added a few more slides on a dormant error and tools of trade.

Contact us