A new generation of static source code analysis tools has very recently become
available for the analysis of software code bases for bugs and other defects. These tools
work without actually running the programs that are built from the software that is under
analysis. Faults can be found early in the development process, so as to improve software quality, as well as save developers time. Such tools can cover the execution paths through a very large code base in a fully automated way, and identify complex defects including bugs involving interactions among multiple procedures.
Great article—it provides a great overview of how static analysis benefits embedded development. I regret missing the actual presentation at ESC. Once readers of your article have decided to take the plunge and start implementing static analysis, a nice follow up resource would be the product-agnostic Static Analysis Best Practices Guide produced by Parasoft (the company I work for). You can find it here http://alm.parasoft.com/parasoft-tv-best-practices-of-static-analysis-in-sdlc/
D. Kalinsky Associates offers a number of intensive courses for embedded software developers and designers of real-time systems, ranging from introductory training on the fundamentals of... Read More
Technical Paper
0
1
Download to Print
Add to bookmarks
1 comment
write a commentParasoft_Mitchell Posted Jul 26, 2012
Great article—it provides a great overview of how static analysis benefits embedded development. I regret missing the actual presentation at ESC. Once readers of your article have decided to take the plunge and start implementing static analysis, a nice follow up resource would be the product-agnostic Static Analysis Best Practices Guide produced by Parasoft (the company I work for). You can find it here http://alm.parasoft.com/parasoft-tv-best-practices-of-static-analysis-in-sdlc/
reply