RapiCover | Rapita Systems

Product Page

Product logo

Does DO-178C require object code structural coverage?

If you are developing software to Level A for DO-178B/C, your code has to undergo extremely rigorous structural coverage analysis for the purposes of certification. This includes examining both source and object code.

Read more about Does DO-178C require object code structural coverage?

What are the overheads of code coverage? Using "Doom" as an example

One question that we are frequently asked is what instrumentation overhead RapiCover introduces. Achieving low overhead instrumentation is recognized by our customers as a key strength of RapiCover. To measure structural code coverage of embedded software, or for that matter any software, code coverage tools like RapiCover use instrumentation (additional code that records what code has been executed).

Read more about What are the overheads of code coverage? Using "Doom" as an example

Code coverage without instrumentation

Follow our progress on collecting coverage results without applying any instrumentation at all.

Read more about Code coverage without instrumentation

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!