DO-178B

1000 conditions per decision ought to be enough for anybody

RVS versions before 3.8 support up to 30 conditions per decision by default (up to 60 on a 64 bit target), and now versions from 3.8 support up to 1000!
Read More

Automating test generation with AUTOSAC

Find out how automated test generation from SPARK Ada pre and post-conditions can cut the effort needed to run test projects. 
Read More

Merging coverage data from multiple test runs

One of the questions we are asked most frequently is how we merge coverage data from multiple test runs. This seems to be an unnecessary bottleneck that we have solved for many of our customers.
Read More

It’s a bad idea to hide problems from customers – so we don’t

What’s the one thing you’ll almost never hear in your meeting with a software sales representative? An admission that the software you may be thinking of buying has bugs in it.
Read More

Presenting a safety case

Our blogs typically concentrate on technical details which will help with the detailed verification of your software. This blog sets the scene to future blogs describing some of the ways in which our verification tools can be used to help meet safety certification requirements. Verification data provides evidence about the performance and functionality of your code, however, you'll also need to justify why that verification data is relevant, how it fulfills certification requirements, whether it is sufficiently complete, consistent, correct etc..
Read More

Pages