TMMI_测试过程改进框架_已定义级别6_测试生命周期和集成4

SG 3 Establish a Master Test Plan 建立主测试计划

A master test plan is established to define a coherent test approach across multiple test levels and an overall test planning.

主测试计划被建立来定义一系列跨越不同测试等级的测试方法和完整测试计划。

SP 3.1 Perform a product risk assessment 执行产品风险评估

A product risk assessment is performed to identify the typical critical areas for testing. Example work products 1. Product risk list, with a category and priority assigned to each risk Sub-practices 1. Identify and select stakeholders that need to contribute to the product risk assessment 2. Identify generic product risks using input from stakeholders 3. Document the context and potential effects of the product risk 4. Identify the relevant stakeholders for each product risk 5. Review the identified product risks against the test assignments 6. Analyze the identified product risks using the predefined parameters, e.g., likelihood and impact 7. Categorize and group product risks according to the defined risk categories 8. Prioritize the product risks for mitigation 9. Review and obtain agreement with stakeholders on the completeness, category and priority level of the product risks 10. Revise the product risks as appropriate Refer to SG 1 Perform a Product Risk Assessment from the process area Test Planning for more details on the (sub) practices for performing the product risk assessment.

产品风险评估被执行来验证需要测试的典型的关键区域。

例子工作产品：1. 产品风险列表，以及对于每一个风险的分类和优先级。

子实践：1.明确和选择利益相关人，他们需要对产品风险评估做出贡献。 2. 明确通用产品风险，使用利益相关人的输入。3.文档化产品风险的背景和潜在的影响。4.为每一个产品风险明确相关利益人。5.基于测试分配重审已经明确的产品风险。6分析已经明确的产品风险。7.为产品风险分类，基于已经定义的风险类别。 8.为产品风险分优先级。 9.重审和获得完整性的一致观点。10.修改。

SP 3.2 Establish the test approach 建立测试方法

The test approach is established and agreed upon to mitigate the identified and prioritized product risks. Example work products 1. Test approach 2. List of items to be tested and not to be tested 3. List of features to be tested and not to be tested 4. Identified set of test levels 5. Allocation table of test items/test features/product risk to test levels 6. Entry criteria per test level 7. Exit criteria per test level Sub-practices 1. Identify and document the items and features to be tested, and not to be tested, based on the product risks. Note that the level of aggregation of the test items and test features is likely to be higher during master test planning than at planning for an individual test level. 2. Identify the test levels that are needed to mitigate the product risks 3. Allocate the items and features to be tested as well as the product risks to the identified test levels 4. Select the test design techniques to be used at various test levels; multiple test design techniques are defined to achieve appropriate test coverage based on the defined product risks 5. Define the approach to review test work products 6. Define the approach for re-testing and regression testing 7. Identify the supporting test tools to be used 8. Identify significant constraints regarding the test approach 9. Define a set of entry criteria related to the test process and to product quality for each identified test level 10. Define a set of exit criteria related to the test process and to product quality for each identified test level 11. Align the test approach with the defined organization-wide or program-wide test strategy 12. Identify any non-compliances with the test strategy and the rationale for the variance 13. Review the test approach with stakeholders 14. Revise the test approach as appropriate Refer to SG 2 Establish a Test Approach from the process area Test Planning for more details on the (sub) practices for establishing the test approach.

测试方法被建立和批准来减少明确的和高优先级的产品风险。

例子工作产品：测试方法，需要测试和不需要测试的列表，需要测试的功能和不需要测试的功能列表，明确的测试等级，为不同的测试等级分配测试项目，功能，风险。不同测试等级进入标准，不同测试等级的出标准。

子实践：1.明确和文档化需要测试的功能项。不需要测试的，基于产品风险。2 明确需要的测试等级来减少产品风险。3.分配需要测试的项目和功能点，还有已经明确测试等级的产品风险。4.选择不同测试等级的测试设计技术。不同的测试设计技术被定义来达到适当的测试覆盖率，，基于产品风险。5.定义方法来重审测试工作产品。6.定义方法来重新测试和回归测试。7.明确支持测试工具。8明确明显的约束，基于测试方法。

SP 3.3 Establish test estimates 建立测试里程碑

Well-founded test estimates are established and maintained for use in discussing the test approach with stakeholders and in planning the testing activities. Note that early in the development lifecycle, the required information may not all be available to establish a firm test estimate. As a consequence, the accuracy of the test estimate is limited. It is important for the test manager to make it clear to the stakeholders that the test estimate will have to be finalized, and possibly refined, later on in the lifecycle when more information is available. Example work products 1. Work breakdown structure (WBS) 2. Selected test lifecycle model 3. Test effort estimates 4. Test cost estimates Sub-practices 1. Select a test lifecycle model from the organization’s standard set on which to scope the planning effort 2. Establish a top-level work breakdown structure based on the defined test approach to clearly define the scope of the test estimate 3. Estimate the test effort and cost for the test work products and tasks based on estimation rationale, e.g., test metrics from the test process database 4. Align the estimated test effort and costs with the overall estimated project effort and costs Refer to SG 3 Establish Test Estimates from the process area Test Planning for more details on the (sub) practices for establishing test estimates.

良好的测试评估被建立和维护供使用来和相关利益人讨论测试方法和计划测试行为。在开发生命周期的早期。对于建立一个稳定的测试评估，不是所有的信息都是有用的。因此，测试评估的正确性被限制。测试经理向相关利益人解释清楚评估不是最终版本很重要。可能是精炼的。后期生命周期更多信息会有用。

例子工作产品：1.工作细分架构。2.选择测试生命周期模型。3，测试工作评估，4.测试消耗评估。

子实践：1.从组织标准设置选择测试生命周期模型。2.建立高级工作细分架构，基于定义的测试方法来清晰定义测试评估的范围。3.为测试工作产品和任务评估测试工作和消耗，基于评估理论。4.保持测试工作和消耗的评估与整体项目工作和评估一致。

SP 3.4 Define the organization for testing 定义测试组织

The organization of the testing at the various levels is defined, including the interfaces to other processes, and a clear overview of what is expected from the various parties involved is established. The relationship of testing to other processes such as development, project management, quality assurance, and configuration management is determined and described. This includes the lines of communication within the test organization, the authority for resolving issues raised by testing, and the authority for approving test products and processes. This may include a visual representation, e.g., an organizational chart. Example work products 1. Description of the test organization Sub-practices 1. Determine the test roles at various test levels to ensure alignment between the various test levels 2. Define authorities and responsibilities for the various test roles, products and processes 3. Define the organizational structure, e.g., the relationship between the various roles, the identified test levels and the other stakeholders within the development process 4. Define the communication structure (e.g., meetings and reports), both within testing and with external stakeholders

不同等级的测试组织被定义。包括其他流程的接口，和一个清晰的关于从各种关联部门的期望整体回顾被建立。其他流程的测试的关系，比如开发，项目管理。质量保证，和配置管理被决定和描述。包括和测试组织沟通。测试中问题解决权威性。批准测试产品和流程的权威性。它可能包含可见代表。比如，组织表。

例子工作产品。1.测试组织描述。

子实践：1.决定在不同测试等级中测试的角色来保证在不同等级中的一致性。2.为不同的测试角色，产品和过程定义权威和责任

3.定义组织架构。4.定义沟通架构。

SP 3.5 Develop the master test plan 开发主测试计划

The master test plan is established to define a coherent test approach across multiple test levels. Example work products 1. Master test plan Sub-practices 1. Establish the master test schedule with predefined stages of manageable size for the identified test levels based on the defined test estimate and selected test lifecycle 2. Align the master test schedule with the overall project schedule 3. Plan for necessary test staffing resources with the required knowledge and skills to perform the testing 4. Plan the involvement of identified stakeholders 5. Identify, analyze and document the project risks associated with testing 6. Establish and maintain the master test plan Examples of elements of a master test plan include the following [after IEEE 829]:  Test plan identifier  Overall introduction (scope, references, system overview and test overview)  Organization, including roles and responsibilities  Non-compliances with the test strategy and the rationale  Items to be tested (including risk level) and not to be tested  Features to be tested (including risk level) and not to be tested  Identification of test levels and test types  Test approach (e.g., test design techniques) per test level  Entry and exit criteria per test level  Test milestones and work products  Test lifecycle and tasks  Environmental needs and requirements (including office environment)  Staffing and training needs  Stakeholder involvement  Test estimate  Master test schedule  Test project risks and contingencies Refer to SG 4 Develop a Test Plan from the process area Test Planning for more details on the (sub) practices for developing a master test plan. Refer to the process area Test Environment for more information on environment needs and requirements.

主测试计划被建立来定义一系列覆盖不同测试等级的测试方法。

例子工作产品：主测试计划

子实践：1. 建立主测试进度，基于已定义的测试评估和选择的测试生命周期。2.保持主测试进度和整体项目进度一致，3.计划一个必须的测试人员资源。4.计划包含的和明确的利益相关人。5.明确，分析和文档化项目风险。关于测试的。6.建立和维护主测试计划。

SP 3.6 Obtain commitment to the master test plan 获得关于主测试计划的承诺

Commitments to the master test plan are established and maintained. Example work products 1. Documented requests for commitments 2. Master test plan review log 3. Revised and re-negotiated master test plan, including changes to test budgets, test schedule, product risk list and stakeholder agreements 4. Documented commitments Sub-practices 1. Organize reviews with stakeholders to help them understand test commitments 2. Discuss differences between estimates and available resources with stakeholders 3. Reconcile any differences between estimates and available resources 4. Identify needed support and negotiate commitments with relevant stakeholders 5. Document all organizational commitments, both full and provisional 6. Review internal commitments with senior management as appropriate 7. Review external commitments with senior management as appropriate Refer to SG 5 Obtain Commitment to the Test Plan from the process area Test Planning for more details on the (sub) practices for obtaining commitment to the master test plan.

主测试计划的承诺被建立和维护。

例子工作产品：1.文档化承诺需求。2. 主测试计划重审日志。3. 修改和再次讨论主测试计划。包括测试预算的改变，测试进度，产品风险列表和相关责任人协定。4.文档化承诺。

子实践：1. 组织重审帮助理解承诺。2. 讨论评估和现有资源之间的区别。3.协调评估和现有资源。4.明确需要的支持和讨论承诺。5.文档化所有组织承诺。6.实时修改。