Currently, there are a lot of approaches that organizations can use for software measurement. Some of which can be traced back over a century ago when a rich body of literature in statistics and quantitative methods were conceived. Tackling various standards, models, courses, and guidebooks is such a very daunting task. But then again, it is a good thing that Capability Maturity Model or CMM came in to the picture as this approach in itself contains a set of practices that spans both process improvement and software measurement. In fact, its successor, which is the Capability Maturity Model Integration (CMMI) has measurement and analysis process areas developed through a collaborative and coordinated effort of key people who work in developing standards on both software measurement and process assessment.
Indeed, the measurement and analysis process are great additions to CMMI, making its scope much wider and more explicit than the previous versions of CMM such as CMM for Software or SW-CMM. These two areas of CMMI support all process areas by providing practices that guide organizations and projects in aligning their measurement objectives and needs using an approach that will yield objective results. In line with this, the measurement and analysis practices are organized under two specific goals. These are:
(a) aligning measurement activities with identified information objectives and needs and (b) providing data analyses and results that address those objectives and needs.
These goals can be achieved by successfully performing specific practices that are associated with the main goal of establishing a more coherent plan for measurement and analysis. Indeed, the measurement and analysis process areas of CMMI provide a central focus that describes good management practice.