RUP解决范围风险。
RUP has many detailed roles and artifacts.
RUP拥有许多详细的角色和工件。
RUP tests can be both manual and automated.
RUP测试可以是手工和自动化测试。
By using the Review Record provided in RUP.
使用RUP所提供的评审记录。
We build courseware using the spirit of RUP.
我们用RUP的思想来构建课件。
Both RUP and CMM have extensive glossaries.
RUP和CMM都有大量的词汇。
This approach is included in both RUP and RUP-SE.
这种方法既包含在RUP中，也包含在RUP -SE中。
But many areas of RUP remain unaffected by this update.
但RUP的许多领域仍旧不受到该更新的影响。
These links are built using the standard RUP heuristics.
这些链接是利用标准的RUP试探法构建的。
Did RUP shape the integration of tools or vice versa?
RUP形成了工具的集成吗，或反之亦然？
Unfortunately this collides with the RUP Elaboration phase.
不幸的是这与RUP的精化阶段冲突。
RUP was based on best practices of software engineering.
RUP基于软件工程的最佳实践。
RUP is the leading iterative software development methodology.
RUP是最主要的迭代软件方法。
Figure 3 shows the RUP, its disciplines, phases, and iterations.
图3显示了RUP、它的规程、阶段和迭代。
RUP then becomes the foundation for rolling out other tools.
于是RUP成为使用其它工具的基础。
Flexibility is built into the iterative approach described by RUP.
灵活性被植入由RUP描述的迭代方法中。
For compliance with CMMI, however, they define separate RUP processes.
然而，为了和cmmi兼容，他们定义了单独的RUP过程。
In fact, even RUP provides few low-level details about implementation.
事实上，甚至RUP也很少提供关于实现的细节。
From the stakeholders point of view, RUP introduces all new vocabulary.
从涉众的观点出发，RUP引入了所有的新词汇。
Again, there should be no confusion between the RUP and MSF principles.
再次说到，RUP和MSF原则之间应该不存在混乱。
Figure 2: the structure of RUP, as described in the RUP product itself.
图2：RUP的结构，正如RUP产品本身所描述的那样。
Again, organizations using RUP can use this to supplement RUP guidelines.
同样，使用RUP的组织可以使用CMMI来补充RUP的指导。
RUP provides no implementation of the Supplier Agreement Management process area.
RUP没有为供应商协议管理领域过程提供实现。
Additionally, RUP comes with built-in tool mentors that can provide guidance.
另外，RUP是有内置工具指导的，可以提供一些指导。
RUP comes in multiple "form factors" (RUP for Systems Engineering, for instance).
RUP由多种形式(比如，系统工程等等)。
Use Rose's RUP template, providing a model framework that adhered to RUP guidelines.
使用Rose的RUP模板，提供一个附带 RUP指南的模型框架。
The simplest way to capture and communicate the RUP tailoring is to build a RUP development case.
最简单的捕捉和沟通RUP裁剪的方法是构造一个RUP开发案例。
These techniques are not described in RUP, but they can be applied without problems in RUP test projects.
这些技术没有在RUP中描述，但是他们可以毫无问题地应用到RUP测试项目中。
Adopt RUP best practices and be guided by the spirit of RUP. Restructuring your project plan is not enough.
采用RUP最优方法并且使用RUP作为导向重构你的项目计划还不够。
The successful RUP adoption started with their project and customized RUP to fit their project and organization.
成功的RUP采用从他们的项目开始，并定制RUP以使其适合他们的项目和公司。
应用推荐