高可复用的业务任务被建模成为系统用例。
Highly reused business tasks are modeled as system use cases.
此图已经在图13中显示过了，并且表示系统用例模型。
This diagram has already been shown in Figure 13, and represents the System Use Case Model.
在系统用例层面，一个测试套件实现用例场景。
At the system use-case level, a test suite implements the use-case scenarios.
uml图还能获取哪个系统用例支持哪个用户目标。
A UML diagram also captures which System use Cases support which user goal.
RSA/M也包含从过程任务到支持这些任务的系统用例的映射。
RSA/M also contains the mappings from process tasks to system use cases that support those tasks.
用例模型有两种基本风格：基本用例模型和系统用例模型。
There are two basic flavors of use case models: essential use case models, and system use case models.
这种活动确定了系统用例和系统参与者，它们最终是用户角色。
This activity identifies System Use Cases and System Actors, which in the end are User Roles.
实际上，每个进入操作者的消息可以被认为是实现操作者功能的系统用例的实现。
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.
每个系统用例将操作一些实体，并且实体通常被包括在多个系统用例中。
Each system use case will manipulate some entities, and the entities are usually involved in multiple system use cases.
测试套件可以在业务层面或者系统用例层面被用来实现自动化测试策略。
The test suites can be used to implement the automation test strategy at the business level or at the system use-case level.
结果产生的系统用例模型如图13所示，并且包括已确定的所有用例。
The resulting System Use Case model is shown in Figure 13, and includes all the use cases identified.
每个流程都将与系统用例对应(位于系统边界外的手动流程和客户体验流程除外)。
Each process will correspond to a system use case (except manual and customer experience processes that lie outside the system boundary).
我不打算再介绍这些题目，而是要阐明如何将业务用例同系统用例分开记录。
My purpose is not to discuss these subjects again, but to clarify how business use cases and system USES cases can be documented separately.
利用系统用例实现和业务用例实现间的依赖性将业务模型与系统模型连接起来。
Link the Business Model to the System Model by means of dependencies between the System Use Case Realizations and the Business Use Case Realizations.
系统用例提及屏幕和报告，如“UI23安全性登录屏幕”和“UI89登记摘要报告”。
The system use case makes references to screens and reports, such as "UI23 Security Login Screen" and "UI89 Enrollment Summary Report."
这个层中的流程位于系统边界之外，并不描述系统功能，因此不需要对应的系统用例。
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.
此系统用例可以用于说明点到点事务模型的概念及其在项目的体系结构设计阶段的变化。
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.
业务实体通过一个业务过程(例如业务用例)被处理和操作，它们接着通过系统用例被自动化。
Business entities are handled and manipulated by a business process (i.e., business use cases), which are subsequently automated via 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."
此外，发起那些方法的业务操作者将追溯到相应的位于系统用例模型中的系统参与者(用户角色)。
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.
最后，产品特性被分解成系统用例以及能够被进一步分析并作为系统组件的低级需求细化的补充需求。
Finally, the product features are broken down into system use cases and supplementary requirements that can be further analyzed and detailed as low-level requirements for the system components.
如果你从详细的用例(基于浏览器的系统用例)，每次改变你的实现平台的时候，你都得重写整个用例。
If you started with a browser-specific version, you would have to re-write the whole thing from scratch when you changed your target platform.
这就允许我们从一种业务观点来评价用例模型的完整性，因为每个系统用例必须支持一个或更多的业务用例。
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.
论文重点分析了代收费系统的业务需求，并以代收电信资费为例概括出系统用例图，设计出主要业务用例。
Paper focused on analyzing business processes needs of collection charges and generalized systems use case diagram and designed major business cases.
RUP的文档显示了从业务用例模型到业务对象模型和系统用例模型的演进；我们发现这是非常正确和有帮助的。
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.
并对系统功能、数据交换流程作了进一步的研究，最后通过系统用例分析，明确了系统管理及数据传输的过程。
And system functions, data exchange process further, the final system through the use-case analysis, a clear system management and data transmission.
在所恢复的遗留系统的抽象结构中(与系统用例相关联的分析模型)，我们现在必须找到实现它的信息系统的组件。
From the recovered abstract structure of the legacy system (the Analysis Model associated to the system Use Cases), we must now find the components of the information system that implement it.
内部交互可能由参与者启动(如果子系统用例是交互的基础)，但它更可能是由叫作Sender的普通类启动的。
An internal interaction might be initiated by an actor (if subsystem use cases are the basis for the interaction), but more likely it would be started by a generic class called Sender.
系统用例经常引用主用户界面(UI)元素，这些元素常常称为“边界”或“用户界面”项，例如HTML页面和报表。
System use cases often refer to major user interface (UI) elements, often called boundary or user interface items, such as HTML pages and reports.
将系统视为一个黑盒，确定与系统(系统参与者)交互的环境元素和实际的相互作用及结果(系统用例及产生的服务)。
Treating the system as a black box, identify environmental elements that interact with the system (the system actors) and the actual interactions and results (system use cases and resulting services).
应用推荐