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

2.2 Level 1 Initial
2.2 级别1 初始的
At TMMi level 1, testing is a chaotic, undefined process and is often considered a part of debugging. The
organization usually does not provide a stable environment to support the processes. Success in these
organizations depends on the competence and heroics of the people in the organization and not the use of
proven processes.Tests are developed in an ad-hoc way after coding is completed. Testing and debugging are
interleaved to get the bugs out of the system. The objective of testing at this level is to show that the
software runs without major failures. Products are released without adequate visibility regarding quality
and risks.
In the field, the product does often not fulfill its needs, is not stable, or is too slow to work with.

Within testing there is a lack of resources, tools and well-educated staff. At TMMi level 1 there are no

defined process areas. Maturity level 1 organizations are characterized by a tendency to over commit,

abandonment of processes in a time of crises, and an inability to repeat their successes. Also products

tend not to be released on time, budgets are overrun and quality is not according to expectations.
在TMMi级别1，测试是个混乱，无定义的过程，常常被当作调试的一部分。组织通常没有提供稳定的环境来支持这个过程。

组织的成功都是依靠能力超强英雄式的人物，而不是使用被证实的过程。在代码完成之后测试被一个特别的方式展开。测

试和调试被混合到一起来去除系统中的错误。这个级别的测试目标是软件运行起来后没有大的失效。关于质量和风险产品

没有足够清晰就被发布。实际应用时，产品经常不符合需求，不稳定或者工作太慢。测试缺少资源，工具和训练有素的人

员。在TMMi级别1没有定义过程域。成熟度级别1的组织的特征是倾向于过度承诺，危机时放弃过程，无法重复成功。产品

往往不按时发布，超支，质量不可预料。
2.3 Level 2 Managed
2.3 级别2 可管理的
At TMMi 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, testing 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 plans are also being developed. Within the test plan a test approach is defined, whereby

the approach is based on the result of a product risk assessment. Risk management techniques are used to

identify the product risks based on documented requirements. The test plan defines what testing is

required, when, how and by whom. Commitments are established with 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 formal review programs as

yet to address this important issue. Post code, execution based testing is by many stakeholders still

considered the primary testing activity.
在TMMi级别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
TMMi级别2有如下过程域：
2.1 测试方针和策略
2.2 测试计划
2.3 测试监控
2.4 测试设计和执行
2.5 测试环境