图1用一个用例图阐明了这些用例。
Figure 1 illustrates these use cases using a use case diagram.
用例复审：用例和涉众复审的进度。
Use-case reviews: Progress on use cases and stakeholder reviews.
然而，用例和情境有局限性。
集成用例管理使用需求信息扩展了用例。
Integrated use case Management extends use cases with requirement information.
你怎样组织你的用例？
制定测试计划和用例。
我们在以下用例中使用这些因素。
用例和性能-理解与每个用例相关的系统质量。
Use cases and Performance - Understanding the system qualities associated with every use case.
用例实现的团队会议讨论和设计用例实现。
Use-case realization team session to discuss and design the use-case realizations.
所有的关联和依赖用例和执行者之间，以及用例之间。
All relationships and dependencies between use cases and actors and between use cases.
定义业务用例、建立到需求的跟踪关系(用例模型)。
Define the business use cases and establish traceability relationships to the requirements (use-case models).
用例只提供足以让涉众很好地了解用例的范围的信息。
The use case provides just enough information to give the stakeholders a good understanding of its scope.
每个用例极为内聚，但也因此造成用例间的高度耦合。
Each use case was extremely cohesive, but consequently the use cases had a high degree of coupling.
集成用例管理的价值就在于无缝地集成了用例与需求信息。
The value of Integrated use case Management is that it seamlessly integrates USES cases with your requirements information.
业务分析人员进行用例标识，并为每个用例创建功能规范。
The business analyst performs use case identification and creates functional specifications for each use case.
用例模型有两种基本风格：基本用例模型和系统用例模型。
There are two basic flavors of use case models: essential use case models, and system use case models.
用例和用例实现：详细说明将构建的所有业务服务的用例。
Use cases and use case realizations: Details use cases for all the business services that will be built.
用例模型还包括描述用户与系统如何交互的用例图和活动图。
The use case model also includes use case diagrams and activity diagrams that describe how users interact with the system.
用例和测试。
用例情节串联模板提供了另外一种描述用例实现的方式。
Use Case Storyboards provide an additional way of describing the realization of a Use Case.
通过添加项目名称、用例名称、用例细节等来编辑文件。
Edit the file by adding the project name, use-case name, use-case details, and so on.
在详细的检查我们的用例模型时，被包含和扩展的用例频繁的出现。
Included and extended use cases frequently emerged during detailed review of our use-case model.
用例描述用例流程的细节信息，包括简单介绍，步骤，选择的流程。
Use case description Details of the use case flow, including brief description, steps, alternate flows.
从字面上，停留在你的用例模型的顶层以避免“700用例并发症”。
Literally, stay on top of your use case model to avoid the 700 use case syndrome.
关于用例的书已经出了不少，它们论述了用例的风格、深度以及细节。
Many books have been written about use cases, discussing style, depth, and detail for writing them.
UML规定了建立用例图表的标准，但并不是为了编写用例描述的。
UML dictates standards for diagramming use cases but not for writing use case descriptions.
该部分讨论用例是用于什么的，并且最后介绍如何根据用例检查需求。
The section talks about what use cases are used for, and finally shows how to check requirements against use cases.
标识了用例后，用例中的活动集可以作为用例中的主要步骤进行记录。
Once use cases are being identified, the set of activities in a use case can be documented as major steps in a use case.
此类团队同时处理多个用例，每个成员都从事用例中有关其自身的方面。
This team works on several use cases simultaneously, each member working on their own aspects of the use case.
此类团队同时处理多个用例，每个成员都从事用例中有关其自身的方面。
This team works on several use cases simultaneously, each member working on their own aspects of the use case.
应用推荐