Using Static Analysis for Embedded Software Optimization

A recent article by Nick McNamara mentions how static code analysis is useful for embedded software optimization:

"The ESO approach is based around four identifiable and measurable phases: analysis, development, test and maintenance. Firstly, the code base is analysed using any number of tools and techniques to understand worst-case execution time behaviour, or performance of static source-code analysis.

A typical embedded system may contain up to a million lines of source code, or even more. Checking this huge volume of code by hand is clearly not a practical option. Static analysis tries to identify code sequences that might result in buffer overflows, resource leaks, or many other reliability and security problems. Source code analysers do an excellent job at locating a significant class of defects that are not detected by compilers during standard builds and often go undetected during run-time testing or typical field operation. "

Read the complete Reducing costs with embedded software optimization for more on how static code analysis adds value in this context.

Static Analysis in Policy-Driven Development

In an article introducing Parasoft Concerto -- a new software development management tool that facilitates end-to-end SLDC process visibility and control to ensure that quality software can be produced consistently & efficiently -- SearchSoftwareQuality.com explains how static code analysis operates in the context of policy-driven development.

They explain that Parasoft Concerto takes a requirement, wraps it with a policy and drives it through the infrastructure. When it's completed, Concerto checks that it met policy expectations. The key is being able to to passively monitor and be unobtrusive to a developer's work; Concerto nudges them each time their actions don't align with policy expectations.

For example, static code analysis identifies an error and the developer tries to mark the requirement as complete. With policy-driven task management, the developer would be notified that there is still an error that needs to be remediated.

You can read the complete article at SearchSoftwareQuality.com.

Static Analysis Symposium

The Sixteenth International Static Analysis Symposium (SAS 2009), to be held in Los Angeles August 9-11, is designed to present theoretical, practical, and application advances in the area of static analysis. Get more details at the Static Analysis Symposium site.