Introduction
A key process area (KPA) contains the goals that must be reached in order to improve a software process. A KPA is said to be satisfied when procedures are in place to reach the corresponding goals. A software organization has achieved a specific maturity level once all the corresponding KPAs are satisfied.
|
Key Process Areas-Identify a cluster of related activities that, when performed
collectively, achieve a set of goals considered important for enhancing process
capability. -Defined to reside at a single maturity level. -Identify the issues that must be addressed to achieve a maturity level. |
Following list describes the KPAs of CMM:
| Maturity Level Two | Repeatable |
| Focus | Basic Project Management controls |
KPA |
Purpose |
| Requirements Management | To establish a common understanding between a customer and project team on the customers requirement. |
| Software Project Planning | To establish plans for engineering and managing a project. |
| Software Project Tracking | To establish adequate visibility of and Oversight actual progress. |
| Software Subcontract Management | To select qualified subcontractors and manage them effectively. |
| Software Quality Assurance | To provide appropriate visibility of the process used and the products build. |
| Software Configuration Management | To establish and maintain the integrity of a product throughout its life cycle. |
| Maturity Level Three | Defined |
| Focus | Project and organizational issues. |
KPA |
Purpose |
| Organization Process Focus | To establish an organizational responsibility. |
| Organization Process Definition | To develop and maintain a usable set of organizational process assets. |
| Training Program | To train individuals so they can be effective and efficient. |
| Integrated Software Management | To integrate software engineering and management activities effectively. |
| Software Product Engineering | To ensure a well-defined process that integrates all technical activities |
| Intergroup Coordination | To establish smooth communication between software engineering groups. |
| Peer Reviews | To remove defects early and efficient. |
| Maturity Level Four | Managed |
| Focus | Process and product quality. |
KPA |
Purpose |
| Quantitative Process Management | To
control a projects process performance quantitatively. |
| Software Quality Management | To develop a quantitative understanding of product quality. |
| Maturity Level Five | Optimizing |
| Focus | Continuous and measurable process improvement. |
KPA |
Purpose |
| Defect Prevention | To identify the causes of defects and prevent them from recurring. |
| Technology Change Management | To identify beneficial new technology and transfer them in an orderly manner |
| Process Change Management | To continually improve the process to improve quality, increase productivity, and decrease development time. |