在细化阶段，演示具有下列的目标。
During the elaboration phase, demonstrations had the following goals.
此构件在各个细化阶段中迭代地进行开发。
This artifact is developed iteratively through various stages of elaboration.
MDA项目所影响的主要阶段是细化阶段。
正如您所看到的，在项目的细化阶段中执行大多数体系结构工作。
As you can see, most of the architecture work is performed during the elaboration phase of a project.
架构师是细化阶段的主要角色，需要对其进行额外的考虑。
The Architect role is the main role in Elaboration that requires additional consideration.
观察细化阶段的活动并简要地描述MDA改进是很重要的。
It is important to look at Elaboration activities and briefly describe MDA modifications.
注意我们所选择在构建阶段进行工作的方式与细化阶段是不同的。
Note that the way we pick what to work on in Construction is quite different from Elaboration.
在细化阶段，我们根据用例流稳定体系架构的能力来挑选用例流。
In Elaboration, we pick use case flows based on their ability to stabilize the architecture.
设想团队在细化阶段计划两次迭代(e1和e2)，这显然会失败。
Imagine that the team plans for two iterations in Elaboration (E1 and E2), which is fairly typical.
您将会看到，通过开发端到端的系统工作框架，在细化阶段如何处理技术风险。
You'll see how technical risk is addressed during the Elaboration phase by developing an end-to-end working skeleton of the system.
说得这样明确可能很愚蠢，在细化阶段，使您的团队大小保持小规模。
It may seem silly to be so specific, but keep your team size small during Elaboration.
在RUP的术语中，这个转换反映了一个从初始阶段到细化阶段的逐步转化过程。
In RUP terms, this move reflected a gradual transition from the inception phase to the elaboration phase.
当两次迭代完成时细化阶段不会中止，而是当体系架构和远景都稳定时。
Elaboration will end not when two iterations have been completed, but rather when the architecture and the vision are stable.
图1显示了在ASDI项目的第1阶段(RUP的初始和细化阶段)中的用例的演化。
Figure 1 shows the evolution of use cases during phase 1 (the RUP inception and elaboration phases) of the ASDI project.
这意味着在细化阶段利用OI提前工作将比在构建阶段出现更高的风险。
This means that working ahead using OI in Elaboration will present a much higher risk than in Construction.
在细化阶段的末尾，Atlas大大地提高了团队生成真正可执行架构的首次实例的能力。
By the end of the Elaboration phase, Atlas vastly improved the team's ability to generate the first instances of a truly executable architecture.
如您将在本系列第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.
在E2的结尾，很可能不能达到细化阶段的出口标准(稳定的远景，稳定的体系架构)。
At the end of E2, it is possible that the exit criteria for Elaboration may not have been met (stable vision, stable architecture).
在细化阶段期间达到高峰期，软件架构师在该阶段指定大多数设计，并帮助分配构造工作
Peaks during elaboration, when the software architect specifies most of the design and helps assigns work for construction
大多数体系结构（在 第 1部分中有述）工作是在分析和设计的工作流中、在项目的细化阶段执行的。
Most of the architecture (described in Part 1) work is performed during the analysis and design workflow, in the elaboration phase of a project.
由于太不稳定且因此更可能导致废弃和重做，所以在细化阶段不接受OI，而只在构建阶段允许。
Disallow OI during Elaboration as being too unstable, and thus more likely to result in scrap and rework, and only allow it in Construction.
这里有一些代码在实现中可被重用；然而，在细化阶段的早期多数代码在服务于风险降低的目的之后就被抛弃了。
Some of this code survived in the implementation; however, early in the elaboration phase most of the code was thrown away after serving its risk-mitigation purpose.
此外，一旦宽度视角稳定了(以及体系架构，但那是个不同的主题)，项目就从细化阶段迁移到构建阶段。
Again, once the breadth view is stable (as well as the architecture, but that is a different topic), the project moves from Elaboration to Construction.
在初始和细化阶段的早期原型帮助我们确认了这些技术的选择并给了我们在培训、API熟悉和开发上的良好开始。
Early prototypes during the inception and elaboration phases helped us confirm these choices and gave us a good head start on training, API familiarization, and development.
一旦我们进入了细化阶段，我们就很快的开始细化并瞄准原型，这将帮助我们降低技术风险并且帮助我们做设计的决定。
Once we hit the elaboration phase, we quickly began having detailed and targeted prototypes, which mitigated technical risks and helped with design decisions.
细化：细化阶段的目标是为系统体系架构设定基础，用来为构建阶段的大多数设计和实现工作提供稳定的基础。
Elaboration: the goal of the Elaboration phase is to baseline the architecture of the system to provide a stable basis for the bulk of the design and implementation effort in the Construction phase.
所以，在细化阶段，需求的宽度视角(远景)是不稳定的，会随着对深度视角的理解和可执行性的生成而变化。
So, in Elaboration, the breadth view of the requirements (the vision) is expected to be unstable, changing as the depth view is understood and executables are created.
对于细化阶段，八个分析人员可能太多了，但一旦远景和体系架构稳定下来，对于构建阶段这个数就非常大了。
Eight analysts are probably too many for Elaboration but may be great for Construction, once the vision and architecture have stabilized.
细化阶段会描绘出一个将必要的业务需求结合了技术体系架构的可执行的系统，并论证所选技术方法的生存能力。
Elaboration produces an executable system that marries the essential business requirements with the technical architecture and demonstrates the viability of the technical approach chosen.
细化阶段会描绘出一个将必要的业务需求结合了技术体系架构的可执行的系统，并论证所选技术方法的生存能力。
Elaboration produces an executable system that marries the essential business requirements with the technical architecture and demonstrates the viability of the technical approach chosen.
应用推荐