This is a guest posting by Jim Holmes
In an earlier article, we discussed five code metrics that can help you and your organization better test your software. This article focuses on static analysis tools themselves, and how to implement them in your environment. You’ll also see how such tools can help you begin to address larger technical debt and overall code health quality issues.
This is a companion discussion topic for the original entry at http://feedproxy.google.com/~r/gurock/~3/k3-XdcrMWps/