The second part discuss about the learning the fundamentals like OOPs concepts and Design Patterns, writing the clean code and how to approach to remove the bad smells from the code. The third part discuss about the different static code analysis tools as code quality measurement tools. The fourth part discuss about how to organize the quality awareness with in the team. http://jaibeermalik.wordpress.com/2009/04/12/code-quality-learn-measure-and-organize-awareness/ http://jaibeermalik.wordpress.com/2009/04/12/code-quality-learn-oops-desing-patterns-clean-code-and-refactoring/ http://jaibeermalik.wordpress.com/2009/04/12/code-quality-measurement-static-code-analysis-tools/ http://jaibeermalik.wordpress.com/2009/04/12/code-quality-organizing-awareness-with-in-the-team/
- Posted by: Jaibeer Malik
- Posted on: April 14 2009 06:46 EDT
You forgot the SOLID principles. I believe that, when code quality is in question, they come before OOD, OOP or design patterns. If one follows the SOLID principles, then OOP and design patterns will be implemented almost automatically.
In your list of tools you don't mention JHawk - a Java static code analyser that covers a much wider range of code metrics than the open source metrics tool. You can find out more at http://www.virtualmachinery.com/jhawkprod.htm and can download a demo version at http://www.virtualmachinery.com/jhdownload.htm. Virtual Machinery also have a number of whitepapers on Java code metrics at http://www.virtualmachinery.com/jhawkmetrics.htm and at http://www.virtualmachinery.com/sidebars.htm