This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Ensuring the Integrity of Embedded Software with Static Code Analysis
May/June 2009 (vol. 26 no. 3)
pp. 96-99
Ben Chelf, Coverity
With embedded software becoming increasingly pervasive and critical to our society, developers must ensure that their software code performs as intended and doesn't fail. Static code analysis is key in controlling code quality even before unit testing. It doesn't replace other verification and validation steps but helps remove certain defect types that otherwise wouldn't be found. This article provides an overview on static code analysis and insight on how to best use it.

1. S. Johnson, Lint: A C Program Checker, tech. report 65, Bell Laboratories, Dec. 1977.
2. C. Ebert and E. Baisch, "Industrial Application of Criticality Predictions in Software Development," Proc. 9th Int'l Symp. Software Reliability Eng. (ISSRE 98), IEEE CS Press, 1998, pp. 80–89.
3. P. Louridas, "Static Code Analysis," IEEE Software, vol. 23, no. 3, July 2006, pp. 58–61.
4. D. Spinellis, "Bug Busters," IEEE Software, vol. 23, no. 2, Mar. 2006, pp. 92–93.
5. C. Ebert and R. Dumke, Software Measurement, Springer, 2007.
6. W.W. Schilling and M. Alam, "Integrate Static Analysis into a Software Development Process," Embedded.com, 2006; www.embedded.com/columns/technicalinsights 193500830.

Index Terms:
static code analysis, verification, code checking, unit test, review, inspection
Citation:
Ben Chelf, Christof Ebert, "Ensuring the Integrity of Embedded Software with Static Code Analysis," IEEE Software, vol. 26, no. 3, pp. 96-99, May-June 2009, doi:10.1109/MS.2009.65
Usage of this product signifies your acceptance of the Terms of Use.