📘 Lecture 10 — Introduction to CMM
📖 Overview: This lecture introduces the Capability Maturity Model (CMM), its structure, and the five levels of software process maturity. It explains the state of the software industry in 1984, key process areas (KPAs), common features, and institutionalization, then dives deep into Level 2 (Repeatable) and its six KPAs. This matters because CMM provides a proven framework for improving software process capability, reducing project failures, and enhancing quality and predictability.
🗂️ Topics Covered
The lecture covers the software state-of-the-art in 1984, the Software Engineering Institute (SEI), the five levels of software process maturity, maturity levels and key process areas (KPAs), key process area goals, common features, institutionalization, key practices, CMM structure, and a detailed examination of CMM Level 2 (Repeatable) including its six KPAs: Requirements Management, Software Project Planning, Software Project Tracking and Oversight, Software Subcontract Management, Software Quality Assurance, and Software Configuration Management.
📝 Lecture Summary
Software State-of-the-Art in 1984
The lecture begins by describing the chaotic state of software development in 1984. More than half of large software systems were late in excess of 12 months. The average costs of large software systems were more than twice the initial budget. The cancellation rate of large software systems exceeded 35%. The quality and reliability levels of delivered software of all sizes was poor. Software personnel were increasing by more than 10% per year. Software was the largest known business expense which could not be managed.
Software Engineering Institute
The Software Engineering Institute (SEI) is a research facility located in the University of Carnegie Mellon, Pennsylvania. It was primarily funded by the US DoD to explore software issues and topics associated with defense contracts. The US DoD is the largest producer and consumer of software in the world. The SEI developed a Capability Maturity Model (CMM) for software systems and an assessment mechanism.
The Five Levels of Software Process Maturity
The CMM defines five maturity levels: Level 1 Initial (ad hoc processes), Level 2 Repeatable, Level 3 Defined, Level 4 Managed, and Level 5 Optimizing.
Maturity Levels
Maturity levels are well-defined evolutionary plateaus, each a layer in the foundation for subsequent process improvement activities. Each level is a layer in the foundation for continuous process improvement. There are five maturity levels in the CMM. Achieving each level establishes a different component in the software process. Maturity levels are described in terms of 18 key process areas (KPAs).
Key Process Area Goals
Goals summarize the key practices of the key process areas. They are considered important for enhancing process capability for that level of maturity. They can be used to guide organizations and appraisal teams in assessing alternative ways to implement key process areas. Each Key Practice maps to one or more goals.
The CMM Key Process Areas
A Key Process Area (KPA) identifies a cluster of related activities that, when performed collectively, achieve a set of goals considered important for enhancing process capability. KPAs are defined to reside at a single maturity level. They identify the issues that must be addressed to achieve a maturity level. There are 18 KPAs in the CMM.
The lecture provides a table mapping KPAs to maturity levels and process categories (Management, Organizational, Engineering). For example, at Level 2 (Repeatable), KPAs include Requirements Management, Software Project Planning, Software Project Tracking and Oversight, Software Subcontract Management, Software Quality Assurance, and Software Configuration Management.
Common Features
Common features are used to organize the key practices in each key process area. They are attributes that ensure the processes are defined, documented, and understood. Common features are: commitment to perform, ability to perform, activities performed, measurement and analysis, and verifying implementation.
Institutionalization
Institutionalization means the organization outlives those who leave it. The organizational culture must convey the process. It is an indicator of whether the KPA is effective, repeatable, and lasting. The CMM has four common features that focus on institutionalizing the process: commitment to perform, ability to perform, measurement and analysis, and verifying implementation. Activities performed focus on implementing the process.
Commitment to Perform describes the actions the organization must take to ensure that the process is established and will endure. It typically includes policies and leadership.
Ability to Perform describes the preconditions that must exist in the project or organization to implement the software process competently. It typically includes function/tools, resources, delegation, training, and orientation. It describes the roles and procedures necessary to implement a key process area, including establishing plans and procedures, performing the work, tracking it, and taking corrective actions as necessary.
Measurement and Analysis describes the need to measure the process and analyze the measurements. It typically includes examples of the measurements that could be taken to determine the status and effectiveness of the activities performed.
Verifying Implementation describes the steps to ensure that the activities are performed in compliance with the process that has been established. It typically includes reviews and audits by senior management, project management, and SQA.
Key Practices
Key Practices state the fundamental policies, procedures, and activities for a key process area. Policies and procedures make up the infrastructure. They describe "what" is to be done but should not be interpreted as mandating "how". They are organized by common features. There are 316 key practices in the CMM.
CMM Structure
The lecture provides a visual of the CMM structure showing Maturity Levels, Process Capability, Key Process Areas, Goals, Common Features, Key Practices, and Institutionalization.
CMM Level 2: The Repeatable Level
Moving from Level 1 to Level 2: At level 2, a software project management system is in place. The organization sets expectations via policies. At level 2 projects have disciplined processes. Organizations have introduced at least some rigor into project management and technical development tasks. Approaches such as formal cost estimating are noted for project management, and formal requirements gathering are often noted during development. Compared to the initial level, a higher frequency of success and a lower incidence of overruns and cancelled projects can be observed.
KPA’s - Level 2: Requirements Management, Software Project Planning, Software Project Tracking and Oversight, Software Subcontract Management, Software Quality Assurance, Software Configuration Management.
Requirements Management
Purpose: The purpose is to establish a "common understanding" between the customer and organization. It involves documenting and controlling customer requirements, and keeping plans, products, and activities consistent with requirements.
Software Requirements versus Allocated Requirements: The scope of Requirements Management is control of requirements allocated to software. Requirements allocated to software come from systems engineering. Software requirements are derived from requirements allocated to software.
Who is Customer? Customers may be external or internal: systems engineering, marketing, or user. The customer and/or end user identifies the problem that software will address.
Documentation of requirements: The system requirements assigned to software engineering must be documented. Documenting system requirements can be as simple as a memo or as elaborate as a multi-volume specification. If requirements change, the changes must be documented and all resulting necessary changes in other documents must be tracked and verified.
Review of Requirements: The software engineering group ensures that the system requirements allocated to software are documented and controlled. For this, the software engineering group reviews the initial and revised system requirements allocated to software to resolve issues.
Software Project Planning
Purpose: The purpose is to establish reasonable plans for performing the software engineering and managing the project. It involves developing estimates for the work, establishing necessary commitments, and defining the plan to perform the work.
Managing Based on Plan: The plan provides the basis for initiating the software effort and managing the work. Other names for this plan include software development plan, software project management plan, software project plan, and software engineering management plan.
What is a Software Development Plan? A software development plan specifies many or all of the following: the project's chosen software life cycle, list of products to be developed, schedules, estimates for level of effort (number of people), cost, etc., facilities, support tools, and hardware, and project risks.
Packaging the Software Development Plan: There are many ways the software plan can be developed. There may be separate documents entitled: software development plan, software quality assurance plan, software configuration management plan, risk management plan, software test plan, and project training plan.
Plans are based on Estimates: In creating estimates for size, effort, cost, schedule, and/or computer resources, use historical data where available. Document assumptions and estimates. Good estimating depends on the skills and judgment of the estimator.
Meeting Commitments: A commitment is a pact that is freely assumed, visible, and expected to be kept by all parties. Commitment is necessary to achieve plans. Feasible commitments are made when plans are realistic. Commitment is a process.
Software Project Tracking and Oversight
Purpose: To provide adequate visibility into actual progress so that management can take effective actions when the software project's performance deviates significantly from the software plans. It involves tracking and reviewing software accomplishments and results against documented estimates, commitments, and plans, and adjusting plans based on actual accomplishments and results.
Manage to a Plan: Progress must be tracked against plans and specifications, including product size, project effort, cost and schedule, activities, and risks. Mechanisms to track progress against plans include both internal reviews and formal reviews with the customer.
Taking Corrective Action: If and when discrepancies between plans and actual progress occur, a judgment must be made about whether to change the work being done or adjust the plans. This judgment results in corrective action. Archives of original and adjusted plans should be kept.
Software Subcontract Management
Purpose: To select qualified software subcontractors and manage them effectively. It involves selecting a software subcontractor, establishing commitments with the subcontractor, and tracking and reviewing the subcontractor's performance and results.
Prime vs Subcontractor: The prime contractor is the organization responsible for building a system. The prime contractor may contract out part of the work to another contractor, the subcontractor. Performance of the prime contractor may critically depend on performance of the subcontractor.
Planning for the Subcontract: In selecting and managing a subcontractor, prime contractors must perform activities additional to the ordinary project management effort. Specify the work to be performed and the procedures to be followed by the subcontractor (statements of work, requirements, products to be delivered, standards, procedures). Specify criteria for selecting and evaluating subcontractors.
Selecting the Subcontractor: The qualifications of a subcontractor may depend on many factors: process capability, software engineering expertise, application domain knowledge, and strategic business alliances.
Managing a Subcontract: The prime contractor must manage the subcontract. Ensure the subcontractor follows software development plans, standards, and procedures. Monitor software quality assurance by the subcontractor. Monitor software configuration management by the subcontractor.
Software Quality Assurance
Purpose: To provide management with appropriate visibility into the process being used by the software project and the products being built. It involves reviewing and auditing products and activities to ensure they comply with applicable procedures and standards, and providing the software project and other appropriate managers with the results of those reviews and audits.
Provides Visibility to Everyone: The value of SQA is that it provides an independent view of the project's activities, process, and product. SQA serves the "eyes and ears" of the management. Most key process areas contain SQA practices in Verifying Implementation.
Independent vs Objective: Commitment 1.2 (the SQA group has an "independent reporting channel" to senior management) indicates that an independent SQA group is normally expected. Goal 2 of SQA (verify adherence objectively) provides latitude in defining SQA. Without an independent SQA group, can the organization demonstrate objective means of adherence?
Resolving Noncompliance: There are three possible ways for resolving a noncompliance issue: make the product or process satisfy the standard, procedure, or requirement; change the standard or procedure to make it usable; or make an executive decision not to satisfy the standard, procedure, or requirement.
SQA Evolves: Proactive SQA functions as a value-adding member of the project team. SQA starts early in the project. SQA helps to prepare and review procedures, plans, and standards. At higher levels, the CMM provides flexibility for SQA to function proactively to drive improvements in the software process and product.
Software Configuration Management
Purpose: To establish and maintain the integrity of the products of the software projects throughout the project's software life cycle. It involves identifying configuration items/units, systematically controlling changes, and maintaining integrity and traceability of the configuration throughout the life cycle.
Using Baselines: SCM relies on baselining software work products. A baseline is a specification or product that has been formally reviewed and agreed on, serves as the basis for further work, and can be changed only through formal change control procedures.
Controlling Change: SCM provides a stable working environment. Uncontrolled change of work products is a chaotic process. SCM provides a memory of the status of software work products via baselines. When many individuals are working on the same product, SCM coordinates access to and change of the software work products.
Software Product and Software Work Product: A software product is the complete set, or any of the individual items of the set, of computer programs, procedures, associated documentation, and data designated for delivery to a customer or end user. A software work product is any artifact created as part of defining, maintaining, or using a software process, including process descriptions, plans, procedures, computer programs, and associated documents, which may or may not be intended for delivery to a customer or end user.
Baseline Vs Developmental Configuration Management: In baseline CM, baselines for identified software work products are established at predetermined points. In developmental CM, configuration control is exercised by the developers as they perform their work. The SCM KPA can be satisfied using at a minimum baseline configuration management.
Managed and Controlled: Some software work products do not need the formality of configuration management but do need to be placed under some form of version control and change control. This is referred to as "managed and controlled" in the key practices. Managed and controlled is a subset of developmental configuration management.
💡 Why this matters: Understanding the difference between a software product and a software work product is crucial for applying the correct level of configuration control. Knowing that SCM can be satisfied with baseline CM provides a practical starting point for organizations new to process discipline.
⭐ Key Takeaways
The CMM provides a structured five-level evolutionary path for improving software process maturity, from chaotic (Level 1 Initial) to continuously improving (Level 5 Optimizing). Each maturity level comprises Key Process Areas (KPAs) that must be institutionalized through common features: commitment to perform, ability to perform, activities performed, measurement and analysis, and verifying implementation. For the exam, you must know that Level 2 (Repeatable) focuses on project management discipline and has six KPAs: Requirements Management, Software Project Planning, Software Project Tracking and Oversight, Software Subcontract Management, Software Quality Assurance, and Software Configuration Management. Institutionalization ensures processes endure beyond individuals, while key practices describe "what" to do, not "how" to do it. Finally, SQA provides an independent view of project activities, and SCM uses baselines to maintain integrity and control changes throughout the software life cycle.
🧠 Quick Revision Questions
- What were the five key characteristics of the software state-of-the-art in 1984 that motivated the creation of CMM?
- List the five maturity levels of the CMM in order, and state what the key focus of Level 2 (Repeatable) is.
- What are the five common features used to organize key practices in each KPA, and which four focus on institutionalization?
- Explain the difference between a software product and a software work product in the context of Software Configuration Management.
- What are the three possible ways to resolve a noncompliance issue in Software Quality Assurance?
📘 Lecture 11 — CMM Level 3: The Defined Level
📖 Overview: This lecture details the transition from Level 2 (Repeatable) to Level 3 (Defined) of the Capability Maturity Model (CMM). It explains how the focus shifts from individual project management to organizational process standardization and improvement, introducing the seven Key Process Areas (KPAs) required for achieving this maturity level.
🗂️ Topics Covered
The lecture covers the transition from Level 2 to Level 3, the seven KPAs at this level including Organization Process Focus, Organization Process Definition, Training Program, Integrated Software Management, Software Product Engineering, Intergroup Coordination, and Peer Reviews. It explains dedicated process groups like SEPGs, the creation and use of software process assets, tailoring guidelines, and the importance of institutionalized training and peer reviews for defect removal.
📝 Lecture Summary
CMM Level 3: The Defined Level
Moving from Level 2 to Level 3 represents a major shift in emphasis. At Level 2, the focus is on individual projects establishing reliable management processes. At Level 3 (The Defined Level), the emphasis shifts to the organization as a whole. Best practices are gathered across the organization, and processes are tailored as appropriate. The organization supports projects by establishing common processes, common measurements, and training. Organizations at this level have mastered a development process that can lead to successful large systems. Over and above the project management and technical approaches found in Level 2 organizations, Level 3 groups have a well-defined development process that can handle all sizes and kinds of projects.
Key Process Areas (KPAs) - Level 3
The seven KPAs at Level 3 are: Organization Process Focus, Organization Process Definition, Training Program, Integrated Software Management, Software Product Engineering, Intergroup Coordination, and Peer Reviews.
Organization Process Focus
Purpose: To establish the organizational responsibility for software process activities that improve the organization’s overall process capability. It involves developing and maintaining an understanding of the organization’s and projects’ software processes, and coordinating activities to assess, develop, maintain, and improve these processes.
A dedicated group of people, such as a Software Engineering Process Group (SEPG) , is responsible for the organization’s software process activities, including appraisals and software process improvement plans. This group also maintains the organization’s software process database and provides training about the organization’s software process. Other ways of focusing on process include process review boards, quality circles, process steering committees, and software quality assurance. The key responsibilities of SEPGs are to establish process standards, maintain the process database, serve as the focal point for technology transition, provide process education and project consultation, and make periodic assessment and status reports. 💡 Why this matters: Without a dedicated group, process improvement initiatives are sporadic and lack organizational support.
Organization Process Definition
Purpose: To develop and maintain a useable set of software process assets that improve process performance and provide a basis for cumulative and long-term benefits. This involves developing and maintaining the organization’s standard software process and related process assets.
Software process assets are a collection of entities maintained by an organization for use by projects. They include:
- The organization’s standard software process
- Descriptions of approved software life cycles
- Guidelines and criteria for tailoring the standard process
- The organization’s software process database
- A library of software process-related documentation
The process building blocks of the standard software process include elements for activities such as estimating, design, coding, and peer review. These elements are described in terms of standards, procedures, templates, and abstractions. They have an order, interfaces, and interdependencies, sometimes referred to as a software process architecture. The organization may support several software life cycle models like Waterfall, Spiral, Incremental, or Agile processes.
Tailoring guidelines are available to individual projects, specifying what can be tailored out, what cannot, how much a process element can be modified, and what part should be considered for tailoring. The organization’s software process database is a central repository containing actual measurement data from projects and related information. The library of software process-related documentation holds best documents from past projects, including lessons learned and example documents. 🔑 Definition — Organization Process Focus vs. Organization Process Definition: Organization Process Focus focuses on the who (roles and people responsible for process activities), while Organization Process Definition focuses on the what (the actual process assets and standards). These two KPAs are tightly coupled.
Training Program
Purpose: To develop the skills and knowledge of individuals so they can perform their roles effectively and efficiently. It involves identifying the training needs of the organization, projects, and individuals, and developing or procuring training to address those needs.
An organizational training group reviews each project’s training needs and plans, analyzes the skills needed by the organization, prepares and maintains training courses, and maintains training records. Organizational training needs are identified based on the organization’s standard software processes, project needs, organizational culture, and individual needs. A waiver procedure should exist to waive training for individuals who already possess the required skill. At Level 2, the phrase “receive training” is used, which may not be institutionalized. At Level 3 and above, the phrase “receive required training” is used, indicating that institutionalization of training is expected. Training may include formal and informal instruction, including mentors and on-the-job training, but these informal vehicles are frequently abused.
Integrated Software Management
Purpose: To integrate the project’s software engineering and management activities into a coherent, defined software process that is tailored from the organization’s standard software process and related process assets.
At Level 3, each project tailors the organization’s standard software process for its particular needs, including software life cycles, standards, and procedures. The project uses lessons learned and data from previous projects and feeds back appropriate measurement data and documents to the organization. The software development plan is now based on the project’s defined software process. Projects can use and share process data and lessons learned. Integrated Software Management is the evolution of Software Project Planning and Software Project Tracking and Oversight.
Software Product Engineering
Purpose: To consistently perform a well-defined engineering process that integrates all the software engineering activities to produce correct, consistent software products effectively and efficiently.
Development and maintenance activities include software requirement analysis, software design, coding, testing, and integration. Testing activities include unit, integration, system, and acceptance testing. Documentation addresses needs that span the life cycle, including customer documentation (user manuals, training materials, operator manuals) and developer documentation (requirements documents, design documents, test documents, maintenance manuals). Consistency and traceability among documents are critical; inconsistent specifications are not usable.
Intergroup Coordination
Purpose: To establish a means for the software engineering group to participate actively with other engineering groups so that the project is better able to satisfy customer needs effectively and efficiently. It involves disciplined interaction and coordination of the project’s engineering groups with each other to address system-level requirements, objectives, and plans.
Commitments among groups are documented and agreed to by all groups. The software engineering group actively interfaces with groups such as systems engineering, marketing, training, and documentation. Intergroup coordination can be as minimal as a few meetings or as extensive as integrated product teams. It is a first step on the road to concurrent engineering.
Peer Reviews
Purpose: To remove defects from software work products early and efficiently. An important corollary effect is to develop a better understanding of the software work products and of defects that might be prevented.
A peer review is a methodical examination of work products by the producer’s peers to identify defects and areas where changes are needed. It involves identifying products that will undergo a review in the project’s defined software process. Performing peer reviews requires planning and scheduling, training leaders and participants, providing material in advance, assigning specific roles, specifying start/end criteria, using pre-planned checklists, identifying action items to track to closure, and collecting data for process improvement. Alternative methods include Fagan-style inspections, structured walkthroughs, active reviews, and phased inspections. 💡 Why this matters: Catching defects early in the lifecycle is exponentially cheaper than finding them in later stages like testing or deployment.
⭐ Key Takeaways
The transition to CMM Level 3 represents a fundamental organizational shift from project-level management to organization-wide process standardization. The SEPG is the central driver for process improvement, while Organization Process Definition provides the standard assets like the process database and tailoring guidelines that all projects use. Institutionalized training is mandatory, moving from optional to required, and the project’s defined process is tailored from the organization’s standard. Peer reviews are a formal, planned activity for early defect removal, and intergroup coordination ensures all engineering groups work together to meet customer needs.
🧠 Quick Revision Questions
- What is the key difference in focus between CMM Level 2 and Level 3?
- Name the two KPAs that are tightly coupled, and explain what each one focuses on (the "who" vs. the "what").
- What is the primary purpose of a training waiver in the Training Program KPA?
- How does the "software development plan" change when a project reaches Integrated Software Management?
- List three key activities required for performing a proper peer review.
📘 Lecture 12 — CMM Level 4 The Managed Level
📖 Overview: This lecture transitions from CMM Level 3 to Level 4, explaining how organizations move from defined processes to quantitatively managed ones. It covers the two Key Process Areas (KPAs) for Level 4—Quantitative Process Management and Software Quality Management—and introduces Level 5 (Optimizing) with its KPAs. The lecture concludes with a review of CMM themes, measurement progression, and an introduction to ISO 9001:2008 as a quality management system standard.
🗂️ Topics Covered
The lecture begins by explaining the transition from Level 3 to Level 4, where decisions are made based on collected data. It then details the two KPAs of Level 4: Quantitative Process Management (controlling process performance quantitatively) and Software Quality Management (developing quantitative understanding of product quality). The lecture proceeds to Level 5, the Optimizing Level, covering Defect Prevention, Technology Change Management, and Process Change Management. Finally, it ties together the CMM themes, discusses measurement by levels, and introduces ISO 9001:2008, its eight principles, and the process-based quality management system model.
📝 Lecture Summary
CMM Level 4 The Managed Level
At Level 3, measurements have been defined and collected systematically. At Level 4, decisions are made based on the data collected. This involves common measurement and data analysis. Organizations have established a firm quantitative basis for project management and utilize both effective measurements and also effective cost and quality estimates.
KPAs - Level 4
The Key Process Areas for Level 4 are Software Quality Management and Quantitative Process Management.
Quantitative Process Management
The purpose of Quantitative Process Management is to control the process performance of software projects quantitatively. It involves establishing goals for process performance, measuring the performance of the project, analyzing these measurements, and making adjustments to maintain process performance within acceptable limits.
🔑 Definition — Special Causes of Variation: Variations in performance that are not within the normal range of process performance. These are "extraordinary" events outside the bounds of process capability.
A key concern is identifying special causes of variation. Quantitative control in the CMM implies any quantitative or statistically based technique. The words "statistical" and "quantitative" imply data, which reflect facts. Fact-based management results in objective decisions.
Basic statistics show that quantitative techniques need not be sophisticated to be useful; a Pareto analysis for example is very simple. Quantitative techniques do require measurable data, consistent data collection, and defined comparable measurements.
📐 Formula/Concept: Seven Basic Tools of Statistical Process Control:
- Histograms
- Cause and effect diagrams
- Check sheets
- Pareto diagrams
- Run charts
- Control charts
- Scatter diagrams
Taking Corrective Action at Level 4
Quantitative Process Management focuses on the process. Process capability is quantitatively known. When performance falls outside the limits, the organization must identify the reason and take corrective action when appropriate.
Software Quality Management
The purpose is to develop a quantitative understanding of the quality of the project's software products and achieve specific quality goals. It involves defining quality goals for the software products, establishing plans to achieve these goals, and monitoring and adjusting software plans and work products.
Building High-Quality Products
Software Quality Management focuses on the product, not the process. Measurable quality goals for the product are defined. The product is considered ready only when the goals are achieved.
Quality Evolves
At Level 2, the focus of quality is conformance to requirements. By Level 4, there is an emphasis on understanding the needs of the customer, end users, and organization (supplier). Ultimately, the customer determines what quality is or is not. TQM (Total Quality Management) revolves around customer satisfaction.
The CMM Level 5 The Optimizing Level
At Level 4, the process is quantitatively understood. At Level 5, continuous process improvement is a way of life. In immature organizations, no one may be responsible for process improvement. Mature organizations usually have 70 to 80% participation in improvement activities at any point in time—everyone is involved. Organizations are assumed to have mastered the current state-of-the-art of software project management and development.
KPAs - Level 5
The Key Process Areas for Level 5 are Defect Prevention, Technology Change Management, and Process Change Management.
Defect Prevention
The purpose is to identify the cause of defects and prevent them from reoccurring. It involves analyzing defects that were encountered in the past and taking specific actions to prevent the occurrence of these types of defects in the future.
Fixing Problems Before They Happen
The focus is on causal analysis: what in the process permitted the defect to occur and what in the process needs to be corrected to prevent the defect from occurring in the future.
Technology Change Management
The purpose is to identify new technologies (tools, methods, and processes) and track them into the organization in an orderly manner. It involves identifying, selecting, and evaluating new technologies, and incorporating effective technologies into the organization.
Reacting to Innovation
Technology changes occur at all maturity levels. At Level 5, innovation is introduced into the process in a disciplined way and is part of the culture (institutionalized).
Process Change Management
The purpose is to continually improve the software process used in the organization with the intent of improving software quality, increasing productivity, and decreasing the cycle time for product development. It involves defining process improvement goals and systematically identifying, evaluating, and implementing improvements to the organization's standard software process and project-defined software processes.
Change Is a Process
Disciplined change is the key to success. Improvement includes planning, evaluating improvement proposals, planning actions, establishing process improvement teams, conducting pilot programs, and updating procedures and training. Improvements are transferred into everyday practice across the organization.
Level 5 is not the destination
Level 5 is the foundation for building an ever-improving capability. Level 5 organizations continuously improve both incrementally (Kaizen) and through revolutionary changes. Everyone in a Level 5 organization is involved in improvement.
Tying It All Together
Themes in the CMM include continuous improvement, defined/documented/used processes, commitment by senior management, stable, measured, controlled, and evolving processes, and team work.
Measurement by Levels:
- Measurement is haphazard, but investigation may yield cost and effort data.
- Projects collect management data (costs, effort, size, schedule, quality).
- Consistent definitions exist across projects; management and quality data are collected organization-wide.
- Data analysis is based on the principles of statistical process control; actual measurements are compared to expected values of mean and variance.
- Continuous improvement is based on business objectives and cost-benefit analysis.
How is improvement achieved? Know where you are, know where you want to go, assign resources and responsibilities, and try progress.
Keys to Improvements: Senior management commitment, organizational consensus on important issues, belief that improvement is possible, and an action-oriented framework for improvement.
Key Adjectives: The CMM is not exhaustive; it focuses on the major leverage points: key process areas and key practices.
What does a good software organization look like? Processes are defined, documented, and used; management plans, monitors, and communicates; roles and responsibilities are clear; product and processes are measured; quality, cost, and schedule are predictable; technology is planned and used effectively; and continuous improvement is a way of life.
ISO 9001:2008
The lecture now discusses the efforts of ISO in improving quality, focusing on the quality management system. The adoption of a quality management system should be a strategic decision of an organization. The design and implementation of an organization's quality management system is influenced by its organizational environment, changes in that environment, risks, varying needs, objectives, products, processes, size, and structure.
🔑 Definition — Process Approach: The application of a system of processes within an organization, together with the identification and interactions of these processes, and their management to produce the desired outcome. An advantage is the ongoing control over the linkage between individual processes.
This International Standard promotes the adoption of a process approach to enhance customer satisfaction by meeting customer requirements.
Eight Principles of Management:
- Customer focus
- Leadership
- Involvement of people
- Process approach
- System approach
- Continual improvement
- Factual approach
- Mutually beneficial supplier relationship
Quality Management System Requirements, Categories:
- QMS - Requirements: General and Documentation (Quality manual, Control of documents and records)
- QMS: Management Responsibility: Management commitment, Customer focus, Quality policy, Planning, Responsibility/authority/communication, Management review
- QMS: Resource Management: Provision of resources, Human resources, Infrastructure, Work environment
- QMS: Product Realization: Planning, Customer-related processes, Design/development, Purchasing, Production/service provision, Control of monitoring/measuring equipment
- QMS: Measurement, Analysis and Improvement: Monitoring/measurement, Control of nonconforming product, Analysis of data, Improvement
The lecture presents a model of a process-based quality management system, which illustrates that customers play a significant role in defining requirements as inputs. Monitoring of customer satisfaction requires the evaluation of information relating to customer perception as to whether the organization has met the customer requirements.
💡 Why this matters: This lecture bridges the gap between having defined processes (Level 3) and using quantitative data to manage and improve them (Levels 4 and 5), which is the core of organizational maturity. The introduction of ISO 9001 shows a parallel, globally recognized framework for quality management.
⭐ Key Takeaways
A student must remember that Level 4 (Managed) is about using statistical and quantitative techniques to control both the process and the product, with KPAs being Quantitative Process Management and Software Quality Management. Level 5 (Optimizing) is about continuous, data-driven improvement through Defect Prevention, Technology Change Management, and Process Change Management. The measurement progression from Level 1 (haphazard) to Level 5 (business-objective-driven) is a critical framework. Finally, the ISO 9001:2008 standard provides a process-based quality management system with eight management principles and five major requirement categories (QMS, Management Responsibility, Resource Management, Product Realization, Measurement/Analysis/Improvement).
🧠 Quick Revision Questions
- What is the fundamental difference in decision-making between CMM Level 3 and Level 4?
- Name the two Key Process Areas (KPAs) for CMM Level 4 and state whether each one focuses primarily on the process or the product.
- What does the concept of a "Special Cause of Variation" mean in the context of Quantitative Process Management?
- List the three Key Process Areas (KPAs) for CMM Level 5 (the Optimizing Level) and briefly describe the goal of each.
- Name three of the eight principles of management promoted by ISO 9001:2008.
📘 Lecture 13 — Introduction to CMMI
📖 Overview: This lecture introduces the Capability Maturity Model Integration (CMMI), explaining what it is and is not. It clarifies the distinctions between a process model, a process, a process description, a procedure, and an appraisal. The lecture covers the history of CMMI, its purpose in integrating systems and software disciplines, and its two key representations: staged and continuous.
🗂️ Topics Covered
The lecture begins by defining CMMI and distinguishing it from processes, procedures, and appraisals. It then covers the short history of CMMI, the problems with having many separate models, and how CMMI bridges the systems/software divide. The core of the lecture compares the staged and continuous representations of the model, their advantages, and the overall structure and benefits of using CMMI for process improvement.
📝 Lecture Summary
What is CMMI?
CMMI (Capability Maturity Model Integration) is a process model, not a process itself. It is a merger of process improvement models for systems engineering, software engineering, hardware engineering, and integrated teams. It provides a common vocabulary and clarifies how these areas interrelate. CMMI is a collection of best practices from highly functioning organizations, designed to help an organization improve its processes by describing what activities should be done, but not how to do them. It can be directly copied to serve as an organization's processes.
What is a Process?
A process is what you actually do in an organization. It is the documented set of activities or steps you perform to accomplish work. For a process to be real, performed consistently, and improved, it must be documented. Having undocumented processes and believing they are used consistently is unrealistic.
What is a Process Description?
A process description is a documented expression of a set of activities to achieve a given purpose. It documents the steps of the process (what you do when performing a task). Closely related are procedures, which provide step-by-step instructions on how to perform those steps.
What is an Appraisal?
An appraisal is a way to evaluate an organization’s processes and procedures. It assesses how they were implemented, to what extent they are followed, and how well they map to CMMI practices. The standard method for this is SCAMPI (Standard CMMI Appraisal Method for Process Improvement), which is a set of appraisal methods differing in intent and rigor. SCAMPI can be used for internal improvement, supplier selection, process monitoring, and contract awards.
Short History of CMMI
The CMM (Capability Maturity Model) was initially successful for improving software processes. This success led to the creation of similar models for other disciplines like systems engineering, software acquisition, and security. This proliferation of models (Software CMM, System Engineering CMM, etc.) caused confusion due to different structures, formats, and terminology. CMMI was created to rescue this situation by integrating systems and software disciplines into one process improvement framework, providing a structure for introducing new disciplines as they arise.
Comparing Model Representations: Staged vs. Continuous
CMMI provides two representations because of its heritage from different source models (Software CMM, SECM, IPD-CMM).
- Staged Representation: Uses predefined sets of process areas to define an improvement path. This path is described by maturity levels, which are well-defined evolutionary plateaus toward achieving improved organizational processes. It provides a roadmap for implementing groups of process areas in a specific sequence.
- Continuous Representation: Allows an organization to select a specific process area and improve it. It uses capability levels to characterize improvement relative to an individual process area. This offers maximum flexibility to focus on process areas that align with specific business goals.
Process Area Capability and Organizational Maturity
These are similar concepts. Process area capability deals with a set of processes relating to a single process area. Organizational maturity pertains to a set of process areas across the entire organization. A key rule to remember is that a model shows what to do, not how to do it or who does it.
🔑 Definition — CMMI: A process model that integrates multiple disciplines and provides a collection of best practices for process improvement. 🔑 Definition — Process: What an organization actually does, which must be documented to be real and consistent. 🔑 Definition — Appraisal: An evaluation of an organization's processes and their conformance to a reference model like CMMI.
CMMI Model Structure
The CMMI model has a specific structure. It includes:
- Maturity Levels (staged) or Capability Levels (continuous)
- Process Areas
- Goals (Generic and Specific)
- Practices (Generic and Specific)
💡 Why this matters: This structure provides a common, organized framework for improvement, allowing organizations to assess their current state and plan a path forward using a consistent set of components.
Benefits of CMMI
CMMI best practices enable organizations to:
- More explicitly link management and engineering activities to business objectives.
- Expand the scope of and visibility into the product lifecycle.
- Incorporate lessons learned from areas like measurement, risk management, and supplier management.
- Implement more robust high-maturity practices.
- Address additional critical organizational functions.
CMMI serves as a collection of best practices, a framework for organizing and prioritizing activities, and a means to align process improvement objectives with business objectives. It supports the coordination of multi-disciplined activities.
⭐ Key Takeaways
CMMI is a process model, not a process, and it integrates best practices from multiple disciplines. The two main representations are the staged approach, which provides a predefined roadmap via maturity levels, and the continuous approach, which offers flexibility to focus on specific process areas via capability levels. A process description documents the steps (what to do), while a procedure explains how to perform them. An appraisal like SCAMPI evaluates how well an organization’s actual processes align with the CMMI model. The primary benefits of CMMI include linking activities to business objectives and providing a framework to coordinate multi-disciplined activities.
🧠 Quick Revision Questions
- What is the fundamental difference between a CMMI model and an organization's process?
- Name the standard appraisal method used in the CMMI world and list one of its uses.
- What is the primary advantage of the staged representation over the continuous representation?
- In the CMMI model structure, what are the two types of Goals and the two types of Practices?
- How does CMMI help to bridge the traditional "divide" between systems engineering and software engineering disciplines?