Скачать или смотреть Understanding the MISRA Standard for Embedded Software Compliance

Explore effective methods and tools to achieve `MISRA compliance` in embedded systems, understanding time estimations and recommendations for smoother implementation.
---
This video is based on the question https://stackoverflow.com/q/62946/ asked by the user 'Ilya' ( https://stackoverflow.com/u/6807/ ) and on the answer https://stackoverflow.com/a/63781/ provided by the user 'Darryl Buchanan' ( https://stackoverflow.com/u/8105/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, comments, revision history etc. For example, the original title of the Question was: Misra standard for embedded software

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 2.5' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 3.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the MISRA Standard for Embedded Software Compliance

When working with embedded systems, ensuring code quality and safety is vital. That's where the MISRA standard (Motor Industry Software Reliability Association) comes into play. MISRA provides guidelines for writing robust, high-quality code that minimizes the likelihood of bugs, especially in safety-critical applications. However, transitioning existing code to meet these standards can be daunting. So, how do we navigate this process, and what resources can help with compliance? Let's break it down.

The Challenge: Making Code MISRA Compliant

You may find yourself in a situation where a significant amount of existing embedded code needs to be brought up to MISRA compliance. This often raises two critical questions:

Time Estimation: How long will it take to convert and ensure that the code is MISRA compliant?

Tool Recommendations: Which tools can help automate this process, particularly those that support customizable options for suppressing specific warnings?

The answers to these questions can significantly affect project timelines and the team’s workload.

Estimating Time for Compliance

Estimating the time needed for MISRA compliance can be somewhat tricky, primarily due to varying degrees of "well-written" code. While there’s no one-size-fits-all answer, here are some rough guidelines based on experience:

Learning Tools: Getting familiar with tools like PC-Lint typically takes about 2 to 3 days. This is essential since these tools will form the backbone of your compliance efforts.

Initial Code Assessment: The process of making existing code compliant might require roughly 10 to 25 percent of the time you initially spent writing the code. For instance, if a module took 40 hours to develop, expect to invest between 4 to 10 hours on compliance.

Ongoing Compliance: Maintaining MISRA compliance will add an additional 5 to 10 percent to the ongoing code development time. A significant portion of this adjustment involves changing the existing habits of your developers and incorporating regular code inspections and testing to ensure compliance with the MISRA rules.

Recommended Tools for MISRA Compliance

To effectively manage the compliance process, using the right tools can make a considerable difference. Here are some recommendations:

PC-Lint

Overview: PC-Lint stands out as a powerful static code analysis tool that checks for MISRA compliance and can be tailored to your specifications.

Integration: If you are working with Visual Studio, consider the Visual Lint plug-in from Riverblade, which allows for seamless integration. However, even if you're not using Visual Studio, PC-Lint can be run efficiently through the command line.

Embedded Compilers

MISRA Compliance Features: Many embedded systems compilers now come with built-in features that provide MISRA compliance feedback as part of their compiler warnings. For example, the IAR compiler for Arm7/Arm9 offers an easily configurable MISRA checklist integrated into the compiler setup.

Additional Suggestions for a Smooth Transition

While tools and techniques are vital, fostering a culture of compliance amongst developers is equally essential. Here are some practical steps:

Training Programs: Invest time in training your team on MISRA guidelines and the tools you’ll be using. Regular workshops can keep the knowledge fresh and encourage better coding practices.

Code Reviews: Implement regular code reviews focused on MISRA compliance, which can help quickly identify potential issues and encourage discussion about best practices among team members.

Documentation: Maintain thorough documentation of compliance efforts and decisions. This can serve as both a guide and a reference for future projects an