Mobilise your data to drive predictable verification
Verification is a data-heavy problem and therefore verification engineers need to be data analysts, though they may not realise it. Verification is also a compute-heavy process that suffers from multiple completeness dilemmas. Engineering teams need to take many judged decisions around the question of “are we done yet?”. The consequences of getting this wrong can be costly. A leading measure of product quality is the volume of impactful bug escapes and how they impact the end user. This in turn leads to re-work costs, reputational costs and potentially missed sales costs when products are late to market, or teams are consumed with rework and product support when they should be focused on developing the next product.
