Static analysis tool satisfies EN 50128 requirements

Author: Marc Brown, BP Business Development, GrammaTech

Source-code compliance
The EN 50128 standard is very clear on using good programming techniques such as modularity, components, structure, and object-oriented programming. It also requires the use of design and coding standards, and language subsets such as MISRA C. In fact, these coding standards are mandatory for higher safety-integrity levels SIL 3 and 4. Static analysis tools such as GrammaTech CodeSonar are very good for enforcing coding standards, whether commonly-used standards such as MISRA C or customised versions specific to your application.

Static analysis
The EN 50128 standard is specific about the use of static analysis tools 'using a customisable set of Coding Standards, Control Flow and Data Flow Analysis Rules' and is highly recommend for SIL 1 to 4. Interestingly, the EN 50128 said: 'Use the inter-procedural Control Flow Analysis module to find variables in use before being initialized, buffer overflows, resource leaks etc.' As this is a highly recommended practice, it’s clear that static analysis is an important part of the safety critical development toolkit.

Satisfying EN50128 requirements 
The following table illustrates how specific EN 50128 requirements are met with a static analysis tool such as CodeSonar. In many cases the techniques/practices are highly recommended, if not mandatory, at the most critical levels. 

Legend: R = recommended, HR = highly recommended, M = mandatory

Supporting certification
An important part of satisfying the requirements for EN 50128 is not just compliance but documentation to support proof of compliance. Automated software tools, including static analysis, provide reporting that supports the certification effort, and with the additional benefits of risk mitigation and developer time savings, the use of automated tools means quicker time-to-market and development dollars saved.

Certified tools
GrammaTech CodeSonar is an EN 50128 certified tool, which means that an independent certification body, TÜV SÜD Saar GmbH in this case, has analysed the functionality of the tool and its development process and certified that it satisfies the requirements to be used in developing safety-critical software. Why is this important? Tools that are used in the development of safety-critical software must be documented and their results analysed. Tools that are not certified require further scrutiny from the certification bodies, possibly increasing workload and risk on the development team.

Static analysis tools have an important role to play in safety-critical software development. The EN 50128 standard for railway software systems is clear in its requirements and highly recommends static analysis for any system SIL 1 or above. Supporting the certification process with certified tools reduces risk, costs, and time.