1 / 9

Capability Maturity Model (CMM)

Capability Maturity Model (CMM). Purpose: To assess and help improve process in software development organizations . Capability maturity levels: Level 1: Initial Worst Level 2: Repeatable Level 3: Defined Level 4: Managed Level 5: Optimizing Best. CMM Levels [1]. Initial

lamond
Download Presentation

Capability Maturity Model (CMM)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Capability Maturity Model (CMM) • Purpose: • To assess and help improve process in software development organizations. • Capability maturity levels: • Level 1: Initial Worst • Level 2: Repeatable • Level 3: Defined • Level 4: Managed • Level 5: Optimizing Best CS 406 Fall 2001 CMM

  2. CMM Levels [1] Initial The software process is characterized as ad hoc, and occasionally even as chaotic. Few processed are defined, and success depends on individual effort. Lacks: Reasonable process. CS 406 Fall 2001 CMM

  3. CMM Levels [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. Lacks: Complete process. CS 406 Fall 2001 CMM

  4. CMM Levels [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. Lacks: Predictable outcomes. CS 406 Fall 2001 CMM

  5. CMM Levels [4] Managed Detailed measures of the software process and product quality are collected. Both the software process and products are quantitatively understood and controlled. Lacks: Mechanism for process improvement. CS 406 Fall 2001 CMM

  6. CMM Levels [4] Optimized Continuous process improvement is enabled by quantitative feedback from the process and from piloting innovative ideas and technologies. CS 406 Fall 2001 CMM

  7. Key Process Areas [1] Optimizing Defect prevention Technology change management Process change management Managed: Quantitative process management Software quality management CS 406 Fall 2001 CMM

  8. Key Process Areas [2] Defined Organization process focus Training programs Integrated software management Peer reviews Repeatable Requirements management Software project planning Software quality assurance Software configuration management CS 406 Fall 2001 CMM

  9. CMM Documents ? http://www.sei.cmu.edu/cmm/cmms/cmms.html CS 406 Fall 2001 CMM

More Related