Highly reused business tasks are modeled as system use cases.
高可复用的业务任务被建模成为系统用例。
A UML diagram also captures which System use Cases support which user goal.
uml图还能获取哪个系统用例支持哪个用户目标。
At the system use-case level, a test suite implements the use-case scenarios.
在系统用例层面，一个测试套件实现用例场景。
This diagram has already been shown in Figure 13, and represents the System Use Case Model.
此图已经在图13中显示过了，并且表示系统用例模型。
RSA/M also contains the mappings from process tasks to system use cases that support those tasks.
RSA/M也包含从过程任务到支持这些任务的系统用例的映射。
This activity identifies System Use Cases and System Actors, which in the end are User Roles.
这种活动确定了系统用例和系统参与者，它们最终是用户角色。
The resulting System Use Case model is shown in Figure 13, and includes all the use cases identified.
结果产生的系统用例模型如图13所示，并且包括已确定的所有用例。
The processes and services in the system use the data elements as part of their message exchange.
系统中的流程与服务将数据元素作为它们之间消息交换的一部分。
There are two basic flavors of use case models: essential use case models, and system use case models.
用例模型有两种基本风格：基本用例模型和系统用例模型。
Each system use case will manipulate some entities, and the entities are usually involved in multiple system use cases.
每个系统用例将操作一些实体，并且实体通常被包括在多个系统用例中。
The credit bureau system use case, on the other hand, says "the credit institution actor requests a copy of a credit report."
另一方面，商业资信咨询机构系统用例表示“这个信用机构参与者请求信用报告的一个副本。”
The test suites can be used to implement the automation test strategy at the business level or at the system use-case level.
测试套件可以在业务层面或者系统用例层面被用来实现自动化测试策略。
The system use case makes references to screens and reports, such as "UI23 Security Login Screen" and "UI89 Enrollment Summary Report."
系统用例提及屏幕和报告，如“UI23安全性登录屏幕”和“UI89登记摘要报告”。
Each process will correspond to a system use case (except manual and customer experience processes that lie outside the system boundary).
每个流程都将与系统用例对应(位于系统边界外的手动流程和客户体验流程除外)。
System use cases often refer to major user interface (UI) elements, often called boundary or user interface items, such as HTML pages and reports.
系统用例经常引用主用户界面(UI)元素，这些元素常常称为“边界”或“用户界面”项，例如HTML页面和报表。
Note that the maximum number of user definable LVs is given by the maximum number of LVs per VG minus 1 because one LV is reserved for system use.
请注意，用户可定义LV的最大数目等于每个VG的LV最大数目减1，因为将保留一个LV给系统使用。
Business entities are handled and manipulated by a business process (i.e., business use cases), which are subsequently automated via system use cases.
业务实体通过一个业务过程(例如业务用例)被处理和操作，它们接着通过系统用例被自动化。
The processes in this layer lie outside the system boundary, and don't describe system functions, so there's no need for a corresponding system use case.
这个层中的流程位于系统边界之外，并不描述系统功能，因此不需要对应的系统用例。
Link the Business Model to the System Model by means of dependencies between the System Use Case Realizations and the Business Use Case Realizations.
利用系统用例实现和业务用例实现间的依赖性将业务模型与系统模型连接起来。
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 fact, every message that enters into the worker can be thought to become the realization of a System Use Case implementing the worker's functionality.
实际上，每个进入操作者的消息可以被认为是实现操作者功能的系统用例的实现。
SV-4 Systems Functionality Description Identifies system behavior and the information flow related to that behavior. Activity Diagram for each system use case 8.
SV - 4系统功能描述确定系统行为及与该行为相关的信息流。
This system use case can be used to articulate the concepts for the point-to-point transactional model and its variations for the architecture phase of a project.
此系统用例可以用于说明点到点事务模型的概念及其在项目的体系结构设计阶段的变化。
12in The Object Advantage (Addison-Wesley, 1995, pg.173), E.A. Jacobsen introduces an algorithm used to map a business use case model onto a system use case model.
12在《The Object Advantage》(addison -Wesley, 1995，第173页)，E.A. Jacobsen介绍了一个算法，用于映射一个业务用例模型到一个系统用例模型。
We start the design of this service provider by creating a system use case that defines its requirements and a component called Invoicer that realizes the use case.
我们对服务提供者进行的设计，首先创建一个定义其需求的系统用例，以及一个被称作 Invoicer 的实现该用例的组件。
The TOC save area, compiler area, and linker area are all reserved for system use, and are not modified by programmers, but the programmer must reserve space for them.
TOC保存区、编译器区和链接器区都会为系统使用而预留出来，程序员不能对它们进行修改，但是必须要为它们预留空间。
This allows us to evaluate the completeness of the use-case model from a business perspective, as each system use case must support one or more business use cases.
这就允许我们从一种业务观点来评价用例模型的完整性，因为每个系统用例必须支持一个或更多的业务用例。
The first way the system use cases are realized is the traditional use case realization, which shows how the use case is realized in terms of a set of cooperating classes.
实现系统用例的第一种方式是传统的用例实现(usecase realization)，它显示出用例如何通过一系列协作类进行实现。
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的文档显示了从业务用例模型到业务对象模型和系统用例模型的演进；我们发现这是非常正确和有帮助的。
We start the design of this service provider by creating a system use case that defines its requirements and a Participant called Invoicer that realizes the use case, as shown in Figure 6.
在开始这个服务时，我们创建一个定义其需求的系统用例，以及一个叫做Invoicer 实现用例的参与者，如图 6 所示。
应用推荐