



PICASSOS - A Collaborative Project - Updated
In 2017, D-RisQ completed an investigation into the use of our then embryonic techniques on automotive software. At the time, expertise was required to use our only relevant technology called Modelworks®. The project was used to trial analysis techniques in order to reduce the time and cost impact of poor requirements and design in context of the automotive safety standard ISO26262. Since then, we have not only developed Modelworks® and Kapture® but added other capabilities. With the backing of the Mobilise* programme, we have taken the opportunity to revisit the work undertaken within PICASSOS but with our up-to-date tools. The original results were impressive with 60-80% savings in design verification baselined against traditional review and another verification technology (SLDV) as shown in the graphic below.
Project Aim
The original PICASSOS programme only focused on software requirements and design correctness. We now have System Kapture™, so we can define system requirements in structured English. Furthermore, we can assess these system requirements for required behaviours before expending further effort. We also now have Kapture® and can therefore express software requirements in structured English and undertake some automated checks. We have further developed Modelworks® and can undertake significantly more verification of design correctness. We can autocode and, as we now have CLawZ®, we can automatically verify that the code is correct. All tools providing independent proof and evidence to support ISO26262.
The Trial

While the PICASSOS project did not have these artefacts, we were able to extrapolate useful System Requirements and to run some checks. For example, we were able to show that torque application will be inhibited when in all cases when it should be. This is useful as if there was a corner case where this was not true, then development would continue until it may have been spotted later in the life cycle incurring time/cost which would need to be revisited. System Kapture™ encapsulates a ‘requirements standard’ and gives a sound basis for verification activities.
DISCOVER MOREAll of the software requirements for the 6 subsystems were expressed in Kapture® and traced to system requirements and verified. Kapture® encapsulates a ‘requirements standard’ and gives a sound basis for further verification activities.
DISCOVER MORE

The existing designs in Simulink®/Stateflow® were subjected to a ‘design standards check prior to automatic verification using Modelworks®. In order to provide a comparison to the original project, the time taken to undertake this verification was taken; results are below.
DISCOVER MOREThe designs were autocode into a MISRA-C compliant program. This was not part of the original project. The code was automatically checked for compliance to the coding standard (available from D-RisQ) prior to automatic proof using CLawZ®.
DISCOVER MORE



Results
Errors were not seeded in this exercise (we already know we can detect them from our original work) and were detected this time too. It’s also not an exact replication of the study due to the obvious fact that there is only D-RisQ doing this, so side-by-side comparisons were not possible, and we used different/new tools and there are now system requirements as well as code and more verification artefacts. In the original exercise, the savings were consistently 60-80% just for the time taken to verify the design against the requirements and were measured in labour hours.

Now we can check for example TA from the graphic above in around 6 minutes compared to the original effort of 3 hours 25mins...which in itself was already considerably faster than conventional (~7 hours) or other techniques (~8 hours). We also autocoded and verified in less than 20 mins, 15 minutes of which was setting up the autocoder.
Note that all the tools can be used to provide the requisite evidence needed to support claims against ISO26262.
*Mobilise is a grant funded programme run by the Advanced Propulsion Centre and Zenzic
Automatic verification of Executable Object Code using FEVER




Privacy Policy | Terms & Conditions
Drisq Ltd 2024. All rights reserved. Design by Design in the Shires
