Continuous Qualification

Keeping Compilers, Libraries and Applications Inside the Safety Envelope

In safety-critical software development, qualification is not a one-time event. Yet in practice, compiler and library qualification is often treated as something that happens once, at the beginning of a project, and is disconnected from future project development. It is then archived as a PDF that everyone hopes will remain valid forever. This approach does not align with the realities of modern software development and internal safety standards, nor with the expectations of functional safety standards, regulators, or auditors. What is needed instead is a new mindset: Continuous Qualification.

In this white paper, BUGSENG and Solid Sands present a new Continuous Qualification system for C and C++ toolchains.
You can download the full paper here on the right.