在这样的情况下，一个对象流图是有用的。
In situations such as these, an object-flow diagram is useful.
在对联系信息进行更改时，工作流图将很有帮助。
A workflow diagram can be helpful when making changes to contact information.
发生的方式之一是将数据流图和用例图混淆在一起。
One way this occurs is by confusing data flow diagrams with use case diagrams.
创建价值流图主要有三个原因：客观性，清晰性以及说服力。
There are three primary reasons to create Value Stream Maps: objectivity, clarity, and persuasion.
清单1显示了图 1的工作流图的WSFL语法。
The workflow diagram in Figure 1 has the WSFL syntax shown in Listing 1.
让我们考虑一下在这篇文章开始部分使用的价值流图的基本范例。
Let's consider the very basic sample Value Stream Map used at the beginning of this article.
价值流图帮助我们考虑，“在向客户交付价值的过程存在什么障碍？”
Value Stream Maps help us consider, "What is getting in the way of delivering value to them?"
但是首先要指出的是，什么是价值流图，以及怎样去制作这样一个价值流图。
But first things first: What a Value Stream Map is and how one can be intelligently produced.
通过这些小型会议，可以形成业务工作流图(例如图1中所示的工作流图)。
From these small meetings, build a diagram of the business workflow, such as that shown in Figure 1.
超出这个基本的范例，让我们考虑一下创建价值流图所涉及到的一些基本元素。
Beyond this basic example, let's consider some of the elements that could potentially go into creating a Value Stream Map.
在用户代理和SIP服务之间沟通具体的活动场景的最普遍的方法之一是利用调用流图。
One of the most common ways to communicate a specific scenario of activity between user agents and SIP services is with a call flow diagram.
generic树被转换成GIMPLE形式，进而转换成控制流图，以支持基于SSA的优化。
The GENERIC trees are converted into GIMPLE form and a subsequent control flow graph to support SSA-based optimizations.
服务的实现，如一组调用流图所描述的，在设计模型中从继承正确框架类的单个原型化的类开始。
A realization of the service, as described by a set of call flow diagrams, begins in the design model with a single stereotyped class that extends the right framework class.
例如，可能您的团队会评审一个价值流图，以理解实施一个外部客户源的新需求需要多长的时间。
For example, it may be the case that your team is reviewing a Value Stream Map to understand how long it takes to implement a new requirement that comes from an external customer source.
价值流图帮助我们给公司带来一些改进，过程及方法上进行升级，而更重要的是，生产质量更高的软件。
Value Stream Maps help us bring about organizational improvement, progress in our processes and methods, and most importantly, better software.
可选的：可以创建一个“如果这样做会怎样”的选择（第二个这样的图片，有时也叫做“未来状态”价值流图）。
Optional: A "what if?" alternative can be created (a second such picture, sometimes referred to as a "future state" Value Stream Map).
flow选项创建一个纯文本跟踪输出文件，在这个文件中，跟踪记录是按进程(by process)以及时间顺序排序的。它所创建的实际上是一个控制流图。
The flow option creates a plain text trace output file in which the trace records are ordered chronologically by process; it creates what is essentially a control flow diagram.
图3显示了带消息日志记录的请求流，图4显示了带消息日志记录的响应流。
Figure 3 shows the request flow with message logging, and Figure 4 shows the response flow with message logging.
图7展示了视觉流，图8深入演示while循环中的流。
Figure 7 shows the visual flow and Figure 8 drills down to illustrate the flow inside the while loop.
在图4中，按照如下步骤把传统的流(图2和3)转化成Web服务。
In Figure 4, the classic flows (Figures 2 and 3) are converted to web services as follows.
图1中所示的流关系图描述了以下模块。
The flow diagram in Figure 1 describes the following modules.
中介流应该与图13所示类似。
The mediation flow should be similar to the diagram in Figure 13.
保存该中介流，返回到组装图，按照前面的描述合并实现。
Save the mediation flow, return to the Assembly Diagram, and merge the implementation as described above.
此中介流组件（图4）执行请求者数据模型与提供者数据模型间的映射，并且还可以针对诊断或审计的目的进行进一步的日志记录。
The mediation flow component (Figure 4) performs a mapping of the requestor's data model to that of the provider, and perhaps performs some further logging for diagnostics or auditing purposes.
图6显示了消息流的整个序列。
这也是我们将中介流组件保留在图10 中的适配器旁边的原因。
This is the reason why we have retained mediation flow components next to each of the adapters in Figure 10.
图1：可重复流作为可链接内容进行复用。
然而，在一般情况下，当两个节点在单独的消息流中时(例如，图2)，您需要自己将必要的相关性信息转发给应答流。
However, in general when the two nodes are in separate message flows (for example, Figure 2), you need to forward the necessary correlation information to the reply flow yourself.
图2展示了用于事件流的配置。
Figure 2 shows the configuration that can be used for event streams.
图4示出了所描述的事件流。
应用推荐