Associating a System use case with a task.
将系统用例与任务联系起来。
Comparing a system use case and an essential use case.
比较系统用例和基本用例。
The system use case has more steps than the essential use case.
系统用例的步骤比基本用例的步骤多。
The system use case has many implementation details embedded within it.
系统用例嵌入了很多实现细节。
Figure 12 represents the business worker with his corresponding system use case.
图12表示业务工人及其相应的系统用例。
This diagram has already been shown in Figure 13, and represents the System Use Case Model.
此图已经在图13中显示过了，并且表示系统用例模型。
The resulting System Use Case model is shown in Figure 13, and includes all the use cases identified.
结果产生的系统用例模型如图13所示，并且包括已确定的所有用例。
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 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).
每个流程都将与系统用例对应(位于系统边界外的手动流程和客户体验流程除外)。
The thesis describes the system function modules in detail using modular structure, then draws the system use case model on this basic.
本系统采用的是模块化结构设计对系统的功能模块进行了详细的描述，在此基础上绘制了系统模块的用例模型。
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.
实际上，每个进入操作者的消息可以被认为是实现操作者功能的系统用例的实现。
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.
此系统用例可以用于说明点到点事务模型的概念及其在项目的体系结构设计阶段的变化。
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.
这就允许我们从一种业务观点来评价用例模型的完整性，因为每个系统用例必须支持一个或更多的业务用例。
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 的实现该用例的组件。
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系统功能描述确定系统行为及与该行为相关的信息流。
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 所示。
If, for example, it is decided that the Scheduler worker has to be automated, the sequence diagram shown in Figure 11 provides useful information to create the Scheduler System use Case model.
例如，如果决定必须自动化scheduler操作者，那么图11中所示的序列图提供有用的信息来创建Scheduler系统用例模型。
Since we are doing an object-oriented software system, the behavior of our use case must be carried out by the classes and objects in our system.
由于我们是在设计一个面向对象的软件系统，我们的用例行为需要由我们系统中的一些对象和类来执行。
I'm most concerned in this discussion with clarifying the relationship between user interfaces, system interfaces, and use case descriptions.
这次讨论中，我更关心的是阐明用户接口、系统接口和用例描述之间的关系。
In this use case, the system interface component is the implementation of such as contract.
在此用例中，系统接口组件是契约之类内容的实现。
Use cases and Performance - Understanding the system qualities associated with every use case.
用例和性能-理解与每个用例相关的系统质量。
Use case diagram Provides a behavioral view of system context by displaying actors external to the system who go to the system to achieve a specific, valued result (use case).
用例图通过向即将使用系统的人员提供一个系统背景的行为性视图，来取得一个特定有价值的结果(用例)。
These use case realizations model how the parts of the system interact within the context of a specific use case.
这些用例实现对系统的一些部分如何在具体用例环境中交互进行建模。
应用推荐