Shote note on the Capability Maturity Model (CMM) 5 Levels for Software Process. - MBA Assignment Notes

Shote note on the CMM 5 Levels for Software Process.

Software Engineering Institute (SEI) developed a model, to address the various levels of maturity levels present in an organization called Capability Maturity Model (CMM). SEI used a five point grading scheme to assess the maturity level.

The five levels are as follows -

Level 1: Initial level –

It is to address the initial processes where there is a tendency of one or more processes getting chaotic. Some of the issues are identified and steps are taken to bring in clarity in the initial processes.

Level 2: Repeat level –

Based on the successes of certain processes in the past, processes are reviewed and revised. Some of the processes which are tracked are the process on costing, scheduling and various other related functions.

Level 3: Documentation –

Organizations follow a streamed line of software development activities. These activities are documented procedures developed over years which are used by both the management and development team. Modules developed are integrated into existing organization software processes.

Level 4: Managing the processes -

It is necessary to measure various product features and processes associated with the software process. Measures are taken to collect data from various processes on various parameter of the software and each one is measured. The quantification of all such measures is done and used in the performance evaluation of the process and the product.

Level 5: Optimization –

Continual improvement is one of the major objectives of organization today. It is achieved by means of some predefined characteristics which are expected from the processes. 

 

The measurement methodology can be different for different processes. A quantitative feedback is obtained for various processes and measured. The measurements are made under constraints under which a process is expected to perform. 

 

Hence the measurements have to be optimized measurements. This helps in taking decisions on the improvement of the process on a continual basis.

The SEI has associated key process areas (KPAs) with each of the maturity levels. The KPAs describe those software engineering functions (e.g., software project planning, requirements management) that must be present to satisfy good practice at a particular level.

Each KPA is described by identifying the following characteristics:

•    Goals – the overall objectives that the KPA must achieve.

•    Commitments – requirements (imposed on the organization) that must be met to achieve the goals, or provide proof of intent to comply with the goals. 

•    Abilities – those things that must be in place (organizationally and technically) to enable the organization to meet the commitments.

•    Activities – the specific tasks required to achieve the KPA function. 

•    Methods for monitoring implementation – the manner in which the activities are monitored as they are put into place.

•    Methods for verifying implementation – the manner in which proper practice for the KPA can be verified.