Pinned topic Software Analyzer question - Info on rules
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Is it possible to find out more information on each of the code review rule in Software Analyzer? It's great that it has all these rules. However, I want to find out more about the reasoning behind each of the rule. Is there any documentation on the reasoning behind each of the code review rules?
Updated on 2009-07-15T18:14:16Z at 2009-07-15T18:14:16Z by CodeAgent
ScottN 2700017J5V20 Posts
Re: Software Analyzer question - Info on rules2009-07-15T15:16:09ZThis is the accepted answer. This is the accepted answer.The best way to gain the information on the rules is by downloading a trial version and looking at the rule categories for identifying what the rules actually look for. We do have documentation in several areas that might help. Both at developer works:
And at the InfoCenter
CodeAgent 110000CKGR2 Posts
Re: Software Analyzer question - Info on rules2009-07-15T18:14:16ZThis is the accepted answer. This is the accepted answer.
- ScottN 2700017J5V
Thanks for the info. Actually we have RSA and Software Analyzer licenses already. I have the code review rule list. What our team is looking for is the rationalization and recommendations behind each of the code review rule for two main reasons: (1) educational (2) so we can enforce the rules better.
When a developer asks "why?" we want to talk about the reasons, instead of just "because IBM Software Analyzer says so." That doesn't make us look very good :-). Also, when you tell somebody to not do something, it's better if you are prepared to answer the question "what should I do instead"? (The quick fix feature does some of this already but not for all rules).
We can certainly do our own research to come up with the reasons and recommendations for all of the rules... but I am trying to see if this info is already available somewhere that I overlooked.
If this info is not available, it's probably something that IBM should consider adding into the next version.