翻译：测试成熟度模型集成（TMMi）（9）

TMMi Level 2: Managed
TMMi2级：管理级
In level 2, testing becomes a managed process and is clearly separated from debugging. The process discipline
reflected by maturity level 2 helps to ensure that existing practices are retained during times of stress. However, it
is by many stakeholders still perceived as being a project phase that follows coding. In the context of improving the
test process, a company-wide or program-wide test strategy is established. Test plan are also being developed.
Within the test plan a test approach is defined, whereby the approach is based on the level of risk. Risk
management techniques are used to identify the product risks based on documented requirements. The test plan
will define what testing is required, when, how and by whom. Commitments are established among relevant
stakeholders and revised as needed. Testing is monitored and controlled to ensure it is going according to plan and
actions can be taken if deviations occur. The status of the work products and the delivery of testing services are
visible to management. For deriving and selecting test cases from specifications test design techniques are
applied. However, testing may still start relatively late in the development lifecycle, e.g. during the design or even
during the coding phase. Testing is multi-leveled: there are unit, integration, system and acceptance test levels. For
each identified test level there are specific testing objectives defined in the organization-wide or program-wide test
strategy. The main objective of testing in a TMMi level 2 organizations is to verify that the product satisfies the
specified requirements. The purpose is also to clearly differentiate the processes of testing and debugging. Many
quality problems at this TMMi level occur because testing occurs late in the development lifecycle. Defects are
propagated from the requirements and design into code. There are no review programs as yet to address this
important issue. Post code, execution based testing is by many stakeholders still considered the primary testing
activity.
在第2级，测试成为了管理过程，并明确地从调试中分开。由成熟度2级反射出的过程训练有助于确信在时间压力下，现行惯例被保留。然而，许多利益相关者仍然感觉它是编码过后的一个阶段。在改进测试过程的背景下，一个公司范围或者产品范围的测试策略被建立了。测试计划也被制定。在测试计划中，测试方法被定义，该方法基于这个级别的风险。风险管理技术被用来识别基于文档化需求的产品风险。测试计划将会定义需要测试什么，什么时候测试，如何测试以及有谁来测试。在利益相关者中间建立承诺，并根据需要修改。测试过程被监控以确保它按照计划执行，一旦有背离发生会有相应的动作。工作产品的状态和测试服务的递交对管理来说是可见的。从详细规格说明中选择测试用例的测试设计技术被应用了。然而，在开发生命周期测试仍然开始的比较晚，比如要在设计或者在编码阶段才开始。测试分了多个层次，有单元测试，综合测试，系统测试和验收测试。对于每个确定的测试层次有指定的测试目标定义在组织范围或者产品范围的测试策略。2级TMMi组织的主要测试目标是检验产品是否符合指定的需求。还有一个目的是清楚地界定测试和调试。这个级别的TMMi有许多的质量问题是因为测试
启动太晚。缺陷被引入从需求阶段，设计阶段到编码阶段。没有正式的评审程序去定位这个重要的问题。许多人认为编码过后的测试执行是主要的测试活动。
The process areas at TMMi level 2 are:
2.1 Test Policy and Strategy
2.2 Test Planning
2.3 Test Monitoring and Control
2.4 Test Design and Execution
2.5 Test Environment
2级TMMi有过程域如下：
2.1 测试政策和策略
2.2 测试计划
2.3 测试监控
2.4 测试设计和执行
2.5 测试环境

PA2.1 Test Policy and Strategy
PA2.1 测试政策和策略
Purpose
目标
The purpose of Test Policy and Strategy is to develop and establish a test policy and an organization-wide or
program-wide test strategy in which the test levels are unambiguously defined. To measure test performance, test
performance indicators are introduced.
测试政策和策略的目标是开发和建立测试策略和组织范围或者产品范围的策略，在此测试级别被明确定义。为了衡量测试性能，测试性能指标被引入。
Introductory Notes
介绍性说明
When an organization wants to improve its test process, it should first clearly define a test policy. The test policy
defines the organization’s overall test objectives, goals and strategic views regarding testing. It is important that the
test policy is aligned with the overall business (quality) policy of the organization. A test policy is necessary to attain
a common view on testing between all stakeholders within an organization. This common view is indispensable to
align test (process improvement) activities. The test policy should address both new development and maintenance
testing activities. Within the test policy the objectives for test process improvement should be stated. These
objectives will subsequently be translated into a set of key test performance indicators. The test policy and the
accompanying performance indicators provide a clear direction, and a means to communicate expected and
achieved levels of test performance. The performance indicators have the objective to show the value of testing
and test process improvement to stakeholders.
当组织想改进它的测试过程的时候，它首先应该清楚的定义测试政策。测试政策定义了组织总体测试目的，目标和测试相关的战略视图。重要的是测试政策与组

织的商业（质量）政策相一致。测试政策有必要对组织所有相关人员实现一个统一的测试视图。这个统一的测试视图对于测试活动（过程改进）是必需的。测试

政策必须实现新的开发，和维护测试活动。在测试政策中，测试过程改进的目标需要被说明。随后这些目标将会转成一套关键性能指标。测试政策及其相随的性

能指标提供了明确的指示，沟通的方法，以期望和实现测试的性能级别。性能指示器客观的向相关人员展示了测试和测试过程改进的数值。
Based upon the test policy a test strategy will be defined. The test strategy covers the generic test requirements for
an organization or program (one or more projects). The test strategy addresses the generic product risks and
presents a process for mitigating those risks in line with the testing policy.

The test strategy therefore starts by
performing a generic product risk assessment studying the products being developed within a program or
organization. A typical test strategy will include a description of the test levels that are to be applied, for example:
unit, integration, system and acceptance test. For each test level amongst others the objectives, responsibilities,
main tasks and entry/exit criteria are defined.

The test strategy serves as a starting point for the testing activities
within projects. The projects are set up in accordance with the organization-wide or program-wide test strategy.
When a test strategy is defined and followed, less overlap between the test levels is likely to occur leading to a
more efficient test process. Also since the test objectives and approach of the various levels is aligned fewer holes
are likely to remain leading to a more effective test process.
在测试政策的基础上定义了测试策略。测试策略包含了组织或者产品（一个或多个项目）的通用测试需求。测试策略解决了通用产品风险，提出了减轻风险并与

测试政策相一致的过程。因此测试策略通过执行通用产品风险评估--研究在产品或者组织内的正在被开发的产品。一个典型的测试策略包括需要被实现的测试类

别的描述，例如，单元测试，综合测试，系统测试和验收测试。对于每个测试类别中的人的目标，职责，主要任务和进入/退出标准被定义。测试策略作为项目测

试活动的起始点。项目依照组织范围或者产品范围的测试策略被建立。当测试策略被定义且被遵守的时候，测试类别只有少的重叠，且会导向一个更加有效的测

试过程。此外，由于测试的目标和各个层次的做法是一致的，较少的漏洞被遗留，这也会导致更有效的测试过程。
Scope
范围
The process area Test Policy and Strategy involves the definition and deployment of a test policy and test strategy.
Within the test strategy, test levels are identified. For each test level, amongst other test objectives, responsibilities
and main tasks are defined. To measure test performance and the accomplishment of test (improvement) goals,
test performance indicators are defined and deployed.
测试政策和策略过程域包括测试政策和测试策略的定义和部署。在测试策略中，测试级别被定义。对于每个测试级别，其中包括的测试目标，职责和主要任务被

定义。为了测量测试性能和测试（改进）目标的完成度，测试性能指标被定义和部署。
Specific Goal and Practice Summary
SG1 Establish a test policy
SP 1.1 Define test goals
SP 1.2 Define test policy
SP 1.3 Distribute the test policy to stakeholders
SG2 Establish a test strategy
SP 2.1 Perform a generic product risk assessment
SP 2.2 Define test strategy
SP 2.3 Distribute the test strategy to stakeholders
SG3 Establish test performance indicators
SP 3.1 Define test performance indicators
SP 3.2 Deploy test performance indicators
具体目标和实践小结
SG1 建立测试政策
SP1.1 定义测试目标
SP1.2 定义测试政策
SP1.3 分配测试政策到相关人员
SG2 建立测试策略
SP2.1 执行通用产品风险管理
SP2.2 定义测试策略
SP2.3 分配测试策略到相关人员
SG3 定义测试性能指标
SP 3.1 定义测试性能指标
SP 3.2 实施测试性能指标