一些人认为在全国范围内实施复杂的投票技术风险太大。
Some people believe that it is too risky to implement complicated voting technology nationwide.
最后，一些人认为在全国范围内运用复杂的投票技术风险太大。
Finally some people say it is too risky to implement complicated voting technology nationwide.
RUP 尽可能早的解决技术风险。
解决技术风险——精化阶段。
确定业务和技术风险。
RUP的精化阶段是对准技术风险的管理的。
RUP's Elaboration phase is directed at managing technical risk.
项目技术风险相当低。
通过及早去除技术风险，架构将更快速地稳定。
By driving out technical risk early the architecture will stabilize more rapidly.
减少技术风险。
构架师的另外一个焦点是鉴别和管理项目的技术风险。
Another focus of the architect is to identify and manage technical risks associated with the project.
但是大多数人做这些事时不会考虑到太多的技术风险。
But most people in those situations don't worry too much about technical risk.
精化不是设计阶段，这是个“减少技术风险”的阶段。
Elaboration isn't a design phase, it's a "reduce your technical risk" phase.
精化(Elaboration)阶段：管理技术风险。
您采用的方法应该着重于在早期减少风险，包括技术风险。
The approach you adopt should focus on early risk mitigation, including technical risks.
技术风险：你正在为安排和估计软件项目构建一个新的应用。
Technical risk: You are building a new application for scheduling and estimating software projects.
在充满高度技术风险的社会，核电组织非同寻常的超市商店。
In a society filled with high technical risks, nuclear organizations are unlike ordinary supermarkets and stores.
对于每一个重要的技术风险，拟订你要原型化什么以减少风险。
For each of the key technical risks, outline what prototyping you need to do to mitigate the risks. Consider the following examples.
commandgateway，它造成了一些最大的技术风险。
The command gateway, which posed some of the greatest technical risks.
后继的精化阶段可能会利用新的测试难点的解决方案来解决技术风险。
The subsequent Elaboration phase might solve technical risks with a solution that imposes new testing difficulties.
在决定偿还债务之前，决策者对业务和技术风险都需要有深刻的理解。
The decision to pay down technical debt requires a solid understanding of both the business and technical impacts.
通过识别最重要的三个技术风险和最重要的三个有必要澄清的功能部分开始。
Start by identifying the top three technical risks and the top three functional areas in need of clarification.
您将会看到，通过开发端到端的系统工作框架，在细化阶段如何处理技术风险。
You'll see how technical risk is addressed during the Elaboration phase by developing an end-to-end working skeleton of the system.
这些原型的目标是减少主要的技术风险和澄清项目涉众对系统应该做什么的理解。
The objectives of these prototypes are to mitigate key technical risks and clarify stakeholders' understanding of what the system should do.
梅丽莎·芬努凯恩：这也可以解释为什么人们不采取技术风险评估后的推荐方法。
Melissa Finucane: And why that might not be consistent with the recommendations that come out of technical risk assessments.
对于DW项目，您的技术风险集中于数据量、对遗留数据源的访问和数据质量上。
For a DW project your technical risks typically focus on data volume, access to the legacy data sources, and data quality.
该方法减少了商业和技术风险，而交付满足最终用户变化需求的高质量解决方案。
This approach reduces both your business and technical risk, while delivering a high-quality solution that meets the changing needs of its end users.
在精化阶段的最后，您希望尽可能的降低技术风险，并且提供一个稳定的体系结构。
At the end of Elaboration you want to drive down as much technical risk as possible and deliver a stable architecture.
技术风险的管理包括制定每一个风险的优先次序，以及确定一个恰当的风险缓解策略。
The management of technical risk involves the prioritization of each risk, and the identification of an appropriate risk mitigation strategy.
如您将在本系列第2部分中见到的，RUP的细化阶段着重于在生命周期早期解决技术风险。
As you will see in Part 2 of this series, RUP's Elaboration phase focuses on addressing technical risk early in the lifecycle.
在这种情况下，预计的业务利益或其他因素驱动的改变往往变得非常重要，以降低技术风险。
In this case, the forecasted business benefit or other factors driving change are usually significant enough that a lower level of technical risk is mandated.
应用推荐