Konferenzen und Rahmenprogramm
The Practicalities of MISRA Compliance / Why the MISRA Deviation Process is Key to Language Subset Adaptability
There are many static analysis tools available to assess code compliance with MISRA guidelines. But the identification and rectification of violations flagged by a tool represents only one part of the compliance process. Step back from the analysis of violations and it is easy to see bigger questions about the process as a whole. MISRA€™s document €œMISRA Compliance:2016€ receives much less press coverage than the language subsets, but it is invaluable in understanding how the information highlighted by the static analysis tool of choice relates to that bigger picture. This paper will discuss several key points raised by the MISRA compliance document. It will reflect on the necessity of a €œdo it right€ mindset even before the detailed demands of the language subsets are considered. And it will conclude that such a mindset cannot be the exclusive prerogative of the critical systems community, because a system does not have to be critical before there is a need for it to work reliably. On first acquaintance, the MISRA language subsets can appear overbearing with their myriad of rule definitions and explanations. They might also appear impossibly draconian. The very first rule in MISRA C:2012, for example, dictates that €œthe program shall contain no violations of the standard C syntax€, and yet the perfectly justifiable use of compiler extensions is widespread. Closer inspection however reveals a deviation procedure, for those occasions when €œit may be necessary to deviate from the guidelines given in [the standard]€œ. Deviations must be recorded and authorized, provided there is justification to do so €“ as for the compiler extensions. This paper will discuss the principles and mechanism surrounding MISRA C deviations. It will discuss how the deviation procedure is intended to work, and how it prevents the unscrupulous from implementing deviations for mere convenience. And it will conclude that the standard as a whole really can apply to almost any critical system.
--- Datum: 25.02.2020 Uhrzeit: 17:00 - 17:30 Uhr Ort: Conference Counter NCC Ost