Figure 6a. Architect activities: use-case model refinement.
图6A.架构师活动：用例模型优化。
From there we selected the template for a RUP use-case model survey.
从中我们选择aRUPuse - case modelsurvey模板。
This doesn't mean that the Use-Case Model can only contain elements from the Vision.
这不意味着用例模型只能够包含来自于前景的元素。
The Use-Case Model in turn is the source for the subsequent Use-Case Specifications.
而用例模型又是随后的用例规格说明 的来源。
Included and extended use cases frequently emerged during detailed review of our use-case model.
在详细的检查我们的用例模型时，被包含和扩展的用例频繁的出现。
These mappings are used to identify the subset of the existing use-case model that is affected by the project.
这些映射是用于识别受项目所影响的现有用例模型的子集的。
Although it is true that these people do these things, it is not what you want to depict in your use-case model.
虽然，的确是这些人做这些事情，但您不想在用例模型中描述这些。
Each describes a different aspect of the system, such as the use-case model, the analysis model, and the design model.
每一个都描述了系统的不同方面，例如用例模型，分析模型以及设计模型。
Traceability links can be created between the test suite definition and the use-case model, as illustrated in Figure 12.
可追溯的连接可以在测试套件定义和用例模块之间建立，如图12所示。
In the end, we found consistency and frequent reviews to be key to success when presenting our use-case model to the customer.
最后我们发现当我们向客户展示我们的用例模型时，一致的并频繁的检查是成功的关键。
As we fleshed out the business use-case model, a number of objects emerged that were good candidates for the business object model.
当我们将业务用例模型充实起来时，对于业务对象模型来说将会出现一系列好的候选对象。
It is worth mentioning the central role played by the use-case model in this work as in any RUP-based software development project.
值得提到的是在此工作中的用例模型所扮演的重要角色与在任何基于RUP的软件开发项目中一样。
You have to evaluate the use-case model with respect to some frame of reference, such as business needs, business domain, and so on.
你必须应用一些参考框架来评价用例模型，例如业务要求，业务领域，等等。
For example, if a Use-Case Model is referenced by the contents of multiple projects, it should not reside in any of those referencing projects.
举例来说，如果一个用例模型被多个项目的内容所引用，那么它就不应当存在于任何一个引用项目中。
Often the dependency relationships are not immediately apparent, but are discovered as the use-case model and associated user interface evolve.
通常依赖关系不会立即显现，但会随着用例模型和相关用户界面的进化而逐渐显露。
The RUP documentation shows the evolution from business use-case model to business object model and system use-case model; we found this to be quite accurate and helpful.
RUP的文档显示了从业务用例模型到业务对象模型和系统用例模型的演进；我们发现这是非常正确和有帮助的。
Moreover the business workers that initiate those methods are to be traced to corresponding system actors (User Roles) living in the system Use Case model.
此外，发起那些方法的业务操作者将追溯到相应的位于系统用例模型中的系统参与者(用户角色)。
In particular, you will often have multiple choices about how to structure your use case model 11; when you do, align your use case model with the above attributes.
特别地，你将时常会有关于如何构建用例模型11的多种选择；当你这样做时，用上述的属性定位你的用例模型。
In previous columns, we have established a use case model in which actors represent external entities that interact with our system.
在前面的专栏文章中，我们构建了一个用例模型，参与者在其中表示与系统交互的外部实体。
The completed use case model should allow all the stakeholders to see how the system supports their roles.
完成后的用例模型应该允许所有的利益相关者看见系统是如何支持他们的角色的。
The resulting System Use Case model is shown in Figure 13, and includes all the use cases identified.
结果产生的系统用例模型如图13所示，并且包括已确定的所有用例。
An important thing not to do is to functionally decompose your use case model; that is, do not break your use cases into smaller parts.
一件重要的事情是不要把功能分解到你的用例模型中；即，不要把你的用例打破成较小的部分。
Literally, stay on top of your use case model to avoid the 700 use case syndrome.
从字面上，停留在你的用例模型的顶层以避免“700用例并发症”。
Testers can more efficiently plan and execute testing when employing the use case model.
当利用这些用例模式时，测试人员可用更有效地设计和执行测试。
Use case identification and documentation into a use case model (with actor association) is the first iteration of this overall activity.
标识用例并将其记录到用例模型中(包含参与者关联情况)是这个总体活动的第一个迭代。
When an organization is complex and trying to automate significant functions, a business use case model can be invaluable.
当一个复杂的开发组织试图自动处理重要的功能时，业务用例模型是非常宝贵的。
With a level of analysis performed at this point, a formal use case model can be created and documented.
此时通过执行某种级别的分析，可以创建并记录正式的用例模型。
This type of model, describing how a user interacts with the system, is usually referred to as a use case model.
模型的类别描述了用户怎样和系统交互，它经常被作为用例被提及。
A similar algorithm is used here to map a business use case model onto another business use case model in a different context.
这里使用一个类似的算法，把一个业务用例模型映射到不同语境中的另一个业务用例模型。
The use case model allows testers to visually identify their test cases, especially when the process includes a use case diagram.
用例模式允许测试人员从视觉上识别他们地测试用例，尤其是当这个过程包括一个用例图时。
应用推荐