Mature evolutionary framework and guidelines-CMM Architecture

I. Framework

SW-CMM provides a step-by-step evolutionary framework for the process capability of software enterprises. There are five steps. Level 1 is actually a starting point. Any enterprise preparing to evolve according to the CMM System will naturally be at this starting point and move towards Level 2 through this starting point. In addition to level 1, each level sets a set of goals. If this set of goals is achieved, it indicates that this level of maturity has been reached and can be moved to the next level. The CMM system does not advocate leapfrog evolution, because from the second level, every low-level implementation is the basis for high-level implementation.

1. Initial Level

Initial software processes are undefined, and project execution is random or even chaotic. Some enterprises may have developed software engineering specifications, but if these specifications fail to cover basic key process requirements and there is no guarantee for implementation of policies, resources, and other aspects, it is still regarded as the initial level.

2. Repeatable

Based on years of experience and lessons learned, it is concluded that the primary issue of software development is not a technical issue but a management issue. Therefore, the second-level focus is on the software management process. A manageable process is a repeatable process, and a repeatable process can gradually evolve and mature. Level 2 management includes requirement management, project management, quality management, configuration management, and subcontract management. Project management consists of two processes: planning process and tracking and monitoring process. By implementing these processes, we can see a software development process that is executed as planned and controllable in stages from the management perspective.

3. Definition level

In Level 2, only the basic management process is defined, but the standard steps for execution are not defined. Level 3 requires the establishment of engineering standards for the enterprise scope, and both management and engineering development require a set of documented standards, and these standards are integrated into the process of enterprise software development standards. All developed projects need to adapt to this standard process and execute these processes. The tailoring process is not random and must be approved by the company's personnel before use.

4. Management Level

Level 4 Management is quantitative management. A corresponding measurement method is required for all processes. The quality of all products (including work products and products submitted to users) must have clear measurement indicators. These measurements should be detailed and can be used to understand and control software processes and products. Quantitative control will turn software development into an industrial production activity.

5. optimization level

The goal of Level 5 is to achieve a state of continuous improvement. Continuous improvement refers to improving the next execution process based on the feedback of the Process execution, that is, optimizing the execution steps. If an enterprise reaches this level, it indicates that the enterprise can continuously adjust the software production process to achieve the optimal performance based on the actual project nature, technology and other factors.

Ii. Structure

Except Level 1, each level of the SW-CMM is made up of exactly the same structure. Each level includes several key process domains (KPA) to achieve this level of goal, and each KPA further contains several key implementation activities (KP), regardless of which KPA, their implementation activities are organized according to five common attributes, that is, each KPA contains five types of KP.

1. Objectives

Each KPA has a set of targets. If this set of goals can be achieved in every project, it means that the enterprise meets the requirements of this KPA. If all the KPA requirements of a level are met, the capabilities required by this level are shown.

2. Implementation guarantee

Implementation guarantee is an activity that an enterprise must take in order to establish and implement the corresponding KPA. These activities mainly include the formulation of enterprise-wide policies and high-level management responsibilities.

3. Implementation capability

Implementation capability is a prerequisite for enterprises to implement KPA. An enterprise must take measures to perform the KPA execution activities only when these conditions are met. The implementation capability generally includes resource guarantee and personnel training.

4. Execute the activity

The execution process describes the necessary roles and steps required to execute KPA. Among the five public attributes, the execution Activity is the only property related to the project execution, and the other four attributes involve the establishment of the enterprise CMM capability infrastructure. Activities generally include plans, executed tasks, and task execution tracking.

5. Measurement Analysis

The measurement analysis describes the measurement and Measurement Analysis Requirements of the process. A typical measurement and measurement analysis requirement is to determine the status of the execution activity and the effectiveness of the execution activity.

6. Implementation Verification

Implementation Verification verifies that the execution activity is consistent with the established process. Implementation Verification involves management reviews and audits and quality assurance activities.

In the implementation of CMM, the order of KPA can be determined based on the different degrees of problems in the enterprise software process, and then the corresponding process can be established and implemented in the determined order. When executing a KPA, the target group can also be gradually satisfied. Process Evolution and gradual maturity are the purposes of the CMM System.