This call and response is integral to the use case.
这个调用和响应对于用例来说是完整的。
This statement serves as the use case name.
这个陈述作为这个用例的名称。
Each use case therefore has a goal.
因此每一个用例都有一个目标。
This is explained further in the next use case.
这一点将在下一个用例中详细解释。
Of course this is just a simple use case.
当然，这只是一个简单的使用场景。
In this approach, each use case is tested.
用这种方法，每个用例都要测试。
Also note the style of the use case.
也请注意用例描述的文字风格。
This use case prevents payments on the claim.
本用例阻止了对索赔的支付。
Figure 3 shows a possible use case diagram.
图3显示了一个可能的用例图。
A business use case will become a subsystem.
业务用例将变成一个子系统。
Provides sample code for the use case described.
为所述的用例提供样例代码。
XPDL also supports this use case.
XPDL也支持这个用例。
In such instances, you can duplicate the use case, assign each use case one primary persona, and create a separate user interface for every use case.
在这种情况下，您可以复制用例，为一个主要角色分配每个用例，并为每个用例创建分开的界面。
This use case receives data from Tax and Wage as noted in the initial claim use case.
正如最初索赔申请用例所提到的那样，本用例从税务或工资系统得到数据。
Literally, stay on top of your use case model to avoid the 700 use case syndrome.
从字面上，停留在你的用例模型的顶层以避免“700用例并发症”。
Design use-case realizations in team sessions.
在团队会议上设计用例实现。
Each user performs a use case and then waits for 120 seconds before repeating the use case.
每一个用户都会执行一个测试用例然后等待120秒再去重复用例。
The Use Case Realization, of course, links to the Use Case it realizes.
当然，这个用例实现链接到它所实现的用例上面。
The business analyst performs use case identification and creates functional specifications for each use case.
业务分析人员进行用例标识，并为每个用例创建功能规范。
A use case model consists of a diagram and a set of descriptions that clarify the use case.
一个用例模型由一张图表和一组阐明该用例的描述组成。
If you do use-case driven development, a usage scenario is typically an instance of a complete use case scenario, or a portion of the use case scenario.
如果你确实执行了用例驱动式开发，那么使用场景就是一个典型的完整用例情景的实例，或者用例情景的一部分。
Use case transactions, being round trips, should be expected everywhere in the use case.
使用当作环形路线的用例事务，可以在用例中随处可见。
The Use Case Model Overview is the final output of the use case modeling.
用例模型概述是用例建模的一种最终输出物。
Therefore, roles are similar to control objects in analysis use-case realizations or business workers in business use-case realizations.
所以，角色与在分析中的用例实现的控制组件或在商业中的用例实现的商人有相似之处。
Use case description Details of the use case flow, including brief description, steps, alternate flows.
用例描述用例流程的细节信息，包括简单介绍，步骤，选择的流程。
Business use-case specifications.
业务用例规格说明。
There are two basic flavors of use case models: essential use case models, and system use case models.
用例模型有两种基本风格：基本用例模型和系统用例模型。
Use case E describes this approach.
用例E描述这种方法。
Use-case types are more like use-case patterns — design patterns — but at the use-case level.
用例类型更像是用例模式——设计模式——但是是在用例级别。
Use-case types are more like use-case patterns — design patterns — but at the use-case level.
用例类型更像是用例模式——设计模式——但是是在用例级别。
应用推荐