Jane's Technical Stuff
Archives
May 2002March 2003
May 2003
July 2003
August 2003
June 2005
July 2005
August 2005
December 2005
January 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
July 2008
August 2008
September 2008
October 2008
Wednesday, April 02, 2008
Static Code Analysis Review - our criteria
The criteria we've come up for choosing a Static Code Analysis tool are the following:
Is there anything else we should be thinking about?
Note: We've excluded cost as we're interested in finding the right tool without thinking about budgetary constraints.
- Integration - how well does it integrate with VS2005. Does it claim to integrate with VS2008? What about legacy VS2003 stuff?
- Versions - can it work against a .NET 1 project? Or a .NET 3/3.5 one?
- Ease of use - how easy is it to run an analysis? How easy is it to understand what it wants you to fix? And where the code is?
- Ease of configuration - how easy is it to add a new rule? Or turn one off?
- Issue detection - running it against a specific project, what does it detect? How many potential issues does it spot? How does this compare the other tools?
- Stability - any problems noticed since installing it/using it?
- Extra - what else is there about this tool? Any added bonuses?
Is there anything else we should be thinking about?
Note: We've excluded cost as we're interested in finding the right tool without thinking about budgetary constraints.
Labels: .NET, C#, Development, static code analysis
// posted by Jane @ 12:02 PM 
Comments:
