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 FTPOnline.com. 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.