Software Development Management (CMM) Classification

From: http://hi.baidu.com/izzie_ou/blog/item/d9e016072c809bf9ab645783.html

CMM Classification

The CMM software development process tries to control the software development with a standardized process that has been at risk for decades and become an industry similar to the traditional industrial production process.

CMM Concept

One of the main concepts of CMM is to strengthen process control, believing that as long as the development process is executed in accordance with the prescribed actions, the quality and progress risks of software development can be greatly reduced. The main means of process quality control is inspection.

The second concept of CMM is to guide new software development projects based on empirical data. CMM defines a series of indicators that monitor whether the software development process is standardized, such as software productivity, inspection defect density, and legacy defect density, and summarizes some experience data from the same industry. When implementing real projects, use these empirical data to guide the development process and try to drop key quality indicators of development into the empirical data range. At the same time, further analysis and summary are carried out to revise the quality objectives to guide subsequent new projects. By gradually summarizing and correcting projects, we can finally get a set of quality objectives that suit our own needs.

The third concept of CMM is also essentially based on the traditional waterfall software development model.

 

Many models have emerged in CMM, covering various specialized fields. Among them, the famous models include system engineering, software engineering, software procurement, integrated product, and process development. Cmme (Capability Maturity Model Integration) is used to merge three models into one framework. Like other CMM models, CMMS provides guidance for process improvement, rather than process description. The actual process used by the Organization depends on a number of factors, including the application field-organizational framework and scale. Cmme adds many verified methods to the architecture to help the Organization evaluate maturity-the capabilities of a software process, and establish improvement priorities and implement improvements.

CMM classification:

Initial level:Software processes are unordered, sometimes even chaotic, and there is almost no definition of the process. Success depends on personal efforts. Management is reactive.

Repeatable Level:Establishes a basic project management process to track costs, progress, and features. The necessary process discipline has been developed to repeat the successful experiences of similar application projects earlier.

Defined Level:The software management engineering processes have been documented and standardized and integrated into the Organization's standard software processes. All projects use approved and tailored standard software processes to develop and maintain software. Production of software products is visible throughout the software process.

Quantitative management level:Analyze detailed measurement data of software processes and product quality, and have a quantitative understanding and control of software processes and products. Management has an objective basis for making conclusions, and management can predict performance within a quantitative range.

Optimized Management Level:Quantitative feedback of the process and advanced new ideas and new technologies promote continuous improvement of the process.

 

CmmeProcess domain:

CmmeTotal5Levels,25Process domains,Each level is composed of several process regions: No1The level is the initial level,

No Cheng Yu; no2Level: managed level,7Process domain;3Level: defined level,14Process domain;4Level: Quantified Management level,2Process domain;5Level: continuous optimization management level,2Process domains, such:

Each level is divided into process domains, special goals and special practices, general goals, general practices and common features. The common features are divided into implementation commitments, implementation capabilities, Guidance implementation and verification implementation, as shown in:

Each level has several process domains, which form a Software Process Capability together. Each process domain has some special and general goals, which are achieved through corresponding special practices and general practices. When all the special and general practices of a process domain are implemented as required, the target of the process domain can be achieved