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

SG 4 Develop a Test Plan

SG4 开发测试计划

A test plan is established and maintained as the basis for managing testing and communication to

stakeholders.

测试计划被建立和维护，作为管理测试和与相关人员通讯的基础。

SP 4.1 Establish the test schedule

SP 4.1 建立测试时间表

The test schedule with predefined stages of manageable size is established and maintained based on

the developed test estimate and defined test lifecycle.

在已开发的测试评估和已定义的测试生命周期基础上，测试时间表和预定义的可管理大小的阶段被建立和维护。

Typical work products

典型工作产品

1. Test schedule

1. 测试时间表

Sub-practices

1. Identify test scheduling constraints such as task duration, resources, and inputs needed

2. Identify test task dependencies

3. Define the test schedule (timing of testing activities, test lifecycle phases and test milestones)

4. Document assumptions made in defining the test schedule

5. Establish corrective action criteria for determining what constitutes a significant deviation from the

test plan and may require rescheduling.

子实践

1. 确定测试时间表约束条件，如任务周期，资源，必要的输入等

2. 确定测试任务依赖

3. 定义测试时间表（测试活动时间，测试生命周期阶段和测试里程碑）

4. 在定义测试时间表时记录假定条件

5. 建立矫正的行动标准，以决定什么构成源自测试计划的重大偏离，可能需要重新计划

SP 4.2 Plan for test staffing

SP 4.2 测试人员计划

Plan for necessary test staffing resources with the required knowledge and skills to perform the

testing.

计划必要的拥有相关知识和技能的测试人力资源，以执行测试工作。

Typical work products

1. Staffing requirements

2. Inventory of skill needs

3. Staffing and new hire plan

4. Test training plan

典型工作产品

1. 所需人员编制

2. 所需技能的详细清单

3. 新聘用人员编制和计划

4. 测试培训计划

Sub-practices

1. Determine staffing requirements based on the work breakdown structure, test estimate and test

schedule

2. Identify knowledge and skills needed to perform the test tasks

3. Assess the knowledge and skills available

4. Select mechanisms for providing needed knowledge and skills

子实践

1. 在工作分解结构，测试评估和测试时间表的基础上决定人员编制

2. 确定所需的知识和技能，以执行测试任务

3. 评估现有的知识和技能

4. 提供必需知识和技能的选择机制

Examples of mechanisms include the following:

? In-house training

? External training

? Coaching

? External skill acquisition

选择机制的例子包括如下：

 内部培训 外部培训 教练 外部技能获取

5. Incorporate selected mechanisms into the test plan

5. 把选择机制合并到测试计划中

SP 4.3 Plan stakeholder involvement

SP 4.3 计划相关人员参与

Plan the involvement of identified stakeholders.

计划已明确的相关人员参与

Stakeholders are identified from all phase of the test lifecycle by identifying the type of people and

functions needing, representation in testing activities and describing their relevance and the degree of

interaction for specific testing activities. A two-dimensional matrix with stakeholders along one axis

and testing activities along the other axis is convenient for accomplishing this identification.

相关人员被确定，从测试生命周期的所有阶段，通过明确人员的类型和功能需要，在测试活动的表现，描述他们的关联和与特定测试活动交互的深度

Typical work products

典型工作产品

1. Stakeholder involvement plan

1. 相关人员参与计划

SP 4.4 Identify test project risks

SP 4.4 明确测试项目任务

The test project risks associated with testing are identified, analyzed and documented.

测试项目任务被确定，分析和存档

Typical work products

1. Identified test project risks

2. Prioritized test project risk list

3. Test project risk contingencies

典型工作产品

1. 确定测试项目任务

2. 确定测试项目任务的优先次序

3. 测试项目风险应急

Sub-practices

1. Identify test project risks

子实践

1. 确定测试项目风险

Examples of project risk identification techniques include the following:

? Brainstorming

? Expert interviews

? Checklists

项目风险辨认技术包括如下：

 脑力激荡 专家评审 检查单

2. Analyze the identified test project risks in terms of likelihood and impact

3. Prioritize the analyzed test project risks

4. Review and obtain agreement with stakeholders on the completeness and priority level of the

documented test project risks

5. Define contingencies for the (high priority) test project risks

6. Revise the test project risks as appropriate

2. 分析已确定的测试项目风险，就可能性和影响而言

3. 确定已分析的项目风险的优先级

4. 对已存档的测试项目风险的完整性和优先级进行评审并获得相关人员的一致同意

5. 对（高优先级的）测试项目风险定义应急措施

6. 适当的时候修订测试项目风险

Examples of when test project risks may need to be revised include:

? When new test project risks are identified

? When the likelihood of a test project risk changes

? When test project risks are retired

? When testing circumstances change significantly

何时需要修订测试项目风险包括如下：

 当新的测试项目风险被定义时

 当测试项目风险可能改变时

 当测试项目风险被撤掉时

 当测试环境显著改变时

SP 4.5 Establish the test plan

SP 4.5 建立测试计划

The test plan is established and maintained as a basis for managing testing.

The results of previous practices are documented in an overall test plan, tying together the information

in a logical manner.

测试计划被建立和维护，作为管理测试的依据。

之前实践的结果被记录在总体的测试计划中，用合乎逻辑的方式把这些信息捆绑在一起。

Typical work products

典型工作产品

1. Test Plan

1. 测试计划

Examples of elements of a test plan include the following [after IEEE 829]:

? Test plan identifier

? An overall introduction

? Non-compliances to the test strategy and its rationale

? Items to be tested (including priority level) and not to be tested

? Features to be tested (including priority level) and not to be tested

? Test approach (e.g. test design techniques)

? Entry and exit criteria

? Suspension and resumption criteria

? Test milestones and work products

? Test lifecycle and tasks

? Environmental needs and requirements (including office environment)

? Staffing and training needs

? Stakeholder involvement

? Test estimate

? Test schedule

? Test project risks and contingencies

Refer to the “Test Environment” process area for information on environmental needs and

requirements.

测试元素包括如下（在IEEE 829之后）

 测试计划标识

 总体介绍

 对测试策略的违背，并列出理由

 需要测试和不需要测试的条目（包含优先级）

 需要测试和不需要测试的功能（包含优先级）

 测试方法（如测试设计技术）

 进入和退出标准

 暂停和恢复标准

 测试里程碑和工作产品

 测试生命周期和任务

 环境的需要和要求（包括办公环境） 人员配置和培训需求 相关人员的参与 测试评估 测试时间表 测试项目风险和应急措施环境的需要和要求的信息请参考“测试环境”过程域。