保存序列图。
Figure 7 is the sequence diagram of a simple request.
图7是一个简单请求的序列关系图。
The sequence diagram below shows the flow of events.
下面的顺序图展示了事件的流程。
By default, the sequence diagram editor is in move mode.
默认条件下，序列图编辑器会处在move模式下。
The sequence diagram in Figure 2 illustrates these steps.
图2中的顺序图说明了这些步骤。
The sequence diagram for the above for loop is shown in Figure 5.
图 5显示了上述for 循环的序列图。
Figure 7 shows the sequence diagram for the ws response template pattern.
图7显示了WS响应模板模式的序列关系图。
Figure 3 shows the sequence diagram for the ws response template pattern.
图3显示了WS响应模板模式的序列关系图。
The update will occur even when the Sequence diagram is in a closed model.
即时这个序列图在一个封闭的模型中，这个更新也会发生。
The sequence diagram is the most popular UML artifact for dynamic modeling.
序列图是应用最为广泛的UML动态建模方法。
It works with both static and regular methods, but the Sequence diagram is static.
它对静态的和平常的方法都可用，但时序图是静态的。
The sequence diagram also has an exit gate that returns the balance variable.
序列图也有一个出囗门，返回balance变量。
Figure 3 depicts part of the sequence diagram for the Loan Application use case.
图3图示了贷款申请用例的序列图的一部分。
The sequence diagram in Figure 3 illustrates the asynchronous communication model.
图3的序列图演示了异步通信模型。
In other words, this is the Web services client described in the sequence diagram above.
换句话说，这是上文中的序列图中展示的Web服务客户端。
This text is taken from the use case, or scenario, that the sequence diagram depicts.
这些文字是从用例，或者场景中摘取的，对顺序图的描述。
An option to filter out all getter and setter methods has been added to the sequence diagram.
并且新版本还在序列图中添加了一个选项，可以把所有getter和setter方法筛选掉。
You see what is going to be reordered, and the sequence diagram editor is now in reorder mode.
您可以看到什么将会被记录，序列图编辑器现在也处于重新排序模式下了。
Figure 17 shows the sequence diagram after having applied the requester-side caching pattern.
图17显示了应用请求端缓存模式后的序列关系图。
You can see what is going to be reordered, and the sequence diagram editor is now in reorder mode.
您可以看到什么将会被重新排序，现在序列图编辑器处于重排模式。
As we move from the sequence diagram to the class diagram, our system analysis becomes more refined.
当我们从序列图转到类图时，我们的系统分析就更精细了。
The sequence diagram shows the dynamic method invocations among classes for performing certain tasks.
序列图显示了在执行特定任务时类间的动态方法标记。
These database calls are shown in the sequence diagram along with the response time for each database hit.
这些数据库调用会显示在序列图中，并且还会显示每次数据库访问的响应时间。
Besides just showing message calls on the sequence diagram, the Figure 4 diagram includes return messages.
除了仅仅显示序列图上的消息调用外，图4中的图还包括返回消息。
Previous versions of the sequence diagram editor allow you only to select classifier-owned operations.
序列图编辑器的前面版本只允许您选择标识符所有的操作。
Breakpoints can be set on the sequence diagram by using the RTC_BREAK conditional statement. (See Figure 14.)
您可以使用RTC _ BREAK状态性声明来在序列图上设置中断点(参见图14)。
The sequence diagram in Figure 3 illustrates the complete messages flow implemented in the sample application.
图3 所示的序列图展示了样例应用程序中实现的完整消息流。
On the Sequence diagram the object boxes have no name preceding the ":." These are called anonymous objects.
在顺序图中，对象框没有名字“：”，这些对象叫做匿名对象。
The interaction between SUBSCRIBE and PUBLISH requests is demonstrated in the sequence diagram shown in Figure 8.
图8中所示的序列关系图演示了SUBSCRIBE和PUBLISH请求间的交互。
Similar to the sequence diagram, the communication diagram can also model the dynamic behavior of the use case.
类似于序列图，通信图也对用例的动态行为建模。
应用推荐