Digital Intelligence & Forensics
Measurement & Analysis
Performance & Dependability
Process & Performance Improvement
Security & Survivability
NEWS AT SEI
This article was originally published in News at SEI on: September 1, 1998
The Software Engineering Institute (SEI) is a federally funded Research and Development Center with the mission to accelerate the most effective technology and practice of modern software engineering. The SEI is funded primarily by the Department of Defense (DoD) but also accepts work from other government organizations as well as the private sector via Cooperative Research and Development Agreements.
The centerpiece product of the SEI has been the Software Capability Maturity Model (CMM) released in 1991. This model has contributed to widespread success in assisting organizations in improving their efficiency in developing quality software products. The success of the Software (SW) CMM spawned other CMMs that address a wide range of subjects.
A CMM provides an organization a conceptual framework within which specific processes, e.g., configuration management and quality, can be optimized to efficiently improve the capability of organizations.
A CMM provides state-of-the-art practices to
By focusing on specific processes, an organization can best leverage the resources for their improvement activities while rallying the organization around specific goals. A CMM can be a road map showing an organization how it can systematically move to more mature levels of performance and do it in more effective and efficient ways. After an objective assessment, an organization can set its goals for increasing the capability of its processes. To the DoD, this translates into more affordable products and services for our war fighters. CMMs can include processes that span the entire lifecycle. Starting with requirements management, they can span the breadth of product development, ensuring quality, lean production concepts, and support to the field. Each individual process includes elements that provide basic practices as well as additional practices that add incremental benefits and maturity.
When these processes are sufficiently matured, the organization increases its performance or maturity. Subsequent to the success of the SW-CMM, other CMMs were developed with SEI support. These CMMs included the Systems Engineering CMM and the Integrated Product Development (IPD) CMM. It became apparent in the development of these and other models that they all contained common processes, e.g., configuration management, quality, and requirements management, supporting the various functional disciplines, software engineering, and systems engineering. Improvements in these common processes could benefit other disciplines. Further, it became apparent that process improvement resources applied to one functional discipline, e.g., software engineering, could be beneficial to another functional discipline. The common elements used in a software CMM appraisal could be used for a systems engineering appraisal, and there would be no need to redo the appraisal of common elements. In addition, improvement efforts based on unique CMMs could result in suboptimization, confusion, and potentially unnecessary expenditure of process improvement resources.
Acquisition reform in the DoD created a significant paradigm shift away from a “how-to” mentality approach to an approach centered on Statements of Objectives and Performance-Based Requirements. The earlier capability models and standards were clearly used in the context of meeting contract requirements. There were even brief attempts to use them as selection criteria or as compliance benchmarks rather than frameworks to identify and define characteristics of good practices that facilitate process improvement. Remember the Requests for Proposals that required an SW-CMM Level 2 or above to propose?
Although DoD Directive 5000 directs we select capable suppliers, it does not direct how it should be determined or set arbitrary levels. DoD has learned over time two important things about maturity levels:
One of the top-priority projects in the SEI is integration of the CMM products for use in single or multiple functional disciplines. Industry and government along with the SEI now have enough experience in the various functional disciplines to build this framework upon which all present and future CMMs can be based. This will greatly enhance the efforts of CMM users and protect the resources already invested.
Organizations can use their previous CMM process improvement work and tailor their future efforts to their unique organization. The initial common framework effort will be based on the SW-CMM, the SE-CMM, and the IPD-CMM. Other functional disciplines may be added later. To efficiently use the government funds allocated to CMMs, further work on CMMs that are not common framework compliant has been halted. The work accomplished to date in Software CMM, Version 2.0 and the IPD CMM have been included in the initial CMM Integration (CMMI) baseline.
In building these CMMI products, the needs of industry and government partners must be understood and met. We have had extensive participation in our reviews of the CMMI requirements, and broad collaborative efforts are underway developing the products. We are depending on the functional discipline experts from industry and government to assist in building the products.
In summary, the CMMI project requires a broad collaborative effort to ensure that the best practices are included and process improvement resources are optimized. Industry along with government and the SEI are participating on a team to build the CMMI products. Since many organizations have already made considerable investments in CMM-oriented process improvement efforts, it is important that the products of this project efficiently integrate into these efforts, and that resources are not wasted on a new approach.
For more information
Please tell us what you
think with this short
(< 5 minute) survey.