--- title: "CMMI levels and the top two levels" subject: "Software Engineering" chapter: 9 key: "semester_5/software_engineering:cmmi-levels" source: https://www.bctengineer.com/q/semester_5/software_engineering/cmmi-levels site: BCT Engineering --- # CMMI levels and the top two levels Software Engineering · Chapter 9: Quality management - Asked in: 2069 Chaitra, 7 marks - Video: [What is CMMI | CMMI Five Maturity Levels | Capability Maturity Model Integration Explained](https://www.youtube.com/watch?v=SCkn25PJYt4) — LearnEveryone - Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14 - Page: https://www.bctengineer.com/q/semester_5/software_engineering/cmmi-levels - Whole chapter: https://www.bctengineer.com/md/semester_5/software_engineering/chapter-9 ## Question What are the different characteristics of the systems at the different levels of Capability Maturity Model Integration (CMMI)? Explain the two top levels of integration models and relate how well these models are effective in managing their software processes. ## Short answer CMMI staged representation defines five levels: Initial (ad hoc), Managed (planned and controlled), Defined (standard process), Quantitatively Managed (statistical control), and Optimizing (continuous improvement). Level 4 sets quantitative objectives and uses control charts for predictable performance. Level 5 analyzes variation causes and drives incremental innovation. These levels yield reliable estimates and fewer defects but demand significant measurement investment and suit large, stable organizations. ## Answer **Capability Maturity Model Integration (CMMI)**, from the SEI, is the successor to CMM. It integrates software, systems engineering and other disciplines into one process improvement model. In its **staged representation**, an organization is rated at one of five **maturity levels**. #### Characteristics at each level | Level | Name | Characteristics | |---|---|---| | 1 | Initial | Ad hoc and chaotic; success depends on individuals; often over budget and late | | 2 | Managed | Projects are planned, monitored and controlled; requirements and configurations managed | | 3 | Defined | Organization-wide standard process, tailored by each project; proactive | | 4 | Quantitatively Managed | Process and quality measured and controlled with statistical techniques | | 5 | Optimizing | Continuous improvement based on quantitative understanding of causes of variation | Brief notes: - **Level 1:** no stable environment; the organization may work well in a crisis but cannot repeat success. - **Level 2:** process areas include requirements management, project planning, project monitoring and control, measurement and analysis, process and product quality assurance, and configuration management. - **Level 3:** process areas include requirements development, technical solution, verification, validation, organizational process definition, organizational training and risk management. (In the **continuous representation**, each process area is instead rated at a capability level: 0 Incomplete to 3 Defined in CMMI v1.3, or 0 Incomplete to 5 Optimizing in earlier versions.) #### The two top levels **Level 4: Quantitatively Managed** - The organization sets **quantitative objectives** for quality and process performance (for example, defect density below 0.5 per KLOC, schedule variance within 5%). - Process performance is measured and controlled using statistical and other quantitative techniques (control charts, baselines). - Process areas: **Organizational Process Performance** and **Quantitative Project Management**. - Difference from level 3: performance becomes **predictable**, not just defined. **Level 5: Optimizing** - The organization **continuously improves** its processes through incremental and innovative changes in process and technology. - Common causes of variation are analysed and removed, and improvements are measured against quantitative objectives. - Process areas: **Causal Analysis and Resolution** and **Organizational Performance Management** (called Organizational Innovation and Deployment in earlier versions). #### How effective these levels are in managing software processes - **Predictability:** level 4 organizations can estimate cost, schedule and quality with narrow error ranges, so commitments to customers are reliable. - **Early detection:** statistical control shows when a process goes outside its normal limits, so action is taken before the project fails. - **Fewer defects:** level 5 removes root causes of defects, so the same errors do not repeat across projects. - **Controlled change:** new tools and methods are piloted and measured before being adopted, which lowers risk. - **Limitations:** reaching these levels needs a large investment in measurement, data collection and trained staff. They are most effective for large, stable organizations with many similar projects; for small or very innovative teams the overhead may be greater than the benefit. Overall, levels 4 and 5 change process management from "following a defined process" to "managing it by data and improving it continuously", which gives the most mature and effective control of software processes. ## Check yourself The answer's key points as multiple-choice questions, with the correct option and why. 1. What is Level 2 called in CMMI staged representation? A. Repeatable B. Managed C. Defined D. Quantitatively Managed Answer: B. CMMI names are Initial, Managed, Defined, Quantitatively Managed, Optimizing. (Key point: CMMI staged levels) 2. What distinguishes CMMI Level 4 from Level 3? A. The process is merely written down B. Process performance is controlled with statistical techniques and becomes predictable C. No measurement is done D. Projects are ad hoc Answer: B. Level 4 sets quantitative objectives and uses statistical control, making performance predictable, not only defined. (Key point: Level 4 meaning) 3. Which process area belongs to CMMI Level 5? A. Causal Analysis and Resolution B. Requirements Management C. Organizational Process Performance D. Risk Management Answer: A. Level 5 has Causal Analysis and Resolution and Organizational Performance Management; Organizational Process Performance is Level 4. (Key point: Level 5 process areas) 4. What is a limitation of levels 4 and 5? A. They give less predictability B. They increase defects C. They cannot be measured D. They need large investment in measurement and trained staff, so suit large stable organizations Answer: D. Overhead may exceed benefit for small or very innovative teams. (Key point: Limitations of top levels) ## Related in Software Engineering - [Short note: Capability Maturity Model](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Acmm-note) — Software Engineering, chapter 9 - [Top-down integration problems; regression testing](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Atop-down-integration-regression) — Software Engineering, chapter 8 - [Software reliability and reliability models](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Areliability-models) — Software Engineering, chapter 9, asked 2× - [Software characteristics and software crisis](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Acharacteristics-and-crisis) — Software Engineering, chapter 1 ## Related in other subjects - [Compare software models; propose a fourth model](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Asw-models-compare-fourth) — Instrumentation II, chapter 9 - [Software process models and effort estimation](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Asw-process-models) — Instrumentation II, chapter 9, asked 2× - [Project management maturity model](https://www.bctengineer.com/question.md?key=semester_7%2Fict_project_management%3Apm-maturity-model) — ICT Project Management, chapter 10 - [Shortcomings of software development models](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Asw-model-shortcomings) — Instrumentation II, chapter 9