The different levels of the Continuous CMMI Capability Level and the Phased CMMI Maturity Level are

These two are not comparable, because they are mainly caused by different forms of expression.

These two are basically the same, but there are differences in the way they are expressed.

Answer]: BCMMI stands for Capability Maturity Model Integration, which is jointly developed and developed by the U.S. Department of Defense, Carnegie Mellon University and the U.S. Defense Industry Association, with the purpose of helping software companies manage and improve the software engineering process, enhance development and improvement capabilities, so as to develop high-quality software on time and without exceeding budget. 1.

The initial software process is disordered and sometimes chaotic, with little definition of the process, and success depends on individual effort. The management of the stool is reactive. 2.

The repeatability level establishes a basic project management process to track expenses, progress, and features. The necessary process discipline has been developed to replicate the successful experience of previous similar applications. 3.

The defined level has documented, standardized, and integrated the software management and engineering and handshake processes into the organization's standard software processes. All projects use approved, tailor-made standard software processes to develop and maintain software, and software product production is visible throughout the software process. 4.

Quantitative management-level analysis measures the detailed measurement data of software processes and product quality, and has quantitative understanding and control of software processes and products. Management has an objective basis for making conclusions, and management is able to perform within a quantitative range. 5.

Optimize the management of the coarse-level process, quantitative feedback and advanced new ideas and technologies to promote continuous improvement of the process.

Answer]: BCMMI stands for Capability Maturity Model Integration, which is jointly developed and developed by the U.S. Department of Defense, Carnegie Mellon University and the U.S. Defense Industry Association. 1.

The initial software process is disordered and sometimes chaotic, with little definition of the process, and success depends on individual effort. Management is reactive. 2.

The repeatability level establishes a basic project management process to track expenses, progress, and features. The necessary process discipline has been developed to replicate the successful experience of previous similar applications. 3.

The defined level has documented, standardized, and integrated the processes of both software management and engineering into the organization's standard software processes. All projects develop and maintain software using approved, tailored, standard software processes, and the production of software products is visible throughout the software process. 4.

Quantitative management-level analysis of detailed measurement data of software processes and product quality, and quantitative understanding and control of software processes and products. Management has an objective basis for drawing conclusions, and management is able to perform within a quantitative range. 5.

Optimize the quantitative feedback of the management-level process and advanced new ideas and technologies to promote the continuous improvement of the process.

The basic idea of CMM.

The basic idea of CMM is that because problems are caused by the way we manage software processes, the use of new software technologies does not automatically increase productivity and profitability. CMM helps organizations establish a regular, mature software process. The improved process will produce better quality software, saving more software projects from time and cost overruns.

The software process encompasses a variety of activities, technologies, and tools used to produce software. Therefore, it actually encompasses the technical and administrative aspects of software production. CMM strategy seeks to improve the management of software processes, and technical improvements are the inevitable result of this.

It is important to keep in mind that improvements in software processes cannot be done overnight, CMM introduces changes incrementally and incrementally. CMM clearly defines 5 different levels of "maturity", allowing an organization to progress to a higher maturity level in a series of small improvement steps.

The necessity of implementing CMM.

The risk of software development is due to the low capacity of software processes, the most critical problem of which is that software development organizations cannot manage their software processes well, so that some good development methods and technologies do not work as expected. Moreover, the success of the project is also due to the outstanding efforts of the working group, so success based on the availability of specific personnel alone cannot lay the foundation for long-term improvement in production and quality throughout the Organization, but must be consistent in establishing an infrastructure of effective software such as management engineering practices and management practices in order to achieve continuous improvement and sustainable success. Software quality is a vague, elusive concept.

We often hear: so-and-so software is easy to use, so-and-so software is not easy to use; The software is fully functional and reasonably structured, and the software function sheet is single.

First, the operation is difficult ......These vague language cannot be regarded as software quality evaluation, let alone quantitative evaluation of software quality science. Software quality, and even the quality of any product, is a very complex nature and behavior. Product quality, including software quality, is the attribute and behavior of people's practical products, which can be recognized and scientifically described.

There are a number of methods and human activities that can be used to improve quality. The implementation of CMM is an effective way to improve the quality of software: an effective and reasonable method to control the software production process, improve the organization of software producers and the individual ability of software producersSoftware engineering is related to many research fields and practical problems, and the main related fields and factors are:

Requirements Engineering. Theoretically, requirements engineering is the application of proven principles, techniques, and tools to help a systems analyst understand a problem or describe the outward behavior of a product. Software reuse is defined as the use of engineering knowledge or methods to build a new system from an existing system.

This technology improves the quality and productivity of software products. There are also software checks, software metrology, software reliability, software maintainability, software tool evaluation and selection, etc.