5To find out more about exploratory testing and TMap, send an e-mail to tmapadmin@sogeti.nl and request the paper by T. Koomen, Exploratory testing and TMap.
5要找更多的有关探索测试和TMap的内容，请发送邮件到tmapadmin@sogeti.nl，索要T.Koomen,Exploratorytestingand TMap论文。
RUP defines a test script in a way that differs from TMap.
RUP按照一种有别于TMap的方式来定义一个测试脚本。
Figure 3: Global relation between TMap lifecycle and the RUP workflow.
图3：TMap生命周期和RUP工作流之间的全局关系。
This activity then needs to be added to the mentioned TMap activities.
然后这个活动需要被添加到谈到的TMap活动中。
RUP v.2002 came about with help from the Sogeti work group "TMap in RUP."
RUP2002版的产生得到了Sogeti工作组"TMap in RUP"的帮助。
Yet implementing TMap alongside RUP offers great added value in many cases.
然而，与RUP一起实施TMap在许多方面提供极大的增值。
This RUP step combines the important TMap phases Specification and Execution.
这个RUP步骤合并了重要的TMap阶段-规格说明和执行。
TMap also defines the required organization and infrastructure in more detail.
TMap也详细地定义了所需要的组织和基本结构。
Now, let's consider how TMap phases and activities can be incorporated into RUP.
现在，让我们考虑一下TMap阶段和活动如何被合并到RUP中。
For development of the test strategy, the technique described by TMap is sufficient.
对于测试策略的开发，TMap描述的技术是足够的。
In designing a test script based on UML, the steps described in TMap need to be executed.
在设计一个基于UML的测试脚本时，需要执行在TMap中所描述的步骤。
The activities of the TMap Completion phase and its RUP counterparts are shown in Table 6.
TMap完成阶段的活动及其与RUP的对照如表6所示。
The TMap phase Specification can be mapped to Test and Evaluate in RUP, as shown in Table 4.
TMap规格说明阶段可以被映射到RUP中的测试和评价，如表4所示。
TMAP presents a structure of information and helps a team progress through the DMAIC process.
TMAP代表信息的结构，通过DMAIC流程帮助团队前进。
More specific details about these additional tests are available within the TMap method itself.
有关这些额外测试的更多详细内容在TMap方法中可以得到。
The first three roles largely correspond to the two TMap descriptions for test manager and tester.
前三个角色主要对应于TMap测试经理和测试员的两个描述。
TMAP can be used to drive specific actions and select the Six Sigma tools that should be employed.
一个TMAP可以用于推动具体的行动和选择应该使用的六西格玛工具。
TMap is a very extensive and complete test approach, whereas in RUP, testing is just one of many aspects.
TMap是一种非常广泛和完善的测试方法，但是在RUP中，测试只是许多方面之一。
One tool that can ensure a firm foundation is the thought process map, sometimes referred to as a TMAP or TPM.
可以确保坚实的基础的工具之一就是思维过程图，有时被称为TMAP或TPM。
The number of test paths to be determined depends on the test measure (for more information, refer to TMap itself).
测试路径的数量取决于测试标准（有关更多信息，请参见TMap）。
Besides the fourth TMap activity, Preserving Testware, this RUP step also contains the evaluation of the test process.
除了第四个TMap活动，保存测试件，这个RUP步骤也包含测试过程的评价。
Proactive management of the test process and applying a risk-based approach, as TMap describes, is therefore mandatory.
因此，测试过程的提前管理并应用一种基于风险的方法，如TMap所描述的，是必须的。
The single, most important benefit of using a TMAP early in a project is it ensures that nothing is left out or missed.
在项目中最早使用TMAP唯一、最重要的益处是保证什么都没有被忽略或错过。
Another difference is that the TMap test strategy is based on risks, quality characteristics, system parts, and required test techniques.
另外一个差异是，TMap测试策略基于风险、质量特性、系统部分和必需的测试技术。
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的观点来处理这个问题。
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系统文档的测试用例(也可以参见下面的“技术”一节)。
Making testability an item on the agenda of the development team is not something that is made explicit in TMap, but which will prove to be a very valuable activity.
将易测性作为开发团队的一个议程项目并不是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有多个技术特性，包括测试策略开发、测试点分析、测试的易测性复审和许多测试规格说明技术和检查单。
Although the test strategy in TMap can in some ways be compared to the activities Define test Approach and Define Assessment and Traceability Needs, the level of detail in TMap is much higher.
尽管TMap中的测试策略在某种方式上可以与活动定义测试方法和定义评估和可追踪性需求进行对应，但是TMap中的详细程度要更高一些。
Although the test strategy in TMap can in some ways be compared to the activities Define test Approach and Define Assessment and Traceability Needs, the level of detail in TMap is much higher.
尽管TMap中的测试策略在某种方式上可以与活动定义测试方法和定义评估和可追踪性需求进行对应，但是TMap中的详细程度要更高一些。
应用推荐