RUP解决财务风险。
Let's consider RUP, for example.
举例来说，让我们考虑RUP。
为什么RUP更有意义？
RUP解决范围风险。
这是RUP强大的地方。
Some team members were new to RUP.
有些团队成员对RUP并不熟悉。
RUP addresses technical risk early.
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都有大量的词汇。
If you want example templates, RUP has many.
如果你需要模板的样例，RUP上面有很多。
The RUP term for these entities is business worker.
这些实体的RUP术语是业务参与者 。
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试探法构建的。
RUP iteration is a classic example of repeatable activity.
RUP迭代是可重复活动的一个经典的例子。
Unfortunately this collides with the RUP Elaboration phase.
不幸的是这与RUP的精化阶段冲突。
When should you consider using RUP instead of waterfall?
你应当在何时考虑使用RUP方法替代瀑布法？
RUP was based on best practices of software engineering.
RUP基于软件工程的最佳实践。
However, in RUP the entire project is tightly controlled.
然而，在RUP中，这个项目是能够被很好的控制的。
RUP is the leading iterative software development methodology.
RUP是最主要的迭代软件方法。
RUP then becomes the foundation for rolling out other tools.
于是RUP成为使用其它工具的基础。
Within the informal work method of RUP, this is often unnecessary.
在RUP方法的正式工作中，这常常是不必要的。
For compliance with CMMI, however, they define separate RUP processes.
然而，为了和cmmi兼容，他们定义了单独的RUP过程。
From the stakeholders point of view, RUP introduces all new vocabulary.
从涉众的观点出发，RUP引入了所有的新词汇。
For instance, RUP has one administrator role, the system administrator.
例如，RUP有一个管理员角色，系统管理员。
Figure 1: the RUP Review Record complements the RUP Development case.
图1：RUP评审记录辅助RUP开发案例。
Again, organizations using RUP can use this to supplement RUP guidelines.
同样，使用RUP的组织可以使用CMMI来补充RUP的指导。
应用推荐