Value in Static Source Code Analysis

If you're not convinced of the value of static source code analysis, you should read this post (I’m not in denial, I’m in a hurry) by David Falkenstein on his blog at In one of his subsequent posts, I hope he takes a look at the static source code analysis tools in Team System.

Static source code analysis is the best way to ensure quality in software projects; yet it is the one step in the software development lifecycle that is most often left to chance. For the life of me, I cannot figure out why because it is the easiest and most effective method of software testing.


I will continue along this thread over the next three weeks as I investigate existing tools and practices, their usage and importance, and how your development can be improved by simply adding continuous static code analysis to your software development lifecycle.

From: I’m not in denial, I’m in a hurry


Technorati tags: ,
Comments (2)

  1. kcastle says:

    I completely agree with this article. Running code analysis really does help alot. I also tend to think that being able to add new rules to the static code analysis, is what would help most departments/organizations adopt this practice. Is there any documentation on how to customize (add new analysis rules and warnings) the static code analysis tool which ships with VS2005 (which is itself FxCop right?)

  2. kcastle says:


    I recently added a post on my blog regarding Static Code Analysis and Team System. The FxCop blog which ireferenced in the post turned out to be great reference for all of those interested.

Skip to main content