TMMI_测试过程改进框架_管理级别5

TMMi Level 2: Managed

TMMI2,可管理级别

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 proven practices are retained during times of stress. However, testing is still perceived by many stakeholders as being a project phase that follows coding.

在TMMI2级别，测试变成可管理的过程并且和调试清晰的分开。成熟等级2所反映出来的过程纪律帮助保证了在时间压力下，已经证明的实践被进行下去。然鹅，测试任然被很多相关人认为是项目coding后面的一个阶段。

In the context of improving the test process, a company-wide or program-wide test strategy is established. Test plans are also 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. Test design techniques are applied for deriving and selecting test cases from specifications. However, testing may still start relatively late in the development lifecycle, e.g., during the design or even during the coding phase.

为了提高测试流程，一个公司范围或者程序范围的测试策略被建立，测试计划被开发出来。在测试计划里测试方法被定义。测试方法是基于产品风险评估的结果的。风险管理技术被使用来鉴别（验证）基于文档需求产品风险。测试计划定义了我们需要测试上面，什么时候测试，如何测试，谁来测试。承诺被相关责任人建立并且按照需求修正。测试被监控，以保证它按照测试计划进行并且出现危机有相应处理机制。工程产品状态和测试服务输出是对管理层是可见的。测试设计技术被使用来从规格说明书中提取和选择测试用例。然鹅，测试任然在开发生命周期中开始较晚。比如，在设计阶段甚至在代码开发阶段。

In TMMI level 2 testing is multi-level: there are component, 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 processes of testing and debugging are differentiated.

在TMMI2中测试是多个等级的。包括组件，集成，系统和可接受测试等级。对于每一个验证测试等级，有很多特定测试目标被组织界别或者程序级别测试策略所定义。测试流程和调试流程是有区别的

The main objective of testing in a TMMi level 2 organization is to verify that the product satisfies the specified requirements. 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 still considered by many stakeholders the primary testing activity.

TMMI2组织的主要测试目标是验证产品是否符合指定的需求。许多质量问题在这个等级出现是因为测试出现在开发周期的晚期。缺陷在需求阶段被繁衍并且被设计到代码里。这里没有正式的复审去解决这个问题。在代码以后，基于执行的测试任然被很多相关责任人认为是测试的主要活动。

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  测试设计和执行

.5 Test Environment  测试环境

Each of these is discussed in more detail in the sections hereafter.