tmap

Yet implementing TMap alongside RUP offers great added value in many cases

然而，与RUP一起实施TMap在许多方面提供极大的增值

For development of the test strategy , the technique described by TMap is sufficient .

对于测试策略的开发，TMap描述的技术是足够的。

TMap also defines the required organization and infrastructure in more detail .

TMap也详细地定义了所需要的组织和基本结构。

An additional step in TMap is discharging the test team .

在TMap中的另外一个步骤正在解放测试团队。

An important part of the test strategy according to TMap is putting together the cost estimation .

按照TMap，测试策略的一个重要部分是与成本估算放在一起的。

Appendix A : Master test plan according to RUP and TMap

附录A：按照RUP和TMap的主测试计划

This activity then needs to be added to the mentioned TMap activities .

然后这个活动需要被添加到谈到的TMap活动中。

More specific details about these additional tests are available within the TMap method itself .

有关这些额外测试的更多详细内容在TMap方法中可以得到。

TMap 's master test plan can be compared to RUP 's master test plan .

TMap的主测试计划可以比作RUP的主测试计划。

This RUP step combines the important TMap phases Specification and Execution .

这个RUP步骤合并了重要的TMap阶段-规格说明和执行。

In TMap ," Setting up the Infrastructure " is part of the Specification phase .

在TMap中，“建立基础结构”是规格说明的一部分。

TMap complies with RUP testing practice , as described in the Test discipline .

TMap遵守RUP的测试实践，如测试流程中所描述的那些。

The first three roles largely correspond to the two TMap descriptions for test manager and tester .

前三个角色主要对应于TMap测试经理和测试员的两个描述。

Another difference is that the TMap test strategy is based on risks , quality characteristics , system parts , and required test techniques .

另外一个差异是，TMap测试策略基于风险、质量特性、系统部分和必需的测试技术。

In designing a test script based on UML , the steps described in TMap need to be executed .

在设计一个基于UML的测试脚本时，需要执行在TMap中所描述的步骤。

The control activities in both TMap and RUP are mainly found in the step , Achieve Acceptable Mission .

在TMap和RUP都有的控制活动主要是在步骤完成可接受任务。

The standard TMap testability review checklists need to be applied when dealing with UML .

标准的TMap易测性复审检查单需要在用UML处理时应用。

As this document addresses a specific variation , a certain level of TMap and RUP knowledge is assumed .

由于本文重点强调一种明确的变化，所以假定读者对TMap和RUP知识有一定的水平。

TMap is a very extensive and complete test approach , whereas in RUP , testing is just one of many aspects .

TMap是一种非常广泛和完善的测试方法，但是在RUP中，测试只是许多方面之一。

Now , let 's consider how TMap phases and activities can be incorporated into RUP .

现在，让我们考虑一下TMap阶段和活动如何被合并到RUP中。

Proactive management of the test process and applying a risk-based approach , as TMap describes , is therefore mandatory .

因此，测试过程的提前管理并应用一种基于风险的方法，如TMap所描述的，是必须的。

More or less comparable TMap roles are methodological support and TAKT architect .

或多或少可对比的TMap角色是方法支持和TAKT构架师。

Besides the fourth TMap activity , Preserving Testware , this RUP step also contains the evaluation of the test process .

除了第四个TMap活动，保存测试件，这个RUP步骤也包含测试过程的评价。

The number of test paths to be determined depends on the test measure ( for more information , refer to TMap itself ) .

测试路径的数量取决于测试标准（有关更多信息，请参见TMap）。

Various TMap specification techniques are very well suited for constructing test cases based on RUP system documentation ( see also the " Techniques " section below ) .

不同的TMap需求规格技术非常适合于建立基于RUP系统文档的测试用例（也可以参见下面的“技术”一节）。

If the TMap test strategy is used , you must take care to ensure that testing stays within the scope of the iteration / test assignment .

如果要使用TMap测试策略，你必须要小心确保测试是在迭代或测试任务的范围中进行。

The remaining activities from the TMap phase Execution can be placed under Test and Evaluate , as can most of the activities from Specification .

TMap执行阶段的剩余活动可以放在测试和评价中，和规格说明的大多少活动一样。

TMap features several techniques , including test strategy development , test point analysis , the testability review of the test basis , and many test specification techniques and checklists .

TMap有多个技术特性，包括测试策略开发、测试点分析、测试的易测性复审和许多测试规格说明技术和检查单。

It is important to note that no explicit test activities take place in this TMap phase , whereas this is the case in the RUP workflow .

注意到在TMap阶段中没有很明确的测试活动，这是很重要的，然而，这在RUP工作流中是一种情况。

RUP stresses that specification and execution of test cases can be parallel activities . Let 's discuss how to deal with this from a TMap point of view .

RUP强调，规格说明和测试用例的执行可以是并行的活动，让我们讨论一下如何从一个TMap的观点来处理这个问题。