Cmm
Download as PPTX, PDF3 likes630 views
The Capability Maturity Model (CMM) is a framework for judging the maturity of an organization's software processes. It describes five levels of process maturity: Initial, Repeatable, Defined, Managed, and Optimizing. At lower levels, processes are ad hoc or inconsistent. At higher levels, processes are more defined, measured, controlled, and continuously improved. The CMM was developed by the Software Engineering Institute to help organizations improve their software development process.
Cmm
- 1. CAPABILITY MATURITY MODEL BY: DEBASMITA MAJUMDER & NILANJAN CHAKRABORTY
- 2. OUTLINE:- WHAT IS CMM PROCESS MATURITY CONCEPT LEVELS OF CMM SUMMARY OF LEVELS DESCRIPTION PROBLEMS WITH CMM
- 3. What is CMM? CMM: Capability Maturity Model Developed by the Software Engineering Institute of the Carnegie Mellon University Framework that describes the key elements of an effective software process.
- 4. Process Maturity Concepts Software Process set of activities, methods, practices, and transformations that people use to develop and maintain software. Software Process Capability describes the range of expected results that can be achieved by following a software process means of predicting the most likely outcomes to be expected from the next software project the organization undertakes
- 6. Maturity level indicates level of process capability: Initial Repeatable Defined Managed Optimizing
- 8. Summary of levels Level 1 – Initial. Anything at all. Ad-hoc process. Will have some successes, as well as failures and badly missed deadlines. Level 2 – Repeatable. SW processes are defined, documented, practiced, and people are trained in them. Groups across an organization may use different processes. Level 3 – Defined. SW processes are consistent and known across the whole organization. Level 4 – Managed. SW processes and results are measured quantitatively, and processes are evaluated with this data. Level 5 – Optimizing. Continuous process improvement. Experimenting with new methods and technologies. Change processes when find something that works better.
- 9. Level 1: Initial Initial : The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual effort. At this level, frequently have difficulty making commitments that the staff can meet with an orderly process Products developed are often over budget and schedule Wide variations in cost, schedule, functionality and quality targets Capability is a characteristic of the individuals, not of the organization
- 10. LEVEL 2: REPEATABLE Basic process 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. Realistic project commitments based on results observed on previous projects. Software project standards are defined and faithfully followed. Processes may differ between projects. Process is disciplined. earlier successes can be repeated.
- 11. Level 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 an maintaining software.
- 12. LEVEL 4: MANAGED Detailed measures of the software process and product quality are collected. Both the software process and products are quantitatively understood and controlled. Narrowing the variation in process performance to fall within acceptable quantitative bounds. When known limits are exceeded, corrective action can be taken. Quantifiable and predictable.
- 13. Level 5: Optimizing Continuous process improvement is enabled by quantitative feedback from the process and from piloting innovative ideas and technologies. Goal is to prevent the occurrence of defects Data on process effectiveness used for cost benefit analysis of new technologies and proposed process changes
- 14. Problems with CMM •It is a goal, not a method •Being used just as stamp of approval •Doesn’t say anything about software •Doesn’t help in a crisis