图3显示了一个可能的用例图。
你可以在图8中看到你的用例图。
图1用一个用例图阐明了这些用例。
Figure 1 illustrates these use cases using a use case diagram.
图7展示了这个系统的用例图。
使用用例图建模应用程序的行为。
用例图显示所有已确定的业务用例。
A use case diagram showing all of the identified Business use cases.
行为图的实例是活动图，用例图和序列图。
Example behavior diagrams are activity, use case, and sequence diagrams.
用例和用例图可以用于测试系统的以下方面。
Use cases and use case diagrams can be used for testing the following aspects of the system.
图7显示了你如何在RSA中创建一个用例图。
图2：与图1中显示的相同的零售系统用例图。
Figure 2: Use Case diagram for the same retail system shown in Figure 1.
发生的方式之一是将数据流图和用例图混淆在一起。
One way this occurs is by confusing data flow diagrams with use case diagrams.
用例模型还包括描述用户与系统如何交互的用例图和活动图。
The use case model also includes use case diagrams and activity diagrams that describe how users interact with the system.
用例图：可视化的描述系统用户，和系统为用户提供的服务。
Use case diagram: A visual representation of system users (actors) and the services they request from the system.
用例图经常被分组来显示涉众们的需求集合（请看图1中的例子）。
Use case diagrams (see Figure 1 for an example) are often grouped to show a collective set of stakeholder needs.
当我们从用例图转入到序列图和类图时，马上就会注意到已知的参与者的影响。
As we move from use case diagrams into sequence and class diagrams, we will immediately notice the impact of known actors.
UML中能算是高层次抽象的部分只有用例图，而这是在完全失却精确性的情况下。
The only part of UML that is on a high level of abstraction is the Use Case diagram, and that's only at the total loss of precision.
为了能够依靠用例来测试，除了用例描述和用例图之外，还需要有关特定方面的额外信息。
In order to be able to test by means of use cases, besides the use case description and a use case diagram, additional information regarding specific aspects is required.
把你已经创建好的项目和类图作为起始点，创建一个用例图以便使你了解应用程序的行为。
Using your project and the class diagram you have already created as a starting point, create a use case diagram to make sure you understand the behaviour of your application.
早期的频繁的客户接触与简单的需求电子数据表代替了传统的功能规格说明书和复杂的用例图。
Early and frequent customer contact combined with a simple requirements spreadsheet replace traditional functional specifications and sophisticated use case diagrams.
所有内容都来自于工作说明，我们得到特性列表和用例图，分解问题，然后选择一个用例开始迭代。
All from a statement of work, we can derive the feature list and use case diagrams, break up the problem, and then pick a use case to start to iterate.
他首先访问更新过的用例图以及序列图来看看这个新变更是如何影响整个应用软件，以及他正在工作的组件的。
He first accesses the updated use case diagram and sequence diagram to see how the new change will affect the application as a whole, as well as the components he is working on.
举个例子，一个团队可能使用用例图传达功能需求，然而另外那个团队却可能使用传统的“应该……”这种表述方式。
For instance, one team might express functional requirements as use cases, whereas another might express them as traditional "shall" statements.
Rhapsody是个双向的模型驱动解决方案，可以通过需求图、用例图、序列图、活动图以及状态图捕获项目需求。
Rhapsody is a round-trip model driven solution and supports capturing the project requirements using requirements diagrams, use-case diagrams, sequence diagrams, activity diagrams and state charts.
UML规范给图类型提供特定的文本值。 （举例来说，sd代表序列图，activity代表活动图，usecase代表用例图）。
The UML specification provides specific text values for diagram types (e.g., sd = Sequence Diagram, activity = Activity Diagram, and use case = Use Case Diagram).
您可以为RationalRequirementsComposer中任意类型的工件(文本文件，用户界面草图，用例图等等)创建模板。
You can create templates for any artifact with a type that is native to Rational Requirements Composer (text documents, user interface sketches, use case diagrams, and so forth).
图1说明了此示例系统中的用例，图2的活动图表中介绍了其中用例的执行顺序。
Figure 1 illustrates the use cases in this sample system, and the sequence in which the use cases are executed is shown in the activity diagram in Figure 2.
这是分区图的一个佳例，它展示的空间分布极具意义。
The above is a very good example of partition chart in which spatial trends are meaningful.
开发者可以使用生成的图快速了解用例，并找到问题的根源。
Developers use the generated diagrams to quickly understand the use case and to find the source of defects.
开发者可以使用生成的图快速了解用例，并找到问题的根源。
Developers use the generated diagrams to quickly understand the use case and to find the source of defects.
应用推荐