Req management
Project planning
Project tracking and oversight
Software quality assurance
S/w configuration management
Measurement and analysis
Sub contract management
Training
Organization process focus
Organization process developement
Peer reviews
Inter group coordination
Quantitative Project management
S/W product engineering
Integrated software management
S/W Quality management
Defect prevention
Technology change mgmt
Proces change mgmt

CMM(compactability maturity module),it has Five levels
initial- Level 1
repeated- Level 2
Defined - Level 3
Managed - Level 4
Optimized- Level 5

Capability Maturity Model (CMM):

An organization may be assessed by an (Software Engineering
Institute) SEI-Authorized Lead Appraiser, and will then be
able to claim that they have been assessed as CMM level X,
where X is from 1 to 5. 

The SEI maintains a list of organizations assessed for CMM
since 2006.

There are five levels defined along the continuum of the
CMM, and, according to the SEI: "Predictability,
effectiveness, and control of an organization's software
processes are believed to improve as the organization moves
up these five levels.

1.Initial (chaotic, ad hoc, individual heroics) - the
starting point for use of a new process.

2.Repeatable - the process is able to be used repeatedly,
with roughly repeatable outcomes.

3.Defined - the process is defined/confirmed as a standard
business process, and decomposed to levels 0, 1 and 2 (the
latter being Work Instructions).

4.Managed - the process is managed according to the metrics
described in the Defined stage.

5.Optimized - process management includes deliberate process
optimization/improvement.

At maturity level 5, processes are concerned with addressing
statistical common causes of process variation and changing
the process (for example, to shift the mean of the process
performance) to improve process performance. This would be
done at the same time as maintaining the likelihood of
achieving the established quantitative process-improvement
objectives.

The CMM model proved useful to many organizations, but its
application in software development has sometimes been
problematic. Applying multiple models that are not
integrated within and across an organization could be costly
in terms of training, appraisals, and improvement
activities. The Capability Maturity Model Integration (CMMI)
project was formed to sort out the problem of using multiple
CMMs.

For software development processes, the CMM has been
superseded by Capability Maturity Model Integration (CMMI),
though the CMM continues to be a general theoretical process
capability model used in the public domain.

Capability Maturity Model Integration (CMMI):

CMMI according to the SEI helps "integrate traditionally
separate organizational functions, set process improvement
goals and priorities, provide guidance for quality
processes, and provide a point of reference for appraising
current processes."

CMMI currently addresses three areas of interest:

(1) Product and service development — CMMI for Development
(CMMI-DEV),

(2) Service establishment, management, and delivery — CMMI
for Services (CMMI-SVC), and

(3) Product and service acquisition — CMMI for Acquisition
(CMMI-ACQ).