Automatic independent verification of autocode

D-Risq - computer icon
Reduces the opportunity for error
Automatic verification avoids unit test costs
Simple compliance to standards
Speeds up development

Benefit 1

Reduces the opportunity for error

Benefit 2

Requirements are verifiable

Benefit 3

Simple compliance
to standards

Benefit 4

Automatic checks for consistency

clawz® in practice

CLawZ achieves this through a few steps focussed on verifiability and conformance to standards.  Firstly, CLawZ ensures that the Simulink/Stateflow design conforms to the Design Standard for the subset of Simulink/Stateflow.  Once this automatic check is complete, it is then possible to use an off-the-shelf autocoder to produce code which is then automatically checked for compliance to the Coding Standard.  This Coding Standard is a subset of C that is an implementation of MISRA-C.   The sub-set is called C-♭ and has a set of independently proven formal semantics for use in programme proof.

D-RisQ has designed CLawZ in a user friendly way so that should the proof fail, it will show exactly where in the code the issue lies and align it with the specific area in the design that has the issue.  CLawZ also provides the evidence to support certification to meet the demands of regulated industries.

D-risq - CLawZ image coding
d-risq - Creating Solutions image

CLawZ in the D-RisQ tool chain

When CLawZ® is used in conjunction with D-RisQ’s Kapture and Modelworks tools, the chain of evidence proves that the source code correctly, completely and accurately implements the software requirements.  Indeed, the Design Standard for Modelworks is the same as the Design Standard for CLawZ.  This frees time for the software engineers to concentrate on optimising the operation of the software.  Because the code generation and verification are automatic, it means the focus is where it should be, on the requirements and then on the design. D-RisQ is using CLawZ on various projects, notably for highly assured decision making for autonomous vehicles in air, maritime and sub-surface as well as in nuclear decommissioning.

The ‘glueware’

In order to make the application code run, other software is needed in order to build the run-time.  This non-application code or ‘glueware’ such as libraries and drivers, is typically off-the-shelf or hand coded by the developer.  The checker for the compliance to the C-♭ subset is available for use as a stand-alone tool for this type of code.  The advantages being that all the code, application and non-application can be in accordance with this very useful, deterministic subset of C.  The coding standard for C-♭, which has an abstract and concrete syntax as well as formal semantics produced and verified by D-RisQ, is available on request.

D-risq - CLawZ image coding

Want to work with us on CLawZ®? Contact us today to find out more

Get in touch
D-Risq - logo