Reengineering the software capability maturity model (CMM)

摘要

The Software Capability Maturity Model (CMM) is basically structured into 5 capability levels (initial, repeatable, defined, managed, optimizing) and 18 subordinate key process areas (KPAs) that are mapped into the three Process Categories of Management, Organizational and Engineering. Although this structure relates positively to building increasing levels of software capability, at least two reasons suggest a potential need to consider reengineering the software CMM: (1) it has not been clearly demonstrated that the stated KPAs are the most important areas of capability (i.e., there are no process areas that can be construed to be more important than at least one of them), and (2) if there are other KPAs that are more significant, then greater benefits are likely to be accrued by assuring appropriate levels of capability in the new areas. This issue can also be viewed in the context of the following two questions: (1) does an achieved CMM level of capability assure that the software system will be provided "faster, cheaper and/or better"?, and (2) do the key process areas represent specific responses to critical and chronic problems we have in the software arena? A concluding suggestion is that possible new problem-driven key process areas may have a greater likelihood (compared to some of the existing KPAs) of improving how we develop software.