The essence of CMMI (Capability Maturity Model Integration) is part of the software management project. Software process improvement is the core issue of current software management projects. The development of calculations in more than 50 years has enabled people to develop software for high efficiency, high quality and low cost development, and must improve software production process. Model-based process improvement refers to the improvement of process improvements with capacity models to guide process capabilities, and the organization can become more mature.
However, software organizations form a complete and mature software process is not a matter, need to experience a series of maturity. Software organizations must first analyze the difference analysis, and if you are more maturity, then you can decide what improvements you want to take according to your own situation, to more effectively improve your own software process. This puts a objective standard for the assessment of the software process. The Software Engineering Institute of Carnegun University in 1987 was a theoretical model of Sw-CMM (Capability) in 1987, the purpose of helping software organization improves software production processes to explore software products. Quality, shorten the development cycle, improve work efficiency software engineering model and standard specification.
CMMI is an integrated mode that can improve system engineering and software engineering. In October 1997, SEI stopped the study of CMM, and was committed to CMMI to solve the problem of using multiple process improvement models. SEI also announced that CMMI will replace CMM and promulgated CMMI-SE / SW 1.0 release from August 11, 2000. In December 2001, 1.1 version was issued. This time the release marks CMMI officially enabled, and is ready to complete CMM this year. CMMI transition. Speaking of CMMI can not mention CMM.
Cmm
The CMM framework uses five evolving levels to assess the history and status of software production: the initial stage describes the organization that is immature, or is an undefined process, is a chaotic process in the process of unpredictable results; it is repeated After training, it has been defined as a standard consistent software process, which is implemented as a feature in organizational improvement project; the managed level is a predictable software process, which is characterized by improved organizational performance; optimization level is software that can continue to improve The process is characterized by quick reconfiguration, and quantitative, continuous process improvements. The software process implemented in any unit may be mature in a certain aspect, not mature enough on the other hand, but it will inevitably belong to a level in these five levels.
CMM includes two parts "software capability maturity model" and "key process domain" of the ability maturity model. "Software ability maturity model" is mainly to describe the structure of this model, and give the definition of the basic components of the model. The "key process domain" of the ability maturity model "describes the process domain involved in each key process.
Repeatable key process domain: demand management, software project plan, software project tracking and monitoring, software subsidiary management, software quality assurance, software configuration management.
Defined levels of key process domain: The organization-level process focus, organization-level process definition, training outline, integrated software management, software product engineering, group coordination, peer review.
Managed Key Process Area: Quantitative Process Management, Software Quality Management.
Optimization-level critical process domain: defect prevention, technology update management, process change management.
The basic goal of most organizations is to achieve a 3-level maturity. One of the means of assessing the current maturity level of the organization is the software capability assessment (SCE). The SCE determines whether the organization is consistent by evaluating the software process (generally in the form of a policy) and project practice. The process of organizes reflects the work made by real records, and project implementation (specific cropping and interpretation of the process) should prove to be said. Many different organizations now have CMM to assist companies' comprehensive process improvement activities, in addition to affirming their software maturity, more images with across the international market. Now through the CMM5 certified organization reached more than 100.
Cmmi
CMM's success promotes other disciplines to develop similar process improved models, such as system engineering, demand engineering, human resources, integrated product development, software procurement, etc., from CMM, some improvement models, such as: SW-CMM, SE -CMM, IPD-CMM, etc. However, the existence of multiple process improvements in the same organization may cause conflicts and confusion. CMMI is to resolve how to keep coordination between these modes.
The Capacity Maturity Model Integration (CMMI) project advocated by the industry, US Government and Carnegie Mellon University, is committed to helping companies alleviate this dilemma. CMMI provides a single integrated framework for improving a organization's process, the new integrated model framework eliminates the inconsistency of each model, reducing the repetition between the model, increasing transparency and understanding, and establishing an automatic, Extended frame. Therefore, the quality and efficiency of the tissue can be improved. CMMI main concerns are cost effective, clear focus, process concentration and flexibility.
Similar to the original ability maturity model, CMMI also includes the necessary elements of establishing an effective process in different fields, reflecting the universal "best" practices of the industry; professional field coverage software engineering, system engineering, integrated product development and system purchase. In this previous mention, CMMI provides guidance and framework for the process of construction and improvement of enterprises; at the same time, it provides a referred to the company's own process.
Source Model of CMMI: Software Ability Maturity Model 2.0, C Draft; Interim Standard (EIA / IS) 731; Integrated Product Development Capacity Maturity Model (IPD-CMM).
CMMI principle:
1. Emphasize the support of senior managers. The process improvement is often a key, consistent support, is the key to the improvement of the process improvement.
2. Carefully determine the improvement goal, first of all, the correct estimation and definition of the improved goals can be completed and formulated. Select the goals that can be achieved and can see the effectiveness of the organization.
3. Choosing best practices should be based on organizing existing software activities and process wealth, refer to other standard models, and take their essence to their mess, get new practical activity models.
4. Process improvements should be consistent with the organization's business goals, closely combined with development strategies.
CMMI objective:
1. Provide guarantees for the development, distribution and maintenance capabilities of organizational procedures and management products.
2. Help organization objectively evaluate their ability to maturity and process domain capability, and improve the process improvement for process improvement.
CMMI method:
1 Decide which CMMI model level is best suited for the improvement of the organization.
2 The representation of the selection model is a continuous or phased.
3 Decide to organize the knowledge field in the model that needs to be used.
4 Top 6 steps proposed by CMM 6 steps, integrated process improvement is divided into: start integration process improvement, construction integrated improvement platform, integrated traditional process, start a new process, and improve evaluation.
CMMI content
The CMMI content is divided into three levels of "Requirements", "expect" and "providing information" to measure the quality of the model included. The most important thing is the "requirements" level, the basis of model and process improvement. The second level "expectations" play a major role in process improvements, but some cases are not required to appear in a successful organizational model. "The information provided" constitutes the main part of the model, providing useful guidance for process improvement, and in many cases, they further explain the needed components needed. The "Requirements" model component is the target, which represents the final state of the process improvement, which has achieved some level in the implementation of the project and process control. When a target corresponds to a critical process domain, it is called "specific goals"; the corresponding critical process is called "public goals". The entire CMMI model includes 54 specific goals, each of which corresponds to one to four specific targets. The description of each goal is very simple, and the goal of sufficient understanding is to extend the "expectation" component.
The "expectation" component is a method, which represents practical means and supplementation of the goals. Each method can be mapped to a goal, and when a method is the only thing is "specific method"; it can be applied to all targets. The CMMI model includes 186 specific methods, each target, two to seven methods corresponds to.
CMMI includes 10 "information provided": purpose, summarizing and summarizing a specific goal of key process domain; introducing instructions, introducing features of key process domains, nature, and actual methods and impact; reference, key process domain The pointing is by reference; the name, the key process area is expressed; method and target relationship, the middle method of the key process is mapped to the target relationship table; the comment, the information source of other model components of the key process area; Typical Work Products Set, definition of work products generated when implementing methods in critical process domains; sub-methods, decomposition and detailed description of method activities; subject expansion, CMMI corresponding disciplines are independent, here there is provided a corresponding subject scope; Description, a detailed description of utility application practices in key process areas.
CMMI provides two stages and continuous two representations, but both representations are logically equivalent. Our familiar SW-CMM software capability mature model is a stage model, and the SE-CMM system engineering model is a continuous model, and the IPD-CMM integrated product development model combines two phased and continuous characteristics.
Phase method represents the model as a series of "maturity level" stages, each stage has a group of KPa points out where an organization should focus on improving its organization, and each KPA is described in a way to meet its goals. It is achieved by satisfying the goals of all KPAs in a particular maturity level.
The continuous model does not have a distracting stage like a phased stage. The method in the KPA of the model is the external form of KPA and can be applied to all KAPs to improve the process by implementing a common method. It does not specifically point out the goal, but emphasizes the method. The organization can properly crop the continuous model according to its own situation and determined KPA as improved goals.
The difference between the two indications is used for each capability and maturity level description process. Although the mechanisms described may vary, two representations are used as needed and desired by using common goals and methods. Elements have reached the same improvement purpose.
============================================================================================================================================================================================================= ==========================================================00 is SW-CMM and SE-CMM. The main difference between CMMI and SW-CMM is to cover many fields; to include four below areas so far:
1. Software Engineering (SW-CMM)
The object of software engineering is the development of software systems, requiring software development, operation, maintenance activities systematic, institutionalizing, and quantifying.
2. System Engineering (SE-CMM)
The object of the system engineering is the development of a full system, which may include the software may not include software. The core of system engineering is to convert customers's needs, expectations, and constraints into product solutions, and provide full support for the implementation of the solution.
3. Integrated products and process development (IPPD-CMM)
The development of integrated products and process refers to a systematic process to better meet customer needs, expects and requirements through all relevant personnel in the product life cycle. If a project or enterprise selects an IPPD process, you need to select all the Practices related to IPPD in the model.
4. Purchasing (SS-CMM)
The content of the purchase is applicable to projects that the supplier's behavior to the project's success or not to function. The main contents include: identifying and evaluating the potential source of products, determining the target supplier of products that requires purchases, monitoring and analyzing the implementation of suppliers, evaluating the work products provided by suppliers, and appropriate adjustments to supply protocols and supply relationships.
In the above modules, companies can choose software engineering, or system engineering, and they can also choose. The integrated product and process development and procurement are mainly used in conjunction with software engineering and system engineering. For example, pure software companies can choose the content of software engineering in CMMI; equipment manufacturing companies can choose system engineering and procurement; integrated companies can choose software engineering, system engineering and integrated products and process development. Most of the content in CMMI is applicable to different fields, but there is a significant difference in the implementation, so the model is provided in the model.
CMM's activity-based metrics and waterfall processes have a very close contact based on activities, and more suitable for the waterfall development process. CMMI relative CMM more steps to support iterative development processes and economic motives driving organizations adopt results: development business cases, ideas and prototype regimens; after refining, the baseline structure is included, which is available, and finally the release of live versions. Although CMMI retains activity-based methods, it independently integrates many modern best practices in the software industry, so it has largely dilutes the links between the waterfall ideas.
On the CMMI model, the continuous model has occurred on the basis of the CMM stage mode, which helps an organization and the customer's customers more objectively and comprehensively understand its process maturity. At the same time, the use of continuous models can bring a greater autonomy to an organization when performing process improvement, without having to be in the same way as the CMM. The benefits of this improvement are strong flexibility and objectivity. The weakness is due to lack of guidance, an organization may lack the correct understanding of the dependencies between key process domains, resulting in some process into air pavilion, lacking other processes support. Two expressions (continuous and phases) are not different from the process area they cover, and different approach process areas and the method of judging the maturity (capabilities) level. The CMMI model further enhances the attention of demand than CMM. In CMM, there is only a critical process domain that needs to be managed in demand, that is, emphasizes the management of quality needs, and how to obtain a clear requirement. In the stage of CMMI, a three-level key process domain is called demand development, which proposes how to obtain excellent requirements and methods. The CMMI model has enhanced engineering activities. In CMM, only 3 of the three-level software product projects and peer reviews are closely related to the engineering process, and in CMMI, they will develop, verify, confirm, technical solutions, and product integration. Process activities have been made as a separate key process area, thereby proposing higher requirements and more specific guidance on the project in practice. Risk management also emphasized in CMMI. Unlike the management dispersion of risks in CMM, the CMMI3 level has been made separately in the CMMI3, and a independent key process domain is called risk management.
