Capability Maturity Model Homework Help, Assignment Help, Online Tutor, Tutoring

Submit Assignment

* *

Payment Online Assignment Help

Web Designing

Homework Help

sfsf

Capability Maturity Model

The Capability Maturity Model (CMM) is a methodology used to develop and refine an organization's software development process. The model describes a five-level evolutionary path of increasingly organized and systematically more mature processes. CMM was developed and is promoted by the Software Engineering Institute (SEI), a research and development center sponsored by the U.S. Department of Defense (DoD). SEI was founded in 1984 to address software engineering issues and, in a broad sense, to advance software engineering methodologies. More specifically, SEI was established to optimize the process of developing, acquiring, and maintaining heavily software-reliant systems for the DoD. Because the processes involved are equally applicable to the software industry as a whole, SEI advocates industry-wide adoption of the CMM.

• A bench-mark for measuring the maturity of an organization’s software process

• CMM defines 5 levels of process maturity based on certain Key Process Areas (KPA)

CMM Levels

CMM's Five Maturity Levels of Software Processes

• At the initial level, processes are disorganized, even chaotic. Success is likely to depend on individual efforts, and is not considered to be repeatable, because processes would not be sufficiently defined and documented to allow them to be replicated.

• At the repeatable level, basic project management techniques are established, and successes could be repeated, because the requisite processes would have been made established, defined, and documented.

• At the defined level, an organization has developed its own standard software process through greater attention to documentation, standardization, and integration.

• At the managed level, an organization monitors and controls its own processes through data collection and analysis.

• At the optimizing level, processes are constantly being improved through monitoring feedback from current processes and introducing innovative processes to better serve the organization's particular needs.

Level 5 – Optimizing (< 1%)

-- process change management

-- technology change management

-- defect prevention

Level 4 – Managed   (< 5%)

-- software quality management

-- quantitative process management

Level 3 – Defined      (< 10%)

-- peer reviews

-- intergroup coordination

-- software product engineering

-- integrated software management

-- training program

-- organization process definition

-- organization process focus

Level 2 – Repeatable (~ 15%)

-- software configuration management

-- software quality assurance

-- software project tracking and oversight

-- software project planning

-- requirements management

Level 1 – Initial         (~ 70%)