Timing Verification & Optimization Blog

The impending crash of automotive software: will ISO 26262 stop it?

Submitted by rapita on 19 January, 2012 - 13:56

A recent article we saw on electronic recalls reads like a Who’s Who of automotive manufacturers struggling to cope with the complexity of electronic systems and paying the price in higher costs and damaged reputations. Will the introduction of ISO 26262 put the brakes on this growing trend or can we expect more of the same?

The Safety Record article* starts with a list of global automotive brand names which it says have recalled models because of problems in complex electronic systems. The companies are:

News from the Certification Together International Conference in Toulouse

Submitted by rapita on 13 December, 2011 - 11:28

I've recently come back to the office from a whirlwind European tour that included a few days at the Certification Together International Conference in Toulouse. We're pleased that Aeroconseil and Certification Together have been able to continue this conference series.

Attendance was similar to last year, around 300 attendees represented 90 organisations (companies and universities) across three days of presentations and workshops. For us, the important buzz was:

4 key benefits of structural coverage for DO-178B systems

Submitted by rapita on 10 November, 2011 - 09:24

Sometimes the value of performing structural coverage (AKA code coverage) is questioned. When it’s performed as an end in itself, this might be true, but when it’s used to show the effectiveness of requirements-based testing, there are some really strong benefits.

DO-178C: The Next Avionics Safety Standard tutorial at the SIGAda conference

Submitted by rapita on 10 November, 2011 - 08:37

Andrew Coombes and Zoe Stephenson of Rapita Systems are in Denver to exhibit at and attend the ACM SIGAda Annual International Conference. Here are Andrew’s thoughts on a tutorial given by Ben Brosgol of AdaCore.

Eliminating timing variability: DRAM refresh times

Submitted by rapita on 8 September, 2011 - 12:23

If you're interested in getting accurate timing measurements of your software, you need to eliminate sources of variation to the software timing wherever possible.

Sources of variability include:

Pages