Software Metrics and Software Metrology
Most of the software measures currently proposed to the industry bring few real benefits to either software managers or developers. This book looks at the classical metrology concepts from science and engineering, using them as criteria to propose an approach to analyze the design of current software measures and then design new software measures (illustrated with the design of a software measure that has been adopted as an ISO measurement standard). The book includes several case studies analyzing strengths and weaknesses of some of the software measures most often quoted. It is meant for software quality specialists and process improvement analysts and managers.
Review By: Keith Kautzman
06/13/2011Alain Abran shows some definite expertise in "Software Metrics and Software Metrology"—so much so that this book is not for a newbie looking to learn from scratch or anyone looking for a quick solution to establishing software metrics. While the book defines itself as being well suited for software engineers, managers, and quality analysts, it seems to be most appropriate for researchers or students. The exercises and term assignments provide a nice benefit in an education environment, but most often require additional lecture or readings to be completed.
The book is divided into four parts. The first section, “Key Concepts for the Design of Software Measures,” spends a considerable amount of time discussing many of the concepts of measurement and how they relate to lengths, volumes, etc. It even devotes an entire chapter to numerous diagrams explaining how counting and measuring are not the same. While this section provides a strong base for understanding measurement methods, it is rather long and leaves the reader wondering when the real software measurement topics will start.
Abran then presents brief analysis of some of the most well-known software measurement designs, including some history and each design’s focus of measurement. This analysis is minimal, which is fine for the purposes of giving a general overview. The book then goes into the details of some of the weaknesses of these measurement designs.
The third section of the book discusses the design of the Common Software Measurement International Consortium (COSMIC) approach to software measurement, also known as ISO 19761. Abran gives an overview of the process used to design COSMIC from prototype to international standardization. He also provides input as to the strengths of COSMIC and feedback from the industry.
Finally, Abran presents some further analysis on the complexities of converting from one software measurement design to another and thoughts on what needs done to improve software measurement practices.
Overall, it is a good book for those passionate about developing or improving software measurement designs.