Figure 10 shows the output for this case.
图10展示了这种情况下的输出。
Figure 1 depicts these use cases in the UML use case diagram.
图1用uml使用案例图描绘了这些使用案例。
In this case, a revision represents a merge (see Figure 3 below).
在这种情况下，修订代表一次合并(见图3)。
And, in any case, that figure needs to be put in the context of a very big banking industry, with a lot of underlying profits, especially when compared with America's.
无论如何这些数字都需要置于异常庞大的银行产业背景下，尤其在与美国进行对比时，还要将巨额潜在利润计算在内。
Figure 11 shows a memory leak case involving a large number of JMSTopicConnection objects.
图11显示了涉及大量JMSTopicConnection对象的内存泄漏情况。
Figure 7 shows a case where the user wants to create a 1..
图7显示了一个实例，其中用户想在Customer和BankAccount CMP bean之间创建1 . .。
The 4, 000 word Anatomy of a 4 Figure Affiliate Promotion case study will be in How To Live Anywhere.
4000字对4位数提升案例的解剖都是关于如何在任何地方生活的。
In this case, figure 1 a Lotus Forms user interface has been selected.
在本例中选择了一个LotusForms用户界面，如图1所示。
In this case, figure 2, a Lotus Forms user interface has been selected.
在本例中，如图2，选择一个LotusForms用户界面。
Figure 4 shows an example: consider the case when you right-click the node of the tree.
图4显示了一个范例：当您右击树形结构的节点时，考虑一下这个例子。
In the simple case shown in figure 7, the configuration resources need to be configured in a hierarchical fashion.
在如图7所示的简单情况中，需要以层次结构方式来对配置资源进行配置。
A feature can therefore trace to a use case or a supplementary requirement (see Figure 2).
因此特性可以追溯到用例或补充需求(参见图2)。
For the specific use case we figure out the problem, write the use case, analyse it to figure out what we need to be thinking about, and do some preliminary design.
对于具体的用例，我们弄清问题、撰写用例、分析找出我们需要考虑的内容，并且做一些初步的设计。
In the following use case, shown in Figure 46, the BPEL process module calls a custom primitive mediation module using an SCA import wiring.
在下面的用例中，如图46所示，BPEL流程模块使用一个SCA导入连接来调用一个自定义基元中介模块。
Figure 5 shows how use case storyboards describe the screens that make up the User interaction, and how they are navigated for the specific use case.
图5显示了用例情节串连板如何描述组成用户交互的屏幕显示，以及如何对具体的用例进行导航。
For example, Figure 11 depicts how the use-case analysis method is represented in RUP as a task performed by the role designer.
例如，图11描述的是用例分析方法作为一个角色设计者所执行的任务是在RUP中是如何表示的。
Figure 1 demonstrates the case in which a transaction contains two queries, each of which accesses data on different nodes.
图1演示了包含两个查询事务的情形，每个查询访问不同节点上的数据。
Figure 2: Use-case realization team sessions should include the system architect and developers responsible for implementing the use case.
图2：用例实现的团队会议应该包括系统架构师和负责实现用例的开发人员。
These tasks are performed by a new role: the Use-Case Analyst (Figure 13).
这些任务由一个新的角色执行：用例分析员(图13)。
The use case in Figure 2 is rather slim, indicating its name and some point-form notes describing the main idea.
图2中的用例相当简略，只是有名称和一些典型的注释来描述主要思想。
The dynamic GUI elements in this case are the category links (see Figure 1).
本例中的动态gui元素是一些类别链接(参见图1)。
Figure 9: the Use-Case Analysis model and its traceability links to the other model elements.
图9：用例分析模型，及其到其他模型元素的可追溯性链接。
Use case diagrams (see Figure 1 for an example) are often grouped to show a collective set of stakeholder needs.
用例图经常被分组来显示涉众们的需求集合（请看图1中的例子）。
Figure 47 shows the assembly diagram wiring for this use case.
图47显示了这个用例的组装图连接。
Figure 42 shows the assembly diagram wiring for this use case.
图42显示了这个用例的组装图连接。
A suspect link (red slashed arrow in Figure 5) indicates that test case TC1.2 may need to be revisited due to a change in use case UC1.3.
可疑链接(图5的红色斜线箭头)说明测例TC 1.2可能因用例uc1.3的改变而需要修订。
Figure 1 illustrates these use cases using a use case diagram.
图1用一个用例图阐明了这些用例。
Figure 2 shows a case where two external systems deposit files in different slots.
图2显示了一个将两个外部系统存放于不同数据槽中的示例。
Figure 37 shows the assembly diagram wiring for this use case.
图37显示这个用例的组装图连接。
Figure 37 shows the assembly diagram wiring for this use case.
图37显示这个用例的组装图连接。
应用推荐