REGISTER | LOGIN
Breaking News
Comments
Pho99
User Rank
Author
Interesting -- This seems to be the first offering by a silicon OEM in this area
Pho99   7/1/2013 6:28:23 AM
NO RATINGS
Interesting -- This seems to be the first offering by a silicon OEM in this area

MeasurementBlues
User Rank
Author
Software safety
MeasurementBlues   7/1/2013 8:18:52 AM
NO RATINGS
What are the main reasons for IEC 61508 and ISO 26262? How does software get tested for safety?

Peter Clarke
User Rank
Author
Re: Software safety
Peter Clarke   7/1/2013 8:27:56 AM
NO RATINGS
IEC 61508 is a standard on the functional safety of electrical and electronic systems and specifically includes software.

So if you want to learn what is necessary I suggest you download the standard.

ISO 26262 is an automotive functional safety standard which again sets out methods of risk assement and how risk concatenates through an automotive function chain. Again it explicitly mentions software.

How you test software for safety is an enormous topic and too beg to address here.

I would just point out that these standards also expect users to test the tools they use to help them create software - such as compilers - to make sure they do not introduce problems.

 

DrQuine
User Rank
Author
Re: Software safety
DrQuine   7/1/2013 11:00:47 PM
NO RATINGS
An example of the kind of thing that these standards do is that IEC 61508 requires that the software is fully tested at the function level and that all possible branches and paths are taken through the software. This is an important step in that having a system do unexpected things that were never tested may be possible to avoid. This, however, cannot necessarily ensure that every unexpected external event will result in the correct software "decision" and outcome.

Peter Clarke
User Rank
Author
Re: Software safety
Peter Clarke   7/2/2013 3:20:09 AM
NO RATINGS
@DrQuine

 

Thanks for chiming in.

 

Your point about software testing not being exhaustive against all possibilities and timings of external events is important.

 

Formal methods were once thought to be the way to "prove" hardware was correct but idea of formally provable hardware lost momentum when it was realized that formally proving sofware-plus-hardware-plus-interrupts was a much less tractable problem.



Like Us on Facebook
EE Life
Frankenstein's Fix, Teardowns, Sideshows, Design Contests, Reader Content & More
Martin Rowe

Test Tool Finds Ethernet Wiring Errors
Martin Rowe
Post a comment
When my house was renovated several years ago, I had the electrician install network outlets in numerous places, then run the LAN cables to a wiring closet. But he didn't document the ends ...

Martin Rowe

Local Electronics Store Supplies Engineers and Hobbyists
Martin Rowe
5 comments
Rochester, N.Y. — Tucked away in this western New York city known for its optics is Goldcrest Electronics, a local store that's supplied businesses and individuals with electronic ...

Martin Rowe

How to Transform a Technology University (Book Review)
Martin Rowe
1 Comment
The Presiding Genius of the Place by Alison Chisolm. WPI, Worcester, Mass., 234 pp., 2016. Engineers love to discuss, and often criticize, engineering education. They often claim ...

Max Maxfield

Aloha from EEWeb
Max Maxfield
Post a comment
Just a few minutes ago as I pen these words, I posted this blog about this month's Cartoon Punchline Competition over on EEWeb.com.