Meanings of CMM representatives at different levels

At the initial level, enterprises generally do not have a stable environment for software development and maintenance. When you encounter problems, you often give up the original plan and focus only on programming and testing.

Level 2: repeatable

At this level, policies for managing software projects and measures for implementing these policies have been established. Plans and manages new projects based on past project experience.

Level 3: Definition level

At this level, documents on a specific software engineering and management engineering process facing the entire enterprise's software development and maintenance will be formulated. At the same time, these processes are integrated into a coordinated whole. This is called the standard software process of an enterprise.

Level 4: Quantitative Management

At this level, enterprises establish quantitative quality objectives for products and processes, and add clear and continuous measurements in the process. As an enterprise measurement solution, it is necessary to measure the productivity and quality of important process activities of all projects. Therefore, software products have predictable high quality.

Level 5: (continuous) optimization level

At this level, the entire enterprise will focus on the continuous optimization of the process. Enterprises will take the initiative to identify the weaknesses and strengths of the process to prevent defects. At the same time, we will analyze the effectiveness of relevant processes, analyze the costs and benefits of new technologies, and propose suggestions for modifying the process.

Level 1 CMM: initial level

◆ Features
(1) software processes are characterized by disorder, disorder, and sometimes chaos. There are almost no rules or steps for defining the process.

(2) Over-commitment, a good commitment is often made, for example, "work in an orderly manner by means of software engineering", or a promise to reach a high goal. But in fact there are a series of problems.

(3) give up the original planning process and repeat coding and testing in case of a crisis.

(4) Success depends entirely on individual efforts and outstanding professionals, depending on exceptional management personnel and outstanding and effective software development personnel. The specific performance and achievements depend on or depend on the individual's abilities, their previous experiences, knowledge, and their initiative and positive degree.

(5) capabilities are only personal characteristics, rather than the characteristics of development organizations. Relying on personal qualities or under great pressure; or looking for tips to achieve results. However, once such people leave, the stability of the Organization also disappears.

(6) software processes are uncertain and unpredictable. The software process of the first software organization is often changed during actual work (the process is random ). Such organizations are also developing products, but their results are unstable, unpredictable, and repetitive. That is to say, the plan, budget, function, and product quality of the software are uncertain and unpredictable.

◆ Process
(1) rarely exist or use a stable process

(2) the so-called "process" is often "in this case.

(3) various regulations and rules and regulations are not in coordination or even conflict with each other.

◆ Personnel
(1) Relying on personal efforts and outstanding figures. Once a good person leaves, the project cannot continue.
(2) people work in the same way as "Fire Fighting", that is, they constantly encounter crises and "fire fighting" in the development process ".

◆ Technology
Introducing new technologies is a great risk.

◆ Measurement
Do not collect or analyze data.

◆ Improvement Direction
(1) Establish a project management process, implement standardized management, and ensure the project's commitment.

(2) The primary task is to manage requirements and establish a common understanding between the customer and the software project so that the project truly reflects the customer's requirements.

(3) Establish various software project plans, such as software development plans, software quality assurance plans, Software Configuration Management Plans, software testing plans, risk management plans and process improvement plans.

(4) Conduct software quality assurance activities (SQA ).

Level 2 of CMM: repeatable

◆ Features
(1) A realistic commitment can be made to ensure another success based on the necessary process principles established based on previous experiences in similar projects.

(2) establish basic process management regulations on a project-by-project basis to enhance process capability.

(3) A basic project management process is established to track costs, progress, and functions.

(4) management mainly tracks software expenditures, progress and functions. Identify commitment issues.

(5) Use baseline to mark progress and control integrity.

(6) define the standards of a software project, trust it, and follow it.

(7) establish an effective supply-demand relationship through sub-contracts.

◆ Process
(1) the process of software development and maintenance is relatively stable, but the process is established at the project level.

(2) regular software processes are controlled by an effective engineering management system, and previous successful experiences can be repeated.

(3) ability to identify and correct problems. The commitment is achievable.

◆ Personnel
(1) The success of the project depends on the individual's ability and support from the management.

(2) understand the necessity of management and its commitment to management.

(3) Pay attention to personnel training issues.

◆ Technology
Establish technical support activities and have stable plans.

◆ Measurement
Create a resource plan for each project. Focus on costs, products, and progress. Corresponding management data.

◆ Improvement Direction
(1) No longer develop software processes based on projects, but summarize the successful experiences of various projects to normalize them and classify the experiences into standard software processes across the entire organization. Software Process activities that improve the overall software process capability of the Organization are the responsibility of the software development organization.

(2) determine the entire organization's standard software process, and integrate software engineering and management activities into a well-established software process. This can improve the software process performance across projects and serve as the basis for Software Process tailoring.

(3) Establish a Software Engineering Process team (SEPG) to assess and adjust the software process for a long time to meet the requirements of future software projects.

(4) accumulate data and establish the organization's software process library and software process-related document library.

(5) Strengthen training.

Level 3 of CMM: definite level

◆ Features
(1) management or engineering software processes have been documented and standardized and integrated into the standard software processes of the software development organization.

(2) software process standards are applied to all projects for software preparation and maintenance. Some projects can also tailor the standard software process of the software development organization according to the actual situation.

(3) When engaging in a project, the production process, cost, plan, and function of the product can be controlled, so that the software quality can be controlled.

(4) The software engineering process group (SEPG) is responsible for software activities.

(5) Arrange training plans throughout the organization.

◆ Process
(1) the entire organization adopts comprehensive management and engineering process management. Software engineering and management activities are stable, repetitive, and continuous.

(2) The software process can anticipate and prevent problems, minimizing the impact of risks.

◆ Personnel
(1) work as a project team. Like a comprehensive product team.

(2) Everyone within the organization has an in-depth understanding of the activities and tasks of the defined software process, greatly enhancing the process capability.

(3) carry out training in a planned manner based on the roles of personnel.

◆ Technology
Establish a new evaluation technology based on qualitative analysis.

◆ Measurement
(1) collect usage data throughout the process.

(2) systematically share data throughout the project.

◆ Improvement Direction
(1) Start the quantitative analysis of the software process to achieve the effect of quantitative control of the software project process.

(2) Achieve the software quality goal through software quality management.

CMM Level 4: Management Level

◆ Features
(1) A detailed and specific measurement standard for software processes and product quality has been developed. Both software processes and product quality can be understood and controlled.

(2) the capability of the software organization is foreseeable because the software process is measured and operated by a clear measurement standard. It is self-evident that the quality of software products can be foreseen and controlled.

(3) The Organization's measurement project ensures that all projects measure productivity and quality and act as important software process activities.

(4) provide well-defined and consistent measurement standards to guide software processes and serve as a quantitative basis for evaluating software processes and products.

(5) A software process database has been established within the Development Organization to save the collected data, which can be used for various software processes.

◆ Process
(1) start to quantitatively understand the software process.

(2) The software process changes slightly, generally within the acceptable range.

(3) Foreseeable software process and product quality trends. Once the quality longitude is beyond these standards or is in violation, some methods can be used to correct it to achieve a good goal.

◆ Personnel
Each project has a strong sense of group work. Because everyone understands the relationship between personal roles and organizations, this kind of group consciousness can be produced.

◆ Technology
Constantly evaluate new technologies based on quantitative analysis.

◆ Measurement
(1) Collect and determine data throughout the organization.

(2) Measure standardization.

(3) data is used to quantitatively understand software processes and stabilize software processes.

◆ Improvement Direction
(1) Defect Prevention should not only promptly improve when problems are discovered, but also take specific actions to prevent future occurrence of such defects.

(2) actively manage, identify, select, and evaluate technical changes so that effective new technologies can be implemented in the development organization.

(3) manage process changes, define the purpose of process improvement, and constantly improve the process.

Level 5 CMM: optimization level

◆ Features
(1) the entire organization pays special attention to the continuity, foresight, and enhancement of software process improvement to prevent the occurrence of defects and problems and continuously improve their process processing capabilities.

(2) Strengthen quantitative analysis, and continuously improve the software process by generating quality feedback from processes and absorbing new ideas and new technologies.

(3) Perform cost/profit analysis based on the effect of the software process, learn from the experiences in the successful software process, and summarize the results. Quickly transfer the Best Innovation achievements to the entire Organization, and analyze the failure cases by the software process team to find out the cause.

(4) The organization can identify the deficiencies in the process and make improvements in advance, and inform all organizations of the lessons learned to avoid repeated previous errors.

(5) evaluation of the software process and improvement of the standard software process are all promoted across the organization.

◆ Process
(1) continuously and systematically improve the software process.

(2) understand and eliminate the common root cause of the problem, which can be found in any system: repetitive work due to random changes, resulting in a waste of time. To prevent possible system changes caused by waste of manpower. Eliminate the root cause of "public" inefficiency and prevent waste. Although these problems exist at all levels, this is the focus of the fifth level.

◆ Personnel
(1) the entire organization has a conscious and strong sense of team.

(2) Everyone is committed to improving the process. People do not meet the milestones any more, but strive to reduce the error rate.

◆ Technology
Based on quantitative control and management, We proactively consider new technologies and pursue new technologies in advance. It can realize the innovation of methods and new technologies in software development to prevent errors and continuously improve product quality and productivity.

◆ Measurement
Use data to evaluate and select process improvement.

◆ Improvement Direction
Maintain continuous software process improvement.

CMM Summary: five-layer structure diagram

We can see that at the fifth level, technological and process improvements are carried out in a planned and managed manner as common business activities. Since the Organization is constantly committed to improving the process capabilities, the software development organization's capabilities can be continuously improved. This improvement is not only manifested in the gradual improvement of the existing software process, but does not show the current innovations in the adoption of new technologies and methods.

Draw a diagram: (five-layer structure diagram of CMM)
-----------------
/Optimized/
/(5 )/
-----------------
Bytes
| Continuous improvement process
|
-----------------
/Manageable/
/(4 )/
-----------------
Bytes
| Foreseeable Process
|
-----------------
/Determine the level/
/(3 )/
-----------------
Bytes
| Standard consistency Process
|
-----------------
/Repeatable/
/(2 )/
-----------------
Bytes
| Disciplined process
|
-----------------
/Initial level/
/(1 )/
-----------------

From: http://hi.baidu.com/flora200609/blog/item/411228c77d075ddcd000607c.html