Proof vs testing in the context of safety standards

During software certification various forms of testing (e.g., unit, integration, regression) are undertaken. These testing processes are very important, but are also generally accepted as expensive, leading to a desire to replace testing with more cost-effective processes, where practicable. This paper is concerned with how such technology substitution can be justified, and presents a template for an argument that can be used to justify substitutions. It also instantiates the argument for a particular proof technology - the CLawZ toolset - and demonstrates how to argue for its safe substitution for testing in this context.