RUP addresses technical risk early.
RUP 尽可能早的解决技术风险。
减少技术风险。
Elaboration phase: Manage technical risk.
精化(Elaboration)阶段：管理技术风险。
Addressing technical risk — The Elaboration phase.
解决技术风险——精化阶段。
Elaboration isn't a design phase, it's a "reduce your technical risk" phase.
精化不是设计阶段，这是个“减少技术风险”的阶段。
But most people in those situations don't worry too much about technical risk.
但是大多数人做这些事时不会考虑到太多的技术风险。
By driving out technical risk early the architecture will stabilize more rapidly.
通过及早去除技术风险，架构将更快速地稳定。
Technical risk is the concrete manifestation of the negative effects technology.
技术风险是技术负效应的具体表现。
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.
技术风险：你正在为安排和估计软件项目构建一个新的应用。
Reducing development risk early by proving technical approaches
通过检验技术方法来尽早地减少开发风险
The ones at risk are development, probably more like Technical Authors or Support Desk.
那些处于危险的是开发，也许更像技术作者或支持服务部。
The ones at risk are development, probably more like Technical Authors or Support Desk.
那些处于危险的是开发，也许更像技术作者或支持服务部。
应用推荐