Coverage
This topic contains questions and answers about the disciplines covered by CMMI models.
Contents:
- Does CMMI cover systems engineering?
- Where is system testing covered in CMMI for Development?
- Can CMMI be used for acquisition management?
- Can CMMI be used for hardware engineering?
- Can CMMI be used in manufacturing organizations?
- Can CMMI be used for electrical and mechanical engineering?
- Does CMMI include customer management processes?
- Can a SCAMPI appraisal cover just software engineering or just systems engineering?
- Will other areas of interest be considered for the CMMI Framework?
- Is the CMMI Framework robust enough to support future models?
Does CMMI cover systems engineering?
Yes. Systems engineering practices are best identified by looking first at the definition of systems engineering in the CMMI model glossary:
The interdisciplinary approach governing the total technical and managerial effort required to transform a set of customer needs, expectations, and constraints into a product solution and support that solution throughout the product's life.
This includes the definition of technical performance measures, the integration of engineering specialties toward the establishment of a product architecture, and the definition of supporting product lifecycle processes that balance cost performance and schedule objectives.
From this definition, you can see that hardware and software design are covered by systems engineering. The systems engineering and software engineering practices in CMMI models significantly overlap. In fact, the model amplifications, which are informative clarifications of practices, are the only differences between how these practices are applied.
With the release of version 1.2, the names of CMMI models have changed from listing the legacy constituent disciplines addressed in a model toward a more comprehensive and integrated approach. Therefore, CMMI-SE/SW/IPPD/SS has become CMMI for Development (CMMI-DEV).
return to top
Where is system testing covered in CMMI for Development?
Examples of system testing are provided in SP 1.1 of the Verification process area and SP 1.1 of the Validation process area. However, system testing is not a term used in CMMI, since the terms "system" and "testing" can be interpreted in many ways.
The term "system" was not used in CMMI because of its multiple interpretations across disciplines. Instead of "system," the term "product" and "product component" were used for consistency and clarity. The terms "verification" or "validation" were used instead of "testing" since (1) testing can be either part of verification or validation, and (2) testing is only one method used for verification or validation.
So, to find information on system testing, look instead for "product verification," "product validation," "product component verification," or "product component validation."
return to topCan CMMI be used for acquisition management?
CMMI for Development covers the acquisition discipline as it relates to product development and maintenance, which includes the use of commercial off-the-shelf (COTS) products and outsourcing.
The CMMI Acquisition Module (CMMI-AM) builds on relevant best practices extracted from the CMMI Framework to define effective and efficient practices for government acquisition organizations. This is a non-appraisable element of the CMMI Product Suite.
CMMI for Acquisition (CMMI-ACQ), a CMMI model designed for acquisition organizations, is planned for release in 2007. An initial draft of the model is now available.
The Software Acquisition Capability Maturity Model (SA-CMM) is a capability maturity model for organizations that acquire solutions such as hardware, software, services, and systems. It is used to appraise an organization's process maturity and help improve its acquisition processes.
return to topCan CMMI be used for hardware engineering?
Yes. CMMI for Development is designed to include hardware engineering as part of product development and maintenance. There are amplifications that specifically address hardware engineering practices. (Look for the words "For Hardware Engineering.") Further, many examples demonstrate that CMMI practices are designed for hardware as well as software and systems engineering.
return to topCan CMMI be used in manufacturing organizations?
Yes, if when improving its organization's processes, a manufacturing organization includes manufacturing functions as part of its process improvement program.
When planning an appraisal of a manufacturing organization, the role of the manufacturing function in the organization determines if that function should be within the scope of a SCAMPI appraisal. The SCAMPI appraisal method permits a wide range of tailoring options, including the organizational scope and model scope of the appraisal. In general, the portions of the organization involved in performing the practices in the model scope must be included.
For example, if the Technical Solution process area is included in the model scope and some of the specific practices within the process area are performed by practitioners that are part of the manufacturing function, then manufacturing should be included in the appraisal.
return to topCan CMMI be used for electrical and mechanical engineering?
Yes. CMMI for Development meets the broader needs of product development by guiding the engineering development of products. These products can be electrical or mechanical. Examples and typical work products often apply to software, hardware, and firmware products.
Organizations applying discipline areas such as electrical and mechanical engineering may wish to supplement CMMI model elements with information that has not been covered but would be helpful in applying the best practices to the organization's environment. For that and similar reasons, CMMI models are available in Microsoft Word format that easily can be tailored.
return to topDoes CMMI include customer management processes?
No, not specifically, but yes by implication. The model's emphasis on relevant stakeholders and on validating [customer] requirements can be seen as confirming the importance of this area as customers are most assuredly relevant stakeholders.
If you think that customer management should be emphasized more in CMMI, submit a change request using the CMMI User Feedback Process described on the SEI Web site at http://www.sei.cmu.edu/cmmi/models/change-requests.html.
return to topCan a SCAMPI appraisal cover just software engineering or just systems engineering?
Yes. CMMI models permit the flexible application of Engineering practices (i.e., those contained in the Requirements Management, Requirements Development, Technical Solution, Product Integration, Verification, and Validation process areas) to software engineering, systems engineering, or other product engineering functions. Each organization selects a CMMI model and the parts of the organization to participate in the process improvement program (i.e., the scope).
The SCAMPI appraisal method can be used to perform discipline-specific appraisals by simply selecting the scope of the appraisal using the "organizational unit" concept and using the appropriate CMMI model. An organizational unit typically has an identifiable senior manager, deploys one or more processes that have a coherent process context, and operates within a coherent set of business objectives. An organizational unit is typically part of a larger organization, although in a small organization, the organizational unit may be the whole organization. Such an appraisal is not termed "CMMI-SE" or "CMMI-SW" as in the past, nor can "SE" or "SW" be appended to the new formal model definition (i.e., CMMI-DEV/SE is not allowed).
As part of every appraisal, an Appraisal Disclosure Statement (ADS) must be completed. This statement must indicate not only the CMMI model used for the appraisal, but also the organizational unit(s) included in the appraisal. This statement clearly communicates the nature of the appraisal, including whether software engineering or systems engineering processes of the organization were appraised.
return to topWill other areas of interest be considered for the CMMI Framework?
The CMMI Framework is designed to accommodate additional areas of interest. These new areas of interest will be added to the CMMI Framework as requested by CMMI users and approved by the CMMI Steering Group.
The process for adding new disciplines is documented in the Concept of Operations (CONOPS) for CMMI. This document is available at http://www.sei.cmu.edu/cmmi/background/conops.html.
return to topIs the CMMI Framework robust enough to support future models?
Yes. The architecture of the CMMI Framework is designed to allow the future addition of other disciplines and the coverage of other areas of interest within CMMI. To apply to multiple areas of interest, the framework groups best practices into what are called "constellations." A constellation is a collection of CMMI components that are used to build models, training materials, and appraisal documents.
Recently, the CMMI model architecture was improved to support multiple constellations and the sharing of best practices among constellations and their member models. Work has begun on two new constellations: one for acquisition (CMMI for Acquisition) and the other for services (CMMI for Services). Although CMMI for Development incorporates the development of services, including the combination of components, consumables, and people intended to meet service requirements, it differs from the planned CMMI for Services (CMMI-SVC) constellation, which largely focuses on the delivery of services. The CMMI models that have been available in the community prior to 2006 are now considered part of the CMMI for Development constellation.
return to topIf you have a question that is not answered within this FAQ, check the CMMI FAQ Main Page or send email to an SEI person at cmmi-comments@sei.cmu.edu. You will receive a response within 48 hours.