图1显示了第1部分中建议的流程分解结构。
Figure 1 shows the process decomposition structure proposed in Part 1.
图11显示了分解为三个局部流程的流程示例。
Figure 11 shows an example of a process decomposed into three local processes.
接下来，Wilby添加了一个功能图，用于定义并分解CreativeGenius执行的主要职能。
Next, Wilby adds a capability map, which defines and decomposes the main functions that CreativeGenius performs.
图1展示了WebSphere从一个J2EE应用程序中分解出来的4 个组件（客户、用户组件、服务器组件和遗留组件）。
Figure 1 shows how WebSphere separates the four components of a J2EE application (client, user component, server component, and legacy component).
图5中“敏捷看板”的例子是一个工作的分解，它在团队内部工作良好。
The example "Agile Kanban" in Figure 5 is a work breakdown, and it works well within the team.
您可以通过将活动拖拽到对象模型图创建一个功能性分解，来分解对象模型图上的活动。
You can decompose activities on an object model diagram by dragging it onto the object model diagram to create a functional decomposition.
图6中“持续看板”的例子是一个功能的分解并且一张卡片代表一个MMF。
The example "Sustaining Kanban" in Figure 6 is a feature breakdown and one card represents an MMF.
图4演示了服务规范工作流中的第一级分解过程。
Figure 4 illustrates the first level of decomposition in the Service Specification workflow.
工作流是指通过将整个工作分解成若干任务并自动化这些任务的分配与进展，以在不同团队间有效地分配工作的系统(图16)。
Workflow refers to systems that allow efficient distribution of work between teams of people by breaking the work into tasks and automating the distribution and progression of those tasks (Figure 16).
图17显示了一个典型的工时单视图，展示了计划好的工作分配情况、工作分解结构和每个任务分派相应的数据。
Figure 17 shows a typical Timesheet view that displays work assignments by project, the work breakdown structure and corresponding data for each task assignment.
如果您不能找到一个好的原因，去分解一个批任务，您可以转化成图1中提到的“补充性效果”类型。
If you cannot find a good reason to split up the batch job, you can revert to the category of "supplementary effort" mentioned in Figure 1.
图5演示了服务实现工作流的第一级分解过程。
Figure 5 illustrates the first level of decomposition in the Service Realization workflow.
它还向您展示了怎样将一个虚拟化系统分解为拓扑图，这演示了虚拟机系统与物理主机之间的相互独立性。
They also show how to separate virtual systems into diagrams, which illustrates the independence of the virtual systems from their physical hosts.
它包括使用活动图进行说明的工作分解结构。
It includes a Work Breakdown Structure illustrated with activity diagrams.
正如我在本系列的第2部分解释的那样，当需求关系在需求图外被提出时，这些属性将会变的非常便捷。
As I explain in part 2 of this article, these attributes become particularly handy when requirement relationships are represented outside requirements diagrams.
同样可以在其中看到运营领域的层次结构分解，其重点同样是图1中突出显示的客户关系管理第1级实体。
Here you again see the hierarchal decomposition within the operations area, focusing on the same Customer Relationship Management level 1 entity highlighted in Figure 1.
对于具有BPM组件的SOA项目，您必需遵循图2中所示的流程分解结构。
For SOA projects with a BPM component, you must adhere to the process-decomposition structure shown in Figure 2.
我将在本文第2部分解释这些图是如何构建的。
I'll explain how these diagrams are constructed in Part 2 of this article.
所开发用于指定基于SOA的解决方案的功能的流程模型应该遵循图2中所示的分解结构。
Process models developed to specify functions of an SOA-based solution should follow the decomposition structure in Figure 2.
此模式如图9所示，图9指示了在分解了100,000个客户文档之后，每个表中的列数和行数。
The schema is shown in Figure 9, indicating the number of columns and the number of rows in each table after shredding 100,000 of our customer documents.
本文附带了一个示例存储过程，该存储过程将MIML数据分解到改进的星型模式中(图8)。
A sample stored procedure that shreds MIML data into the refined star schema (Figure 8) is attached to this article.
图7中“精益+敏捷看板”的例子与图8一起展示了上级功能分解和下级工作分解的结合。
And the example of "Lean + Agile Kanban" in Figure 7 used with Figure 8 shows a combination of a feature breakdown in the upper level and a work breakdown in the lower level.
下方是我们制作的互动图，数据来自欧盟官方的统计机构欧盟统计局（Eurostat），该图分解了27个欧盟成员国（外加挪威）各国的就业构成。
Using data from Eurostat, the official EU statistics body, our interactive chart, below, breaks down the employment make-up of each of the 27 EU member states, along with Norway.
这个图表对我们的主要目的是对时间进对和里程碑达成一致，并且建立工作分解结构（work breakdown structure，WBS）的层次图，工作分解结构中的每一项我们都可以跟踪、估计和执行。
The main purpose of the chart was for us to agree on schedule and milestones and to set up a hierarchy of work breakdown structure (WBS) items that we could track, estimate, and execute against.
图20中显示了您能够轻易的分解工作量，并且指派到不同的用户组，使得每一个组负责不同的虚拟用户。
Figure 20 shows how easily you can break down the workload and assignments to different user groups, with each group carrying different virtual users. For example, to add a new group
使用State这个模式的一个好处是，它可以通过孤立各种状态来分解图3中if语句的情景。
One of the benefits of applying the state pattern is that it can resolve the if-statement situation difficulty shown in Figure 3 by isolating the various states.
图2和图3对Web 2.0的基础设施进行了分解。
为澄清名称及绑定，我调试了CDT对Hello World程序的解析并在图3中提供了AST的分解。
To clarify names and bindings, I debugged the CDT's parsing of the Hello World program and provided the AST breakdown shown in Figure 3.
进一步说，我喜欢一个成功的轴线分解图的原因是它有清晰容易理解的设计元素，而不仅仅是依靠单个立面或者他们奢华的内部来体现。
Even more though, I like how a successful exploded axon depends on a clear understanding of all the elements of a design, not just a single facade or dramatic interiors by themselves.
返回到轴线的结构分解图，一旦群体被建立，分解不同构件的渲染图是不用花费多少时间的。
Back to the exploded axon, once the groups are established, exploding the geometry for the illustration takes no time at all.
应用推荐