RUP的精化阶段是对准技术风险的管理的。
RUP's Elaboration phase is directed at managing technical risk.
构架师的另外一个焦点是鉴别和管理项目的技术风险。
Another focus of the architect is to identify and manage technical risks associated with the project.
在充满高度技术风险的社会，核电组织非同寻常的超市商店。
In a society filled with high technical risks, nuclear organizations are unlike ordinary supermarkets and stores.
非系统风险包括技术风险、投资风险和管理风险。
Non - systematic risks are classified as technique risk, investment risk and management risk.
对于每一个重要的技术风险，拟订你要原型化什么以减少风险。
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.
非系统风险主要包括管理风险、技术风险、生产风险、市场风险和财务风险。
Non-system risks include management risks, technology risks, production risks, market risks and finance risks.
如您将在本系列第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.
为了确保你的团队能够将注意力放在所有主要的技术风险上，他们必须理解系统的每一个区域。
To ensure that your team will address all major technical risks, they must understand each area of the system.
所提出的方法为建立系统化、结构化的复杂工程系统技术风险分析方法提供了可能。
The suggested method makes it possible to build the systematic method of technology risk analysis for complicated engineering system technology.
高校中间试验工作承担着技术风险和市场风险，具有横垮科研与生产两大领域的特点。
The essay elaborates that the intermediate experiment which links up with the scientific research and production, bears the responsibility for both the technology and the market risks.
由于执行工作相似的原因，管理工作的方法也趋于相似，进一步强调了精化阶段对技术风险的重视程度。
As a result of the similarities in the work performed, the measurements used to manage the work tends to be similar as well, with a greater focus on technical risks in the Elaboration phase.
举例来说，在Elaboration的末尾，您希望去除尽可能多的技术风险，并且交付稳定的架构。
For example, at the end of Elaboration you want to drive as much technical risk as possible and deliver a stable architecture.
为了将相对直截了当的管理工作流水化，此决定潜在地增加了开发和操作成本，更不要提整体的技术风险。
This decision potentially increases development and operational costs, not to mention overall technical risk, in order to streamline a relatively straightforward administration effort.
更重要的是，我们必须能够证明针对DW的有效且端到端的框架，这表明我们了解并处理了主要的技术风险。
More importantly we must be able to demonstrate a working, end-to-end skeleton for our DW which shows that we understand and have addressed the major technical risks.
技术评价是技术完善的基础和降低实施风险的前提，技术预见对于技术风险的管理具有指导意义。
Technology estimation constitutes the foundation of consummating technology and the precondition of reducing risk. Technology forecast is significant to the risk regulation.
可能是开发小组缺乏减少技术风险的技术方面的经验，或者可能是项目应变的速度跟不上商业环境改变的速度。
Perhaps the team lacks the technical experience to mitigate the technical risks, or perhaps the business environment is changing more rapidly than the project can respond.
在构建阶段，技术风险大大降低，此时的主焦点问题是“我们在此阶段结束之前能够完成所有的必要任务吗？”
By the Construction phase, with the technical risks effectively mitigated, the principal focus turns to the question "Can we get all the work done by the end of the phase?"
风险可以有多种分类，包括财务风险，法律风险，信息技术风险，经营风险，舞弊风险和名誉风险。
Risks can be classified in various ways, including financial, legal, IT, operational, fraud and reputation.
应用推荐