TMMI_测试过程改进框架_优化级别8_缺陷预防1

PA 5.1 Defect Prevention 缺陷预防

Purpose

The purpose of Defect Prevention is to identify and analyze common causes of defects across the development lifecycle and define actions to prevent similar defects from occurring in the future.

缺陷预防的目的是明确和分析开发生命周期中常用的缺陷原因和定义行动来阻止类似的缺陷在将来发生。

Introductory Notes

In line with the evolutionary test model [Gelperin and Hetzel], testing at TMMi level 5 completes its journey from being detection-focused to being a prevention-focused process. In line with this view of testing, testing is focused on the prevention of defects that otherwise might have been introduced rather than just their detection during testing activities. Defect Prevention involves analyzing defects that were encountered in the past, identifying causes and taking specific actions to prevent the occurrence of those types of defects in the future. The selection of defects to be analyzed should be based on various factors including risk. Focus needs to be given to those areas where prevention of defects has the most added value (usually in terms of reduced cost or risk) and/or where the defects are most critical. Attention should be given to both existing types of defects as well as new types of defects such as defects that are new to the organization but are known to occur in the industry. Defect Prevention activities are also a mechanism for spreading lessons learned across the organization, e.g., across projects.

符合进化的测试模型，TMMI5中的测试完成了聚焦发现缺陷到预防缺陷的历程。为了符合这种测试观点，测试会集中注意力在缺陷预防上，这些缺陷很可能是被引入的而不是发现的。缺陷预防包括分析之前遇到到bug。明确原因和采取特定的行动来预防将来同类bug出现的。选择的要分析的缺陷应该基于多种多种因素，比如风险。应该注意缺陷预防具有最大的附加值的地方。以及关键缺陷的地方。应该注意哪些已经存在的缺陷类型，同时要关注行业类著名的对组织比较新的问题类型。缺陷预防活动也是一种机制在组织内传播知识。

Defect Prevention improves quality and productivity by preventing the introduction of defects into a product. Industry data shows that reliance on detecting defects after they have been introduced is usually not cost effective [Boehm]. It is usually more cost effective to prevent defects from being introduced by integrating Defect Prevention practices into each phase of the project. At TMMi level 5, an organization will know which is more cost effective, prevention or detection of a certain type of defect. Many process improvement models emphasize the use of causal analysis as a means of continually improving the capability of the process. Examples of methods for causal analysis are specific causal analysis meetings, using tools such as fault tree analysis and cause/effect diagrams, project retrospectives, causal analysis during formal reviews, and usage of standard defect classifications.

缺陷预防提高了质量和生产力通过阻止引入缺陷到产品。行业数据显示在问题引入以后依赖缺陷发现通常不会消耗效率。通常更加消耗效率，阻止缺陷通过集成缺陷预防实践到项目的每一个阶段。在tmmi5，组织应该知道哪些更加消耗效率，预防或发现一些缺陷类型。很多过程提升模型强调使用因果分析作为持续提升流程成熟的方式。，特定因果分析会议，使用工具比如缺陷树和因果图，项目原型图，因果分析通过正式的重审，标准缺陷分类用法。

Defect Prevention is a mechanism to evaluate the complete development process and identify the most effective improvements regarding product quality. As part of the Defect Prevention practices, trends are analyzed to track the types of defects that have been encountered and where they were introduced, and to identify defects that are most likely to reoccur. A (test) measurement process is already in place having been introduced at level 4. The available measures can be used, though some new measures may be needed to analyze the effects of the process changes. Based on an understanding of the organization’s defined standard development and test process and how it is implemented, the root causes of the defects and the implications of the defects for future activities are determined. Specific actions are defined and taken to prevent reoccurrence of the identified defects. Defect Prevention is an essential part of a mature test process. Defects found during development, testing or even during production must be systematically analyzed, prioritized and action must be undertaken to prevent them from occurring in the future. The test organization coordinates the Defect Prevention activities. This should be done in close cooperation with other disciplines, e.g., requirements engineering, system engineering and/or software development, as improvement actions will often affect other disciplines.

缺陷预防是一种机制来评估开发过程的完成和明确最有效的产品质量提升方法。作为缺陷预防实践的一部分，趋势被分析来监察遇到的缺陷类型和这些缺陷是哪里引入的，已经明确那些经常重现的缺陷。测试测量过程已经在TMMI4被引入。可用的测量被使用。虽然一些新的测量可能需要分析过程改变的影响，基于组织定义的标准开发和测试流程，已经如何实施，缺陷的原因，缺陷对未来工作的含义，等等的一致理解被确定。特定的行动被定义和实施来阻止明确缺陷的再次出现。缺陷预防是成熟测试过程的重要部分。在开发，测试和产品上线发现的缺陷应该系统的分析，分优先级，行动应该被采取来阻止他们将来发生。测试组织协调缺陷预防行为。它应该和其他标准配合。需求工程，系统工程，软件开发，作为提升行文通常影响其它行为。

Scope

The process area Defect Prevention addresses the practices for identifying and analyzing common causes of defects, and defining specific actions to remove the common causes of those types of defects in the future, both within the project, and elsewhere in the organization. All defects, whether found during development, testing or in the field, are within the scope of the process area. Process defects that have resulted in outliers and not meeting expected process performance also are within the scope. Since Defect Prevention needs measurement data and measurement processes as an input, Defect Prevention builds on the TMMi level 4 measurement practices and available measurement data regarding development, testing and product quality.

缺陷预防过程域追踪实践来明确和分析问题的常见原因，定义特定的行动来避免这类将来出现问题的原因。不管是组织还是项目，所有的缺陷，是否在开发发现，在测试或者其它地方发现。都是这个过程域的范围。哪些引起异常值的缺陷和没有满足期望过程性能的问题也在这个范围内。因为缺陷预防需要测量数据和测试过程作为输入，缺陷预防在TMM4测量实践被建立，已经建立在可用的测量数据（开发，测试和产品质量）

Specific Goals and Practice Summary

SG 1 Determine Common Causes of Defects 明确常见的问题原因

SP 1.1 Define defect selection parameters and defect classification scheme SP 1.2 Select defects for analysis SP 1.3 Analyze causes of selected defects 

SG 2 Prioritize and Define Actions to Systematically Eliminate Root Causes of Defects 分级和定义行为来系统地减少缺陷主要原因。

SP 2.1 Propose solutions to eliminate common causes SP 2.2 Define action proposals and submit improvement proposals