Software erosion protection for automotive embedded software


About TRW

With a turnover of 16.2 billion US dollars in 2011, TRW Automotive is one of the world’s leading suppliers to the automotive industry. The company, with its headquarters in Livonia (Michigan, USA), has a global presence through its subsidiaries in 26 countries and employs approximately 60,000 people worldwide. TRW Automotive’s product portfolio includes integrated vehicle control and driver assist systems, braking systems, steering systems, suspension systems, occupant safety systems (seat belts and airbags), electronics, engine components, fastening systems and aftermarket replacement parts and services.

TRW uses the Axivion Suite to protect the UML-based architecture of its electric parking brake (EPB) and the applications based on it against
erosion. This enables consistent and high development speeds to be achieved in the field of safety-critical control devices with unchanged high
levels of quality.

Why Axivion?

Axivion enusres high levels of software quality for safety-critical control devices according to e.g. ISO 26262

Axivion allows maintaining an increasing number of customer- and model-specific variants

Axivion Static Code Analysis includes checks for MISRA C:2004, MISRA C:2012, MISRA C++:2008 and MISRA C/C++:2023

The seamless integration into daily business reduces the workload for developers

Improved collaboration between architects and developers enhances development efficiency

Axivion allows for better reusability of sub-components in several variants

The Axivion Suite helps us implement our architectural concepts flawlessly. The seamless integration into our UML tool chain went without a hitch and it has made our everyday work easier.

Our innovations are increasingly dependent on software. At the same time, the customer and market requirements are changing faster and faster, and the number of different versions is increasing. This calls for fast response times and the Axivion Suite helps us significantly in this respect.

TRW Automotive GmbH

The Challenge

The electric parking brake (EPB) from TRW has proved very successful in the market and is being used in more and more vehicle models. Today, the specific customer requirements and the necessary flexibility are mainly achieved and ensured by software. The growing customer base and the ever-increasing number of customer- and model-specific variants is therefore a major challenge for software development. For the OEM, perceptions of quality and flexibility are influenced directly by software development at TRW. Development speeds and adherence to deadlines for new variants are critical for TRW’s success.

Software development based on ISO 26262 also demands high standards for the components and associated documentation regarding the quality, which has to be just as high. These include, in addition to requirements for the software architecture and its documentation, the establishment of and compliance with coding guidelines such as MISRA-C.

TRW-EPB systematically relies on the implementation of an UML-based architecture when developing its electric parking brake (EPB). The major challenge here lies in keeping the UML models and the implementation continuously synchronised. Manual checking is not an option because of the large number of projects and variants.

The Solution

The existing tool chain was extended to include the Axivion Suite, whose XMI interface is tailored to the popular CASE tools. The architecture of the UML models is now checked during the development phase itself. As a result, specific change requests for improving the quality are automatically triggered on an ongoing basis.

As soon as the implemented components differ from the models, the software developers receive warning messages. In most cases, developers can quickly resolve the discrepancy themselves. Because the solution was easy to integrate into daily business and the individual developers could be included, it has made the architects’ job easier, as they only have to intervene when changes to the architecture are actually required.

In a further step, the coding guidelines were revised with the assistance of Axivion and these are now likewise automatically checked during the development phase using the Axivion Suite.

The Success

The constant checking of the architecture specifications and modelling rules has made the entire development team more aware of architectural issues. The importance of the architecture and the architects in the project has grown and been generally accepted.

Collaboration between architects and developers has been greatly improved and has become much smoother. Day-to-day tasks involve resolving discrepancies, sometimes in the implementation and sometimes in the architecture. Work is concentrated on finding the optimal solution in each individual case. As a result, not only are the requirements met in full, but lessons can also be learnt in the area of architectural design, thereby allowing overall architectures to be improved more and more. Hence it has been possible to establish new architectures so that – for example – parts of the software are easier to integrate into third-party control units, as is increasingly being stipulated by OEMs.

The perfect interaction and intermeshing of the UML models and the component implementations also enhanced the ability to reuse certain sub-components in several variants. The automated checking of the coding guidelines in the background reduces the manual workload, increases acceptance among the developers and is more conducive to learning, since there is immediate feedback.

Need more information?


Request a meeting with one of our experts to find out how Axivion can help you ensure the high quality of your software code.


Contact us