Close and save the sequence diagrams.
关闭并保存这个序列图表。
Ultimately, sequence diagrams are maps of interaction.
归根结底，序列图就是交互图。
Existing sequence diagrams can be reused as test cases.
已存在的序列图可以作为测试用例再使用。
Simplify sequence diagrams using subsystems (optional).
用子系统简化序列图(可选)。
Nature of the problems with class and sequence diagrams.
类及序列图问题的实质。
Transactions are very easy to identify in sequence diagrams.
事务处理在序列图中是很容易识别的。
As with sequence diagrams, there is the concept of messages.
对于序列图，有消息的概念。
Using sequence diagrams to model application execution flow.
使用时序图建模应用程序执行流程。
Sequence diagrams are excellent for documenting method logic.
方法逻辑序列图在记录方法逻辑方面非常优秀。
Use cases are often refined into one or more sequence diagrams.
用例常常被细化为一个或者更多的序列图。
Generate an initial state chart from package sequence diagrams.
从包序列图表生成一个初始状态表。
Sequence diagrams are often used to document these interactions.
序列图通常用于记录这些交互。
As you can see, sequence diagrams get complicated fairly quickly.
您可以发现，序列图可以很快变得相当复杂。
Sequence diagrams are used to model the logic of usage scenarios.
序列图用于为使用方案的逻辑建模。
These enhancements have made sequence diagrams much easier to edit.
这些增强使序列图编辑起来更容易。
Example behavior diagrams are activity, use case, and sequence diagrams.
行为图的实例是活动图，用例图和序列图。
Then an object model and sequence diagrams were created for each system.
然后为每个系统创建对象模型和序列图。
However, there is another way to pass information between sequence diagrams.
然而，有另一个方法在序列图之间传递消息。
Use Case Design Step 3: Simplify sequence diagrams using subsystems (optional).
用例设计第3步：用子系统简化序列图(可选)。
When that occurs, use cases are often refined into one or more sequence diagrams.
那种情况下，用例常常被细化为一个或者更多的序列图。
JSP calls - the calls to JSP (s) in a use case are shown in the sequence diagrams.
JSP调用——在用例中对JSP文件的调用也会显示在序列图中。
Simply put, instance names in sequence diagrams are underlined; roles names are not.
简单拖放，序列图的实例名称有下划线，而角色名称没有。
Figure 4: UML sequence diagrams provide a simple, coherent way to represent systems.
图4：uml序列图提供表示系统的简单，条理分明的方法。
The UCD team initially did the sequence diagrams with respect to the object diagrams.
起初，UCD小组完成的序列图与对象图有关。
These business scenarios are also expressed in UML collaboration and sequence diagrams.
这些业务方案也是用UML协作和序列图表示的。
This arguably points to the need to always model return values in your sequence diagrams.
这可能证明为什么总是需要在序列图为返回值建模。
Sometimes, Sequence diagrams contain a lot of detail that you are just not interested in.
有时候，序列图包含许多您并不感兴趣的情况。
Interface driver, constraint, and timing rules, modeled using interaction or sequence diagrams.
接口驱动器、约束和计时规则，通过交互或时序图进行建模。
Our refinement leads to the detailed class and sequence diagrams in Figures 3 and 4 respectively.
经过改进，我们分别得出了如下面的图3和图4所示的详细类图表和序列图表。
Sequence diagrams, also of great value in Function Verification, provide the interaction information.
序列图，在功能验证中有很重要的价值，提供交互的信息。
应用推荐