CMMI called: Capability Maturity Model Integration, or Capability Maturity Model Integration. CMMI is the latest version of CMM model. Early the CMMI (CMMI-SE/SW/IPPD) 1.02 version was used in the software industry in project management, SEI in some countries and regions to promote and trial began. With the application of the promotion and development of the model itself, has been widely interpreted as a comprehensive model of the application.
Since 1994, SEI Software CMM has been officially released, have also developed a systems engineering, software procurement, human resources management and integrated product and process development in a number of Capability Maturity Model. Although these models in a number of organizations have been a good application, but for some large-scale software enterprises, the need may arise at the same time using a variety of models to improve their ability to multi-process. By then they will find there are some problems, of which the main issues reflected in:
n can not concentrate on their different ability to process improvement in order to achieve greater results;
n must be carried out to repeat the training, assessment and improvement activities, thus increasing the number of cost;
n encountered a number of different models of the same things that are inconsistent or incompatible activities, and even Law.
So, I hope to integrate the needs of different CMM model produced. In 1997, the U.S. Federal Aviation Administration (FAA) has developed a FAA-iCMMSM (Federal Aviation Administration's Integrated CMM), the model applies to systems engineering integrates the SE-CMM, software access to the SA-CMM and software, SW - CMM model of all three principles, concepts and practice. The model is considered the first integrated model.
Preparatory work for CMMI assessment
Practice has proved that assessment: conducting CMMI assessment, develop a correct assessment of plans and documents to ensure that there is a very experienced, trained and appropriately qualified team can be used to assess the implementation of the assessment process to prepare is very necessary.
Document we are talking about CMMI assessment of the results, including: requirements, agreements, valuation, risk, tailoring, as well as associated with the assessment of the practical considerations (such as: scheduling, logistics, organization background information). In addition, it should be initiated to obtain and record the side for the CMMI assessment plan for formal approval. In the formulation of the assessment plan, to deal with the importation of CMMI evaluation be reflected in documents of the agreement, the agreement will help to assess the objectives and key CMMI Assessment Program of the common understanding of the parameters. Drive the planning process in the key parameters of a common understanding of the basis, CMMI and SCAMPI assessment initiated by the division director of assessment should be to reach agreement on the assessment plan; initiator and evaluation team leader should have been planned to assess the technical and non-technical details to reach unanimously. The scheme in the implementation of other stages of the planning and preparation activities that need to be further refined.
CMMI assessment team through the preparatory work will have an experienced, trained and accurate positioning of the group is ready to implement CMMI assessment tasks. Member of the panel should be obtained to complete their respective tasks necessary knowledge, or if they have prior knowledge is sufficient to confirm the completion of related tasks. The evaluation team leader has been provided to each individual to complete their task on the opportunity to practice skills, or confirm that these skills in the past has been exemplary. Mutual understanding between team members, at the same time started to plan how they coordinated the work. It should also be done: to prepare a good team is to assess the objectives of serving members of the panel have to provide training and training results are recorded, when necessary, for they have done due to lack of knowledge or skills of remedial work has been completed. We believe that, regardless of CMMI assessment team leader is to start from scratch a new assessment of the training group, or from experienced team members choose to form a team to ensure that they and CMMI assessment team leader to the formation of a successful collective its responsibility. In addition, CMMI assessment of the preparatory work, the model we should also understand the principle of tailoring:
1. In some applications, the program templates and procedures for the routine assessment of the needs can be adjusted, which is the process of local ownership as facilitate the exchange;
2. A structured group program in the process is conducive to the experience of only a limited assessment of the organization, such a strategy to ease the process as like, the risk is found a valuable opportunity;
3. Case study materials provide a variety of options to expand the content of group training to enhance the training of those who need to focus more;
4. An experienced team leader to assess the case in the absence of analysis, the same can be simulated to assess the management and conduct;
5. In the group have been training all members of the collection, the establishment of the group's work to ensure that its management team cohesion is important, therefore, a lot of team-building exercises are available, group size, skills, composition are part of the contents of this method of cutting;
6. The use of tools including an assessment plan template, sample, and planned procedures embedded template assistance, in addition, in order to estimate the impact assessment of constraints, and methods to estimate worksheet is also useful.
In short, CMMI assessment is a very complex process, but also because of its uncertainty, the practice in the assessment must be prepared to do. From the practice of truth, we believe that as more and more software organizations to CMMI assessment, more and more successful experience for our use and learn from.
Cmmi assessment methods
Since 1991, CMM there were a lot of models, covering a wide range of fields. Well-known model in which software engineering software engineering procurement integrated product and process development. However, when enterprises want to organizations of different professions in the field of process improvement, these areas of expertise for different models and methods in the framework of the contents of the different restrictions on the successful implementation of the organization's ability to improve. In addition, this model will be integrated in the organization of training also increased the cost of certification and to improve. Including a number of fields of a model with integrated support for training and certification will solve these problems.
CMMI (Capability maturity model integration) is to merge the three models to a framework
Capability Maturity Model for Software (SW-CMM) v2.0 draft C,
Electronic Industries Alliance Interim Standard (EIA / IS) 731
Integrated Product Development Capability Maturity Model (IPD-CMM) v0.98
Like other CMM model, CMMI Process Improvement provides guidance, rather than a description of the process or processes. The actual process used by the organization depends on many factors, including the application of the organizational framework and scale of the field. CMMI many proven methods of adding structure to help organizations evaluate the group of software process maturity, the ability of a degree, and to establish priorities for improvement and implementation of improvement.
From the CMMI Framework can generate different CMMI model, it is necessary first to identify the most suitable type of model to improve the business process needs.
Stage continuous description or description of
Systems engineering or software engineering or both
Can be described using the continuous choice for their needs in accordance with the order of process improvement to reduce enterprise risk, which to do so through the ISO process improvement to provide a convenient comparison. Degree of use of capacity (Capability) to measure.
Stage provides a description of the process has already been verified to improve the order to facilitate the transplant from the CMM. The use of maturity (Maturity) to measure process improvement.
Systems engineering, including the development of the entire system, which may include or may not include software.
Software engineering for software system development, mainly using the system in a quantitative scientific approach to the development of operation and maintenance of software.
cmm is a project management
By the United States Carnegie Mellon University Software Engineering Institute (SEI) created the CMM (Capability Maturity Model Software Capability Maturity Model) certification assessment, in the past decade, the global software industry had a very far-reaching impact. There are five CMM levels, the capacity of software companies, respectively, marked the five-level maturity. From low to high, software development and production plans to increase the accuracy level, unit level works to shorten the production cycle, lower unit costs of the project level. According to SEI statistics, the software company by assessing the project's ability to estimate and control about 40% to 50%; productivity increased by 10% to 20% error rate of software products declined by more than 1 / 3.
Of a software business to basically CMM2 entered on the scale of the development of basic software has a modern enterprise's basic structure and methods, have the capacity to undertake outsourcing projects. CMM3 assessment will need to grasp the largest software integration, including integration of the overall framework. In general, the adoption of the higher level of CMM certification, and its easier access to the user's confidence in the domestic and international market, the stronger competitiveness. Therefore, it can also become a CMM certified software enterprises in the international project to measure the ability to develop an important sign.
CMM is the world recognized software products permit to enter the international market, it is not only on product quality certification, it is also a way to improve the software process. CMM assessment to participate in Brocade said that the assessment of the adoption of CMM certification is not a goal, it is just to promote software companies in product development, production, service and management continue to mature and progress means, is a continual upgrade and improvement of their own ability to process. The consulting firm by the United States is responsible for assessing the PIA and the final certification through CMM3 marked Brocade capacity in quality management has risen to a new level.
CMMI is divided into five levels, the process of region 25 (PA) (as shown).
1. Initial software process is disorderly and sometimes chaotic, almost no definition of the process, success depends on personal efforts. Management is reactive.
2. Management level has been the establishment of the basic project management process to track cost, schedule and functional features. Process to develop the necessary discipline to repeat earlier made a similar application of the successful experience of the project.
3. Class has been defined management and software engineering aspects of the process of documentation, standardization, and integrated into the organization's standard software process. The use of all the projects are approved, the process of tailoring the standard software to develop and maintain software products throughout the software process is visible.
4. Quantitative analysis of the management of the software process and product quality of the detailed measurement data, the software process and products are quantitatively understood and controlled. Management to make the conclusions of an objective basis, management can quantitatively predict the performance of the framework.
5. Optimization of quantitative process management-level feedback and advanced new ideas, new technology to promote continuous improvement process.
Each grade were divided into the process domain, and the special goals and specific practices, common goals, common practice and common features:
Each level has a number of the process of regional components, the course of these domains form a common software process capability. Domain of each process, there are some special goals and common objectives, through the special practice and general practice to achieve these goals. When a process all the special domain of practice and general practice have been implemented as required, will be able to achieve the objectives of the process domain.
Ability grade: statements are continuous, the capacity of a total of six grade (0 ~ 5), the ability of each grade corresponds to a general objectives, as well as a set of general methods and specific methods of implementation.
0 incomplete grade
Executive Level 1
2 management level
3 definition of class
Quantitative Management level 4
The best level of 5
CMMI assessment methods:
Self-evaluation: leadership for the enterprise's own software evaluation capacity.
Director of assessment: to evaluate the leadership of the enterprise's own software, the ability to promote software companies announced their ability to
CMMI assessment type:
Software organizations, software process on the specific capacity assessment.
Software organizations to assess the capacity of the overall software (software capability maturity level of assessment).
The basic idea of CMMI
1, the process of software projects to resolve difficult issues to improve
2, the realization of software engineering of parallel and multi-disciplinary combination of
3, to achieve the most cost-effective process improvement
1, CMMI background
CMM's success prompted the development of other disciplines also have a similar model of process improvement, such as systems engineering, requirements engineering,
Human resources, integrated product development, software procurement, etc., derived from the CMM to improve the model, such as:
(1) SW-CMM (Software CMM) software CMM
(2) SE-CMM (System Engineering CMM) systems engineering CMM
(3) SA-CMM (Software Acquisition CMM) software acquisition CMM
(4) IPT-CMM (Integrated Product Team CMM) Integrated Product Groups CMM
(5) P-CMM (People CMM) Human Resources Capability Maturity Model
In order to show the difference between a lot of information at home and abroad CMM called the SW-CMM. SEI in accordance with the original plan, CMM improvements in version 2.0 should be completed in November 1997, and then made a practice of version 2.0, after feedback, in 1999 completed version of quasi-CMM2.0.
However, the Office of the U.S. Department of Defense released CMM2.0 delayed version of SEI, and the first to complete a project more urgent CMMI, because the tissue in the same model more than the existence of process improvement may lead to conflict and confusion, CMMI is In order to address how to maintain the coordination between these models.
CMMI (Capability Maturity Model Integration) that is the Capability Maturity Model Integration, which is an idea the U.S. Department of Defense, they all want to now will be developed, as well as the various Capability Maturity Model, integrated into a framework. The framework has two functions, first, the reform of the procurement methods for software; secondly, to establish a integrated product and process from the point of view of development, including the sound principles of system development process improvement. On the software, CMMI is a SW-CMM revised version.
It integrated the SW-CMM 2.0 version of C and the SPA in the draft of a more rational, more scientific and more of the advantages of well. SEI in the published version of CMMI-SE/SW 1.0 was announced about two years to complete from the CMM to CMMI transition.
CMMI project is more industry and government departments to provide an integrated set of products, its main purpose is to eliminate inconsistencies between the different models and duplication and reduce the cost of model-based improvement. CMMI will be more systematic and coherent framework to guide organizations to improve software processes, products and services to enhance the development, acquisition and maintenance of capacity.
From the industry, • the United States Government and Carnegie Mellon University Software Engineering Institute initiated the first Capability Maturity Model Integration (CMMI) project is committed to helping alleviate the plight of enterprises. CMMI to improve the processes of an organization provides a single integrated framework, the new integrated model of the framework of each model to eliminate the inconsistencies between the model to reduce duplication, increase transparency and understanding, set up a automatic, can be expansion of the framework. Therefore, it can re-organization to improve the overall quality and efficiency. CMMI main concern is the cost-effectiveness, a clear focus, process focus and flexibility of four aspects.
With the original Capability Maturity Model similar, CMMI is also included in the establishment of an effective process in different fields is essential for the industry reflects the generally accepted "best" practice; fields covering software engineering, systems engineering, product development and systems integration procurement. On this premise, CMMI for enterprises to build and improve the process of providing guidance and a framework for the role; at the same time assessing their own business processes that can be the light of the industry benchmarks.
2, CMMI source models
Capability Maturity Model for Software version 2.0, C version; Electronic Industry Association Interim Standard (EIA / IS) 731; Integrated Product Development Capability Maturity Model (IPD-CMM) v0.98.
3, CMMI principles
(1), stressed the support of senior managers. Process improvement is often recognized by the senior managers and made big efforts and consistent support is the key to process improvement.
(2), carefully determine the goals to improve, first of all, should be given time to finish the goal of improving the estimates and the definition of the right and formulated a plan. Options to achieve the goals and be able to see the effectiveness of the organization.
(3), choose the best practice, organizations should be based on existing software activities and processes of wealth, make reference to other standard model, to select the essence of its dross, a new model of practice.
(4), process improvement and organization to the business goal is the same, closely integrated with development strategies.
4, CMMI goals
(1), to improve the organizational processes and management of product development, publishing and maintenance capabilities to provide protection.
(2) to help group the objective evaluation of their own weaving and process Capability Maturity domain ability to establish priorities for process improvement and implementation of process improvement class.
5, CMMI approach
(1), decide which level of CMMI model best suited to the needs of organizational process improvement.
(2), choose the model that is continuous or stage.
(3), decided to organize the model requires knowledge of the field.
(4), similar to the CMM process improvement step 6, integrated into process improvement: the beginning of integrated process improvement, to improve the construction of integrated platforms, the traditional process of integration, the launch of a new process to improve the assessment.
6, CMMI content
CMMI is divided into "Required" (necessary), "Expected" (expectations), "Informative" (providing information) the three-level, to measure the quality of the model, including the importance and role. The most important thing is "demand" level, is the model and the basis for process improvement. The second-level "expectations" in the process played a major role in improving, but some cases may not be not necessary for the success of the organization in the model. "Provided information" constitutes the main part of the model for process improvement provide useful guidance, in many cases, their needs and expectations of the members have done a further explanation.
"Request" of the model components is the goal, process improvement on behalf of the desired end state, it is the realization of that project and process control has reached a certain level. When a key corresponding to a target domain process, it referred to as the "specific objectives"; the corresponding domain on the entire key to the process known as "the common goal." CMMI model includes the entire 54 specific objectives, key processes in each domain corresponds a specific target 1-4. Description of each goal is very simple, in order to fully understand the requirements of the goal is to expand the "expectations" component.
"Expectations" component is a way to represent the practical means of achieving the objectives and complement understanding. Each method can be mapped to a target, when a method is the only one of the objectives is the "particular method"; and can be applied to all targets is the "common method." CMMI model include specific methods 186 of each objective method corresponds to 2-7.
CMMI includes 10 kinds of "information provided in": The purpose of a general summary of the key processes and domain-specific goals; introductory description of the scope of Key Process Areas, nature and impact of the actual methods and characteristics; quoted, the key process domains The point is by reference; name, said a key component of the process domain; methods and objectives of the relationship, the key method of process mapping to the target domain the relationship between the tables; Notes, the Notes of the key process of domain model elements to other sources of information; typical work product set, the key to the process of definition of time domain methods of implementation of the work products produced; son method method activities and a detailed description of the decomposition; disciplines expand, CMMI is an independent academic counterparts, here are the corresponding expansion of specific disciplines; common methods in detail description of the key process of the application domain practice the common methods described in detail.
CMMI provides a continuous phase and the two said, but the two expressions are logically equivalent. We are familiar with the SW-CMM Capability Maturity Model for software that is the stage of the model, SE-CMM for systems engineering model is a model, and the IPD-CMM Integrated Product Development model combines the continuous phase and the characteristics of the two.
Stage approach to model-wai said a series of "maturity level" stage, each stage of a group of KPA has pointed out that an organization should focus on where to improve their organizational processes, each KPA to meet its objectives by way of description, process improvement through a particular level of maturity KPA meet the needs of all objectives achieved.
Continuous-stage model is not as fragmented as the stage model of the KPA is when the external form of KPA, and applies to all of the KAP, through the realization of the common ways to improve the process. Pointed out that it does not specifically target, but stressed that method. Organizations can cut their own appropriate and continuous model to determine the goals of the KPA to improve.
Expression differences between the two reactions for each level of ability and maturity to describe the process and methods used, although they described the mechanism may be different, but that the two methods through the use of common objectives and methodology of the needs and expectations as a model elements to achieve the same purpose to improve.
CMMI is a challenge is to create a single model, and the stage from the continuous observation of two perspectives, contains the same basic information to improve the process; dealing with the same range of a CMMI process can produce the same conclusion. Unified CMMI (U-CMMI) is a means only to support the common methods and composition of their model KPA. When according to a conceptual approach to the preparation can be extended and for the definition of organizations have specific goals for the process template, the template definition will define a component model to apply to any project or other.
Difference between CMMI and CMM:
CMMI is the successor model of SW-CMM and SE-CMM, the former is what we refer to the CMM. CMMI and SW-CMM is the main difference between a number of areas of coverage; so far include the following four areas:
(1), software engineering (SW-CMM)
Software engineering is the development of software systems, demanding the realization of software development, operation, maintenance activities in a systematic, institutionalized, and quantified.
(2), systems engineering (SE-CMM)
Systems engineering is a full set of system development activities, may or may not include software. Systems engineering is the core of the customer's needs, expectations and constraints into product solutions and the realization of solutions to provide full support.
(3), integrated product and process development (IPPD-CMM)
Integrated product and process development is the product life cycle, through the cooperation of all relevant staff, using a systematic process to better meet customer needs, expectations and demands. If the project or choose IPPD process, you need to choose the model of all relevant practice and IPPD.
(4), procurement (SS-CMM)
The contents of the procurement for the conduct of those suppliers to the project played a key role in the success of the project. Include: identify and evaluate potential sources of products to determine the need to purchase the target product suppliers, supplier monitoring and analysis of the implementation process, evaluate the work of suppliers to provide products and supply agreement for the supply of the relationship is appropriate adjustments.
In these modules, enterprises can choose to software engineering, or engineering, you can choose. Integrated product and process development and procurement is in line with the major software engineering and systems engineering to use the content. For example, pure software companies in the CMMI can choose the content of software engineering; equipment manufacturers can choose to systems engineering and procurement; integrated enterprise can choose to software engineering, systems engineering and integrated product and process development. Most of the content of CMMI is applicable to various areas, but implementation will be significant differences, so the model provides a "detailed applications in different fields."
CMM measurement of the activity-based methods and falls were the order of the process, activity-based management standards are closely linked, it is more suitable waterfall type development process. CMM and CMMI relatively more step to support the iterative development process and economic motives to promote the use of results-based organization approach: the development of business cases, the concept and prototype programs; into the baseline after the structure refinement can be released as the final published version of the scene. Although the CMMI retained activity-based methods, it does integrate many of the modern software industry best practice, so it falls to a large extent and to dilute the ideological ties.
CMMI model in the retention phase of the CMM model, based on a continuous model, this can help an organization, as well as the organization's customers a more objective and comprehensive understanding of the process of its maturity. At the same time, the use of continuous model can give an organization improved during the course of time lead to greater autonomy, no longer the same as in the CMM, the severe restrictions imposed by the hierarchy. The benefits of this improvement is the flexibility and objectivity, and weakness is due to the lack of guidance, an organization may be the key to the process of a lack of domain-dependent relations between the correct one-sided understanding of the implementation process, resulting in a process of some castles in the air, there is no other process support. Two expressions (continuous and phase) from their course of covered area is no different, different is the process of regional organization and the maturity (capability) level to determine ways.
CMMI than the CMM model to further strengthen the importance of demand. In the CMM, the only demand-side management on the needs of a key process in this domain, that is, emphasis on quality management needs, and how to obtain a clear There are no requirements. Stage in the CMMI model, there are three key processes of an independent domain name needs to develop and put forward on how best to obtain the requirements and methods of demand. CMMI model for the project activities to strengthen certain. In the CMM, only three of the software product engineering and peer review process of the two key domains is closely related to the engineering process, and in the CMMI, the demand will develop, verify, confirm, technology solutions, product integration of these projects process activities are the key to the process as a separate domain for the request, which in practice put forward higher requirements on the project and more specific guidance. CMMI also stressed the importance of risk management. Unlike in CMM risk management in the distributed programs and projects in the project tracking and monitoring requirements in, CMMI3 separate class in a separate domain called the key to the process of risk management.
CMMI standard terminology
1 AT Assessment Team assessment panel
2 ATM Assessment Team Member, members of the panels
3 BA Baseline Assessment of baseline assessment
4 CAR Causal Analysis and Resolution reason analysis and decision-making
5 CBA CMM-Based Appraisal of the evaluation based on CMM
6 CBA-IPI
CMM-Based Appraisal for Internal Process
Improvement
For internal process improvement and the CMM-based assessment (usually
Known as the CMM assessment)
7 CC Configuration Controller Configuration Manager
8 CF Common Feature of public properties
9 CFPS Certified Function Point Specialist Register Function Point experts
10 CI Configuration Item Configuration Item
11 CM Configuration Management Configuration Management
12 CMM Capability Maturity Model Capability Maturity Model
13 CMMI Capability Maturity Model Integration Capability Maturity Model Integration
14 COTS Commerce off the shelf commercial off-the-shelf
15 DAR Decision Analysis and Resolution Decision analysis and the development of
16 DBD Database Design Database Design
17 DD Detailed Design Detailed Design
18 DP Data Provider data providers
19 DR Derived Requirement derived demand
20 EPG Engineering Process Group Engineering Process Group
21 FP Function Point Function Point
22 FPA Function Point Analysis Function Point Analysis
23 FR Functional Requirement of functional requirements
24 GA Gap Analysis Gap Analysis
25 ID Interface Design Interface Design
26 IFPUG International Function Point Users Group International Function Point User Group
27 IPM Integrated Project Management Integrated Project Management
28 IR Interface Requirement Interface needs
29 KPA Key Process Area Key Process Areas
30 KR Key Requirements The key requirements
31 LA Lead Assessor, director of assessment
32 MA Measurement and Analysis Measurement and Analysis
33 MAT Metrics Advisory Team Measurement Advisory Group
34 MCA Metrics Coordinator and Analyst measure of the Commissioner
Measure 35 ML matreraty library database
36 NFR Non-functional Requirement of non-functional requirements
37 OC Operational Concept concept of operations
38 OID Organizational Innovation and Deployment organizational innovation and deployment
39 OPD Organizational Process definition Organization process definition
40 OPF Organizational Process focus Organization process focus
41 OPL Organizational Process Assets wealth of organizational processes
42 OPP Organaizational Process Perormance performance of organizational processes
43 OSSP Organization's Set of Standard Process
Set standards process
44 OT Organizational Training Organization-level training
45 PA Process Areas Process Areas
46 PAT Process Action Team Process Action Team
47 PB Process Assets Library Process Library wealth
Summary 48 PD Preliminary Design Design
49 PDSP Project Defined Standard Processes standard definition of the process of project
50 PI Produce Integration Product Integration
51 PLC Product Life Cycle Product Life Cycle
52 PMC Project Monitoring and Control Project Monitoring
53 PP Project Planning Project Planning
54 PPQA Process and Product Quality Assurance process and product quality assurance
55 PPR Price Performance Ratio price-performance ratio
56 QA Software Quality Assurance Software Quality Assurance
57 QA Quality Assurance Quality Assurance
58 QAP Software Quality Assurance Plan Quality Assurance Plan
59 QPM Quantitative Project Management quantitative project management
60 RD Requirements Development needs to develop
61 RM / ReqM Requirements Management Requirements Management
62 RSKM Risk Management Risk Management
63 RTM Requirement Traceability Matrix Traceability Matrix demand
64 SAM Supplier Agreement Management. Supply agreement management
65 SC Steering Committee Steering Committee
66 SCAMPI
Standard CMMI Assessment Method for
Process Improvement Process Improvement Standard CMMI Assessment Method
67 SCCB Software Configuration Control Board Software Configuration Management Control Board
68 SCM Software Configuration Management Software Configuration Management
69 SDP Software Development Plan Software Development Plan
70 SEI Software Engineering Institute (USA) Software Engineering Institute
71 SEPG Software Engineering Process Group Software Engineering Process Group
72 SPI Software Process Improvement Software Process Improvement
73 SPP Software Project Planning Software Project Planning
74 SPTO Software Project Tracking and Oversight Software Project Tracking and Monitoring
75 SR System Requirements System Requirements
76 SRS Software Requirement Specification Software Requirements Specification
77 SSM Software Subcontract Management Software Subcontract Management
78 SSR Software System Requirement Software System Requirements
79 TS Technical Solution Technical Solutions
80 UC Use Case Use Case
81 UID User Interface Design User Interface Design
Confirmed 82 VAL Validation
83 VER Verification authentication
84 WBS Work Breakdown Structure WBS
85 WP Work Products Work Products
86 Pre-assessment pre-assessment
Baseline 87 Baseline
88 Quality Attribute Quality attributes
Scene 89 Scenario
Keywords: CMMI, SCAMPI, Process Improvement, Capability Maturity, EPG
Software Capability Maturity Model (CMM / CMMI) has become the IT industry in the process of general-purpose system, is a software enterprises to improve product quality, and enhance the core competitiveness of enterprises an effective way of bringing it to the success of software companies have for many domestic and foreign proof of a well-known software vendors, according to statistics SEI, CMM software companies after the introduction of labor productivity grew by an average of 35 percent; to reduce the error rate of 39 percent on average; the average cost rate of return of 5:1. Looking at domestic since 1993 Motorola (China) Up to subsequent Neusoft, Kingdee, UF and other companies have implemented CMM or CMMI, the domestic enterprises to implement CMMI ascendant for a time. However, the majority of enterprises (nearly 60% of enterprises) to implement the CMMI less than ideal results, and ultimately to the failure of a variety of reasons, such as the EPG not the quality of personnel, EPG team loose and just be a piece of paper certificates, the neglect of process improvement projects on the importance of the enterprise itself, a variety of these reasons is the fundamental core of the formation of EPG. CMMI advisory capacity as the first national enterprises set up in the EPG have a deep understanding and experience. EPG formation in concrete has the following four steps:
1, EPG called
The process of improving the implementation of staff if there is not sufficient software engineering background, not enough in an organization's ability to complete its job, it may lead to the failure of the implementation of the project. It is necessary to choose those who are experienced and capable staff to participate in the implementation process to give full play to their enterprises positive influence.
Basic operation is as follows: Consulting with customers and staff need to have the EPG related conditions, customer consulting firm in accordance with the conditions provided by staff, combined with the specific situation of the persons of the Company to provide the list of EPG team members,
2, EPG to identify
Provided by the client group the list of EPG on the basis of consulting with customers to exchange and filter which does not meet the requirements of the staff, and ultimately determine the EPG members. Once the EPG members, it is necessary to maintain its stability, free movement of persons frequently, resulting in process improvement project costs.
3, Organization
After the officers identified will be organized together to form project teams EPG, EPG project team to establish a common vision or goal, to ensure that the members agreed and accepted the goal, we need to establish common values and beliefs, so that members believe that it is feasible to process improvement projects and necessary, it is important to businesses and high-efficiency, improve product quality. At the same time, need to be clear at this stage the following points:
(1) clear the members of the EPG project the role and responsibilities and to preserve the form of documents;
(2) to ensure access to public support for a timetable;
(3) to ensure that EPG team has the resources;
(4) the establishment of sound records and information communication system;
(5) the development of team rules;
4, training
In the clear after the corresponding task, process improvement projects in order to make a smooth and effective implementation, consultants need to
Project team members to carry out relevant training content, and conduct in-depth understanding of CMMI models and learning the job skills training EPG, including its ability to conference management, project management capability to make it more profound understanding of the role of their own, as well as how to until the completion of the development plan.
5, EPG plan
Members to the project in the knowledge after the training, the project members of the CMMI to understand the basic knowledge, in this
Kind of basis, consultants, together with the EPG members, combined with the actual situation of enterprises, from the reality of process improvement projects to complete specific plans, process improvement team members make a clear mandate to further the mission and the task of refining the time cut-off point.
6, tracking and monitoring
For CMMI process improvement project, the plan is the premise of doing a good job, but the latter part of the tracking and monitoring is key to process improvement through follow-up project plan for the implementation of the plan to solve the problems and amend the plan timely. If there are no good to plan the implementation of effective and reasonable follow-up, is likely to lead us to slow down the process of improving the project or from the track, which eventually led to the failure of CMMI project.
EPG for the formation of the above methods and the need to pay attention to the issue of a certain amount of interpretation, the company engaged in the process improvement projects for many years, according to the experience of many years, CMMI project to succeed, each stage requires a lot of effort into, "a son mistake, one single mistake and blowing up the whole "and therefore, the formation of links in the EPG to pay attention!
Disclaimer: This article belongs to all science and technology, reprint please specify the source of the author and.
Between five levels of maturity are as follows:
1, the initial level
Features:
(1) software process is characterized by chaotic and sometimes confusing. The definition of almost no rules or steps in the process.
(2) to make excessive Connaught. Often make good the promise: such as "in accordance with the methods of software engineering, the engineering process in an orderly manner to work"; or the promise to achieve high goals. But the fact is the emergence of a series of crises.
(3) face a crisis on the give up the original planning process and repeated coding and testing.
(4) the success depends entirely on personal efforts and outstanding professionals, depending on the management of extraordinary and outstanding effective software developers. Specific performance and results are derived from or is determined by the capacity of individuals and their previous experience, knowledge and their degree of initiative and positive.
(5) the ability of the characteristics of the individual only, rather than the development of the Organization of the holds. Depend on the quality of the individuals or under tremendous pressure, or looking for tips to bear fruit. However, once such people leave, the stabilizing role of the organization also disappeared.
(6) software process can not be identified and can not be predicted. Software, the degree of maturity of the software in the first-class software organization of the work process in the actual process of change often (random process). Such organizations are also developing products, but the results are unstable, unpredictable, non-repetitive. In other words, the software program, budget, function
And the quality of the product are not identified and can not be predicted.
Process:
(1) the existence or the use of stable minimal process.
(2) the so-called "process" often is "to do" is concerned.
(3) a variety of regulations, rules and regulations incompatible and even contradictory
Staff:
(1) rely on the personal efforts and outstanding figures. Once the good people leave, the project will not be able to continue to
(2) people's work as "fire." In the development process is constantly at risk, as well as the constant "fire fighting."
Technology:
Introduction of new technologies is a great risk
Measurement:
Does not collect data or analysis of data
Improve the direction of:
(1) on the establishment of the management process. The implementation of standardized management. Commitment to the protection of the project.
(2) first and foremost task is to carry out demand-side management, the establishment of software between the client and the shared understanding of the project truly reflects the customer requirements.
(3) the establishment of a variety of software projects. Such as software development, software quality assurance plan, software configuration management plan, software test plans, risk management planning and process improvement plans.
(4) to carry out the activities of software quality assurance (SQA).
2, repeatable level
Features
(1) Connaught for more realistic, according to previous similar projects in the successful experience of the process of establishing the necessary criteria
To ensure the success once again.
(2) is a project by project to build the basic Process Management process to strengthen the capacity of the Ordinance.
(3) the establishment of the basic project management process to track cost, schedule and functionality.
(4) the management of the main tracking software expenditures, progress and function. Commitment to identify emerging issues.
(5) the use of a baseline (BASELINE) to mark the progress of the integrity control.
(6) defines the criteria for software projects, and believes that it, follow it.
(7) through the contract to establish an effective relationship between supply and demand.
Process
(1) software development and maintenance of the process is relatively stable, but the process of establishing at the project level.
(2) there are rules in the software process is an effective project management system under the control of the success of previous experience can be repeated.
(3) when problems arise. Ability to identify and correct. Its commitment to be achieved.
Staff
(1) the success of the project depends on the ability of individuals and management support.
(2) understand the need for management and the commitment of management.
(3) attention to the training of personnel,
Technology
The establishment of technical support activities, and a stable plan.
Metric
The establishment of resource planning for each project. Mainly concerned about costs, products and progress. A corresponding management data.
Improve the direction of
(1) is no longer in accordance with the process of project development software, but summing up the successful experience of various projects so that the rules of the specific experience summed up in an organization-wide standard software process. To improve the organization's overall software process capability of the software process activities as software development organizations.
(2) to identify an organization-wide standard software process, software engineering and management activities into a firm to determine the course of the software. So that we can improve the software process of cross-item effects, can also be used as the basis for software process tailoring.
(3) the establishment of Software Engineering Process Group (SEPG) long-term commitment to software process assessment and control tasks, in order to adapt to the requirements of future software projects.
(4) the accumulation of data: the establishment of organizational software process software process library and library-related documents
(5) to enhance the training.
3, to determine class
Features
(1) Whether management or software process engineering have been documented, standardized, and integrated into software development organizations software process standards.
(2) software process standards are applied to all projects for the establishment and maintenance of software. Some projects may also be based on the actual situation of software development organizations standard software process tailoring.
(3) engaged in a project, the production process, costs, programs and functions can be completely controlled, so the software can also control the quality.
(4) Software Engineering Process Group (SEPG) is responsible for software process activities.
(5) in the arrangements for organization-wide training program.
Process
(1) the full implementation of the organization as a whole integrated process management and project management. Software engineering and management activities are stable and repeatable, with continuity.
(2) software process has to foresee and prevent the issue of the role, would minimize the risk of
Staff
(1) to the project team's way. As an integrated product team.
(2) in the entire organization for the definition of all software process activities, have an in-depth understanding of the task. Greatly enhance the ability of the process.
(3) in a planned way according to the role of staff training c
Technology
Based on qualitative assessment of the new technology.
Metric
(1) in the whole process of data collection.
(2) in the whole project to share data in a systematic
Improve the direction of
(1) began the process of quantitative analysis software in order to achieve quantitative process control software project results.
(2) the adoption of quality management software to achieve software quality goals.
4, the management level
Features
(1) the development of the software process and product quality of the detailed and specific metrics. Software process and product quality can be understood and controlled.
(2) the ability of software organizations is predictable. The reason is that software process is defined by metrics and operational metrics. It goes without saying. The quality of software products can be predicted and controlled.
(3) organization works to ensure that all project metrics to measure productivity and quality, and the software process as an important reactive live.
(4) the definition of a good and consistent standard of service metrics to guide the software process and for evaluating the software process and products based on the quantitative.
(5) in the development of the organization software process database has been established to preserve the data collected can be used for the purpose of software process.
Process
(1) the beginning of the process of quantitative understanding of the software.
(2) small changes in software process. Generally acceptable range.
(3) can be predicted that the software process and product quality trends. Once the quality beyond measure by or be in violation of these standards. Can be used to correct a number of methods in order to achieve a good standard of the day.
Staff
Each item exists in a strong work ethic groups, because each individual's role in understanding the relationship between the organization and therefore able to generate awareness of such groups.
Technology
Continuous basis in the quantitative assessment of new technologies.
Metric
(1) carried out an organization-wide data collection and to determine.
(2) the standardization of measurement.
(3) data for the quantitative understanding of the software process and software process stability.
Improve the direction of
(1) defect prevention. Not only found a problem in a timely manner to improve, and should take specific action to prevent such defects arise in the future.
(2) changes in the management of technology initiatives, identification, selection and evaluation of new technologies. New technologies to enable effective organization in the development of the implementation of
(3) change management process. The purpose of the definition of process improvement, often the process of continuous improvement.
5, optimization level
Features
(1) pay special attention to the software throughout the organization to improve the sustainability of the process, the top view of enhancing their own. To prevent the occurrence of defects and problems. Continuously improve their process capability.
(2) to strengthen the quantitative analysis, through feedback from the quality of the process and absorb new concepts, new technology, so that software process can be improved continuously,
(3) The effect of software process, conduct a cost / benefit analysis, from the successful practice of the software learning process, to sum up. The best results of innovation and rapid transfer to the whole organization. Case of failure by the Software Process Group near line analysis to determine the cause.
(4) organizations to identify and advance the process of improving the shortcomings. To learn from the failure to inform all organizations in order to prevent repeat mistakes.
(5) of the software evaluation process relative standard software process improvement throughout the organization in the promotion.
Process
(1) continue to systematically improve software process
(2) to understand and eliminate the root causes of problems in public. In any one system can be found: As the result of random changes in duplication of work, which led to a waste of time. In order to prevent the waste of manpower may lead to changes in the system. To remove the "public" the invalidity of the root causes to prevent the occurrence of waste. Despite the existence of all levels have these problems, but this is the focus of the fifth grade.
Staff
(1) the existence of the organization as a whole are conscious of the strong sense of team.
(2) that everyone is committed to process improvement. It is no longer in order to achieve success and meet the milestones, and to seek to reduce the error rate.
Technology
Based on the quantitative control and management, taking the initiative in advance of new technologies, the pursuit of new technologies, the use of new technologies. Can be achieved in software development methods and innovative new technologies in order to prevent an error, and continuously improve product quality and productivity.
Metric
The use of data to assess, improve the selection process.
Improve the direction of
To maintain continuous software process improvement.
Second, agile development and high-level CMMI
Keywords: high-level CMMI Agile Development
I often discuss with others the knowledge of Agile development process, and we will always argue a combination of Agile development processes and high-level CMMI topic. Combination of the two of them can use it? Or just the two of them in the opposite direction? With this doubt, together we explore below.
"This issue can be said to be a platitude, but I am on the first 5 levels in the fundamental differences that have a doubt this will make people doubt the mood of unease. CMMI1.2 stressed the importance of control in the organization would like to change the outcome, and its center of gravity shifted to the individual body. Agile development not only in the sense is to enable each project to respond to a wide range of environments the ability to have flexibility and can allow them to do in this environment, the performance of the best. We do not have all the items of particular concern in the irregularities in order to be able to predict the results are "reliable."
However, I am not sure I would like to explain this to the difference between whether it is agile development and the basic concepts of CMMI as a basis for the distinction, or just how the interpretation and implementation of the first CMMI Level 5, a result. Of course, the agile development team in the process model and process of the practice of the assets of the trust appears to have CMMI team than less - While there is no quick way to regulate these things even if they are low-cost, but did not assume that this is organized way to go. In fact, supporters of agile development tend to think so, in any form of the process model can be met quickly to build gradually to reduce the results. Whether this is the same as saying that supporters of agile development believe that the reasons will affect the implementation of the special effects are so widespread, even in an organization trying to establish the predictability of the model is useless? "
CMMI Level No. 4:
QPM (quantitative project management): The main concern about the acts know how to change the course of the individual items, they think that these changes affect their success and how to deal with things - or at least affect the completion of product development or achieve their goals. Organizational units (EPG) results must be monitored.
OPP (practice organization): The main concern about the integrated model, the project can use the model to achieve the success they want to regulate the area, such as quality, schedule, budget, maintenance and any other things. In the process know-how is the project implementation based on these models to control the behavior QPM. Typically, these models may be based on similar projects in the outcome of repeated continuously built up, while there may be no such demand. Level of individual items in the model should be improved in order to use CMMI model in a project based on historical data (for example, incremental) or 20 items of historical data is not differentiated, although this may be the user is differentiated.
CMMI Level No. 5:
CAR (the reasons for analysis and solution): The main concern about the main cause of the problem, negligence, or other management issues need to be addressed. Project, EPG, or whether any other can be applied, as a solution to the problem. EPG monitor the results of the OPP, or get other experiences. (Agile Development in increments starting point or end point is not recommended to carry out similar acts? I am not sure I know the terminology is correct)
OID (Organization Innovation and Promotion): completely non-project features. Concern based on the individual, CAR, model the use of external factors, such as improving the organization. Do you collect and use of all of these lessons learned? After you enter the company will seek new or better ways of doing business (including agile development may be just one example)? In the organization how to deal proved that the analysis of (vocational), and use (please refer to section 4 the structure of the model-level and process control) these improvements.
I personally think that high-level CMMI and Agile development work should be combined. Agile CMMI can help more easily achieve the high-level short-term changes, and it matters in dealing with the development of a very important role. Basically my experience level was from the first 5 years, some from the No. 4 level. With many organizations, "everyone must do so" through the idea of the first 3 levels, but they are opposed to 4,5 in the first level has the same idea. As I have mentioned, the use of agile development is the first CMMI Level 4,5 how to develop products to improve the perfect example.
CMMI is the Capability Maturity Model Integration (Capability Maturity Model Integration) acronym is CMM (Capability Maturity Model Capability Maturity Model) developed from the basis of
Third, CMMI implementation
Now for some reason, many companies want to CMMI, and general practice
1, decided to implement the CMMI
2, EPG training, understanding CMMI
3, EPG according to their own understanding of the CMMI and the actual situation in the development process of a lot of beautiful Liangliang documents, flowcharts, forms, templates, checklists, operating guidelines.
4, all while listening to the interpretation of EPG (including training, Q & A), while the process of implementation of these standards, and audit (internal and external)
The current best practices will be recorded, write it down, and down the document.
Many of the new EPG has been doing for some time found himself helpless as a process of actually reduced the standard guide, and even the administrator documentation. Most of the time they work in the face of the document, or to urge others to write the document
I think that the EPG should be the most important R & D went to the front line to help R & D personnel R & D process to solve the most serious practical problems (of course, solutions to the process of rising to high, and not a single issue or individual), even if it is not serious but the experience of your project to know how to resolve the issue. Overall progress of the project is to master any minor technical difficulties the main points and take the initiative to record.
Why? CMMI main purpose of the implementation of each project is the source for the collection of data to enhance the overall effectiveness and resource reuse. The real value is the need for front-line staff experienced in practical work and solve problems, and summarized the problem, not an itemized account in next line of work. R & D personnel as a daily newspaper. What to do to write morning, afternoon doing. This accumulation of the enterprise what is the use of it? The course of his work, any problems, how he solved a detour through what experimental methods have failed, and the reasons for the failure is, what the final choice methods, may not be the best, but the completion of the task to the resource allocation efficiency and balance. These things can be similar to projects in the future, encounter the same problem, it may be useful. EPG usually career technical accumulation. Only company employees, their view that the accumulation of the most valuable contribution to come out. May reach the company before the accumulation of value. Written form and not every hour of the morning of the itemized account in next afternoon.
Understand that the above said purpose of the CMMI as a qualified EPG, it should have the following qualities:
1, to understand the accumulation of what is valuable, first to you personally, then so as to help the company to do the accumulation.
2, in-depth first-line and found them and record them faithfully. CMMI in the SP, GP, just to help you to remind you which aspects of what may be a valuable. To collect about you, do not turn a blind eye to the. Because there is a business and your personal point of view is different from the position of different problems. For example, REQM in the collection of demand for the accumulation of personal technologies, while small, is essential for enterprise, one needs to change, no detail was clear that customers have forgotten to sign the implementation, may be caused to the enterprise great loss. As a qualified EPG, is the need to have the responsibility and obligation to do Each and every element of the best, this is where professional ethics. But also for self-extension of a good opportunity to learn some and communication, listen to what the professional manner in order to easy. These are also regarded as an additional harvest EPG.
Under normal circumstances, in order to complete the project on time and according to the volume of the first line of the backbone of writing daily, weekly, documents are disdained. EPG is also very accommodating after the qualification, which is a good way to improve efficiency. But half a year over the past month, we can imagine the memory of normal people, it is difficult to remember details. Nothing more than perfunctory. It is also reasonable. You can not make a thing tomorrow will be cross-group in the night tonight at the same time efforts to resolve the BUG, but also what kind of report writing, which is not human. However, as the EPG can not just focus on this woman's mind. The farther to. Why would so late to the project, BUG END no solution? Are we going to ever do it? Projects there are many unpredictable factors, and even developers often said "I'm Feeling" and "character problem." But these are the need to control, but also can be controlled through the experience, the so-called expert bold art. The level of art is determined by the accumulation of experience.
The dilemma of how to address this problem? Forcing the heart to write the technical backbone of water, others did not have time under immense pressure. Not written, the company also is not effectively the accumulation of all refuse accumulated water. There is a company's approach and experience that you can learn from:
Company engaged in a BBS, the different types of work is divided into different groups, there are purely technical, JAVA Group, C + + groups, there are PPT group, and even animation group, interface group. We usually work themselves up the accumulation of FTP, and even the production of methods, problems and solutions are throwing up the document, how would like to start with the number of sets of programs, what the final choice. How to feel. The mentality of all these written documents. Thrown into the sun, we commented. With click-through rate and the "top" to indicate the number of people who wrote the heart of water, who refuse to write. We are a company, it is easy to real names. Directly into the assessment mechanism. As a front-line staff, we also have an incentive to write and have demonstrated their wisdom and talent of the platform, vanity and wallet have been appropriate to meet. Why not do it?
EPG timely assessment of all the results and share their projects. To help the project summary, even in peacetime problems, direct assistance and technical personnel to do the necessary records. Song project when project personnel to improve the content of supervision. In order to achieve the accumulation of individuals and companies to maximize.
EPG should be aware that the accumulation of learning and is a lifelong process, the company's case, The same is true of individuals. CMMI is a supplementary, auxiliary, we have accumulated on the company, but also help us to make the necessary accumulation of the individual. Companies need to gradually moving towards a higher management level, the development platform.
Fourth, CMMI implementation of the core
Keywords: CMMI, SCAMPI, Process Improvement, Capability Maturity, EPG, PA, the process of domain
Section in the previous chapter, we talked about the team on the formation of process improvement methods and process in the formation of issues requiring attention in this section we will continue to explore another EPG process improvement is more important - the definition of the process of document.
Appraisers have a joke that was written three documents, the document is written in four documents, five of the document is written documentation of the document. This shows that the document throughout the CMMI, process improvement in a pivotal role to play. So how can we write is in line with the CMMI and based on the actual situation in their enterprises this document? This is what this article will explore the issue - the definition of the process of documentation.
Documents in the definition of the process, first of all, the habit of enterprises should be expressed with the terminology and language CMMI mapping between. Organizational structure in particular some of the terminology, the role of the relationship between the organization and the formulation process of the activities need to mapped to the corresponding part of the organization in order to prevent other people can not understand.
The definition of the general steps the process of documentation is:
(1) to identify and describe the product life cycle.
In general, the product life cycle can be divided into six stages, namely the product concept stage, the product definition phase,
Product development stage,
Stage of product testing, user acceptance stage, product maintenance phase.
(2) According to the product life-cycle needs to be improved at all stages of the process to determine the domain (PA) activities.
"The process of domain" is used to describe the standard definition of CMMI software process capability assessment model of a component. In the model, "the process of domain" is the biggest building block of each "process domains" by a group of objectives that each goal has been to support a group practice. Model of the process described in reference to the template, using "process domains" to that. Can not be confused with the actual process. "The process of domain" is not a practical process, it is a model template.
(3) the process for a PA activities, the completion of the data flow chart of PA.
(4) to prepare the corresponding template, checklist or method definition of the process of the annex to the document. Internal discussions in the EPG and then modified, and then show reviewers who read and, finally, a formal assessment. Further amended, then the assessment until the date we approved, and then move on to the next process of a PA. (Or, alternatively, after the enactment of the pilot assessment, the pilot of a successful re-entry process to have a PA.)
According to their years of consulting experience, summed up the definition of the process in general easier to document problems.
1, "the localization is not doing enough"
Consultants are often found in items such issues: the definition of a PA in the process, customers will be over-reliance on advice provided by a number of other enterprises in the process of documentation, these documents will be adjusted as a tip of the process of its own document. Since each software companies is not the same, process, standardization, and record companies should be based on the actual situation to develop, in the light of CMMI framework, the development of the situation for the company itself, "localization" process system, such an effect will be even better.
(2) the overall grasp, and gradually refining
PA in the process of definition of the first, if not take it with the other the relationship between the PA directly reference the CMMI objectives of the PA to complete the process and practice document the results that may occur either through the assessment, or through the following return to be amended. As a result of close ties between the PA, are closely related, so the actual definition of the process, we must grasp the overall relationship between the PA to complete the whole process flow chart based on the data further broken down step by step, otherwise, that is, "only see for the trees. "
(3) more exchanges summary
Early in the project as a result, EPG group enough for a thorough understanding of CMMI, it is no experience, which requires EPG members, QA, management, development of exchanges between the many, in the definition of when the course of the discussion document, set all the wisdom, With the progress of process definition, EPG group to deepen the understanding of the CMMI, we need to sum up experience, to avoid similar problems in the face of the future when the number of detours.