The Capability Maturity Model(CMM)

                                                                                                                                  -Sudhakar Anugu
The Capability Maturity Model(CMM):- is Software frame work and describes the principles and practices underlying software process maturity and is intended to help software organizations
improve the maturity of their software processes in terms of an evolutionary path from ad hoc, chaotic processes to mature, disciplined software processes. The CMM is organized into five maturity 5levels with 18 key processing areas(KPA) and goals:


Key processing areas(KPA):

Each maturity level is composed of key processed areas , each KPA identifies a cluster realted activities , When performed collectively achive  aset of goals concider important for establishing process capability at maturity level

Goals:

The goals of a key process area summarize the states that must exist for that key process area to have been implemented in an effective and lasting way. The extent to which the goals have been accomplished is an indicator of how much capability the organization has established at that maturity level. The goals signify the scope, boundaries, and intent of each key process area.


1) Initial:-
The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined,
and success depends on individual effort and heroics.

No KPAs


2) Repeatable:-
Basic project management processes are established to track cost, schedule, and functionality. The

necessary process discipline is in place to repeat earlier successes on projects with similar applications.

1. Software Configuration Management
2. Software Quality assurance
3. Software Sub contract management
4. Software Project Tracking and over sight
5. Software Project Planning
6. Requirement management


3) Defined:-
The software process for both management and engineering activities is documented, standardized, and integrated into a standard software process
for the organization. All projects use an approved, tailored version of the organization's standard software process for developing and maintaining software.

1. Peer reviews
2. Intergroup coordination
3. Software product engineering
4. Integrated software management
5. Training programme
6. Organization process defination
7. Organization process focus


4) Managed:-
 Detailed measures of the software process and product quality are collected. Both the software process and products are quantitatively understood and controlled.

1. Software Quality management
2. Quantitative process management



5) Optimizing:-
 Continuous process improvement is enabled by quantitative feedback from the process and from piloting innovative ideas and technologies.


1. Process change management
2. Technology change management
3. Defect prevention


Diference between ISO and CMM Levels:


International Organization for Standardization(ISO):-

           is the world's largest developer of standards. Although ISO's principal activity is the development of technical standards, ISO standards also have important economic and social repercussions. ISO standards make a positive difference, not just to engineers and manufacturers for whom they solve basic problems in production and distribution, but to society as a whole.

    The International Standards which ISO develops are very useful. They are useful to industrial and business organizations of all types, to governments and other regulatory bodies, to trade officials, to conformity assessment professionals, to suppliers and customers of products and services in both public and private sectors, and, ultimately, to people in general in their roles as consumers and end users.

Capability Maturity Mode(CMM):-

        The Capability Maturity Model for Software (CMM) is a framework that describes the key elements of an effective software process. There are CMMs for non software processes as well, such as Business Process Management (BPM).

        The CMM describes an evolutionary improvement path from an ad hoc, immature process to a mature, disciplined process. The CMM covers practices for planning, engineering, and managing software development and maintenance. When followed, these key practices improve the ability of organizations to meet goals for cost, schedule, functionality, and product quality. The CMM establishes a yardstick against which it is possible to judge, in a repeatable way, the maturity of an organization's software process and compare it to the state of the practice of the industry. The CMM can also be used by an organization to plan improvements to its software process. It also reflects the needs of individuals performing software process, improvement, software process assessments, or software capability evaluations; is documented; and is publicly available.