Using use case diagrams to model application behaviour.
使用用例图建模应用程序的行为。
As such, let's take a look at your system using UML use case diagrams.
同样，让我们看看使用UML用例图的系统。
Use case diagrams, which demonstrate how to add UML diagrams to the report.
用例图，它阐述了如何将UM l图添加到这个报表中？
One way this occurs is by confusing data flow diagrams with use case diagrams.
发生的方式之一是将数据流图和用例图混淆在一起。
Use case diagrams are among the standard Unified Modeling Language (UML) artifacts.
用例图表是标准的“统一建模语言(uml)”构件之一。
Use cases and use case diagrams can be used for testing the following aspects of the system.
用例和用例图可以用于测试系统的以下方面。
Over time, it has become increasingly common for them to be graphically represented in use case diagrams.
长期以来，在用例图中以图形的格式表示就变得越来越普遍。
Use case diagrams (see Figure 1 for an example) are often grouped to show a collective set of stakeholder needs.
用例图经常被分组来显示涉众们的需求集合（请看图1中的例子）。
Of course, you can create other UML diagrams, such as use case diagrams and sequence diagrams, to document your exchange.
当然，您可以创建其他uml范式(比如用例图表和序列图表)来归档您的交换。
As we move from use case diagrams into sequence and class diagrams, we will immediately notice the impact of known actors.
当我们从用例图转入到序列图和类图时，马上就会注意到已知的参与者的影响。
The use case model also includes use case diagrams and activity diagrams that describe how users interact with the system.
用例模型还包括描述用户与系统如何交互的用例图和活动图。
Use case diagrams are constructs that model the main functions of a system, and identify initial interactions between the system and its environment.
用例图是用来建模系统主要功能的结构，可以识别出最初的系统与它的开发环境之间的交互。
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.
所有内容都来自于工作说明，我们得到特性列表和用例图，分解问题，然后选择一个用例开始迭代。
Early and frequent customer contact combined with a simple requirements spreadsheet replace traditional functional specifications and sophisticated use case diagrams.
早期的频繁的客户接触与简单的需求电子数据表代替了传统的功能规格说明书和复杂的用例图。
For example, in UML use case diagrams it is common to apply stereotypes such as and to associations between use cases (see the tip use case Modeling Tips for details).
例如，在UML用例图中，通常将原型(例如，和)应用于用例之间的关联。(有关详细信息，请参阅用例建模技巧)。
As mentioned above, use cases may be completely text-based with no supporting diagrams, or they may be illustrated using only simple use case diagrams as shown in Figure 1.
正如上面所提到的，用例可能完全是不带支持的基于文本的图，或者它们可能仅仅使用简单的用例图来描述，如图1所示。
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).
您可以为RationalRequirementsComposer中任意类型的工件(文本文件，用户界面草图，用例图等等)创建模板。
The Mirror Image and Session Facade patterns are useful for changing actors in use case diagrams into valid abstractions in class diagrams, which ultimately results in a cleaner translation to code.
对于将用例图中的参与者转换成类图中有效的抽象，镜像映象模式和会话虚包模式是很有用的，这样最终将能够更清楚地转换成代码。
Example behavior diagrams are activity, use case, and sequence diagrams.
行为图的实例是活动图，用例图和序列图。
In analysis, our use case realization contains only analysis classes and objects, which may populate various UML diagrams such as class diagrams and interaction diagrams.
在分析阶段，我们的用例实现只包括分析类及分析对象，它们能组装成不同的UML图如类图和交互图。
Behavior diagrams, such as use case and activity diagrams, represent general types of behavior.
行为图，比如用例和活动图，代表普通类型的行为。
We've partially worked through sequence diagrams in conjunction with use case modeling in the two previous columns.
在先前的两个专栏中，我们已经完成了一部分将序列图同用例建模关联起来的工作。
Developers, testers and managers can search this database by use case name and view the related sequence diagrams in a browser.
开发者、测试人员和经理都可以通过用例名来搜索这个数据库，并在浏览器中查看相关的序列图。
You might also want to continue elaborating your requirements by linking to artifacts, such as: rich text documents, use-case diagrams, business models, and storyboards.
您可能还想链接到一些工件，例如：多格式文件、用例图、业务模型以及脚本，来继续加工您的需求。
Developers use the generated diagrams to quickly understand the use case and to find the source of defects.
开发者可以使用生成的图快速了解用例，并找到问题的根源。
If you're modeling a use case scenario, your sequence diagrams will generally represent an interaction with an external entity.
如果正在建立用例方案的模型，那么序列图通常表示与外部实体的交互。
For example, a system designer is interested in the logical and physical aspects of a system, so the most useful forms are class and sequence diagrams rather than use-case and activity diagrams.
例如，系统设计人员对系统的逻辑和物理方面感兴趣，因此最有用的形式就是类和序列关系图，而不是用例和活动关系图。
Identifying and naming a use case realization provides traceability from the interactions diagrams and textual commentary back to the use case.
确认并命名一个用例实现保证了交互图和文本注释回到用例的可追踪性。
Examples are use cases, use case models, business rules, classes, class diagrams, sequence diagrams, the data model, and supplementary specifications.
例子是用例、用例模型、业务规则、类、类图、序列图、数据模型和补充规约。
Examples are use cases, use case models, business rules, classes, class diagrams, sequence diagrams, the data model, and supplementary specifications.
例子是用例、用例模型、业务规则、类、类图、序列图、数据模型和补充规约。
应用推荐