A biased comparision of static ABAP code analyzers
Recently, I had the chance to talk at sitHH (http://wiki.sdn.sap.com/wiki/display/events/SAP+Inside+Track+Hamburg+2012) about my personal experience with some static ABAP code analysis tools. I also talked about my experience with establishing a process around this kind of tools. If you want to have a detailed look at the slides, you can find them here at SlideShare.net: http://www.slideshare.net/therealtier/static-abap-code-analyzers.
One of the important points is that a tool should be installed at last. First of all, you should establish a working process for code review and after that implement a tool to support the experts in finding violations of 80% of the most prominent basic rules you can check on static ABAP code. The missing 20% will always go undetected by tools and need manual reviews to find them.
Also it is very important to get the tools as close as possible to the developers and have them integrated into the development cycle to ensure code quality. But at the same time you need BI-like views to create transparency for management to give suites the chance to spend time and money on the hotspots of missing code quality in your application. If you have long-time products in maintenance, you will need long-term evaluation to see emerging trends and start the steps to stop code quality degredation.
Looking forward to your comments and discussions.