But there is also another aspect of system's design that comes into play as soon as the system Actor is an actual User.
但是当系统活动者是一个真实的用户的时候，还有系统设计的另一个方面开始活动。
Additionally, the same class diagram also describes the relationship between each User Goal identified during the IaD activity and the corresponding System Actor.
此外，同样的类图也描述了在IaD活动中确定的每个用户目标和相应的系统参与者之间的关系。
In the last column in the UML workbook series, we devised a system that would interact with both a human actor (a loan applicant) and an external system actor (a credit bureau).
在UML工作簿系列的前一个专栏中，我们设计了一个既能与参与人(贷款申请人)又能与外部系统参与者(征信所)交互的系统。
At this level, the system to be developed serves as the black box central actor.
在这个层次，要开发的系统作为黑盒子中心的演员。
Then the system reacts; i.e., it processes the input and returns the result to the Actor.
此时系统发生反应。它处理输入并将处理的结果返回给用户。
As the Access class serves as the part of your system that interacts with the other pieces, you'll model that as an actor within your diagram.
因为访问类为你的系统提供与其它块交互的服务，所以在你的图表中，你要建模它为一个主角。
Applying the scoping rules for the system level, the online order system serves as the black box central actor.
应用了系统层次的范围规则，在线定单系统就作为黑盒子中心的演员。
Each use case should specify a significant chunk of functionality and show how the system provides value to an actor.
每个用例应指定一个有意义的功能块，说明系统如何为参与者提供有价值的东西。
As such, we are not dealing with individual people or systems; rather, we have encapsulated the details of those who interact with the system in an abstract entity that we call the actor.
因此，我们不是在处理个别的人或系统；相反地，我们把那些与系统交互的人或系统的细节封装到抽象的实体中，我们称它为参与者。
This is also true in the third transaction, where the system part of the credit bureau transaction is a subset of the actor part of the third transaction.
这对于第三个事务处理也是一样的，商业资信咨询机构事务处理的系统部分是第三个事务处理的参与者部分的一个子集。
Thus, the actor part of the credit bureau transaction is a subset of the system part of the second transaction of the loan submission system.
这样，商业资信咨询机构事务处理的参与者部分是贷款提交系统的第二个事务处理的系统部分的一个子集。
Specifically, let's look at the system part of the second transaction and the actor part of the third transaction.
尤其得让我们查看第二个事务处理的系统部分和第三个事务处理的参与者部分。
In a typical use case, the flow of activity is driven by the interaction of a particular actor with the system toward the execution of a specific goal (for example, "managing a water-health sample").
在典型的用例中，活动流是由特定参与者与系统间以执行特定目标为目的而开展的交互驱动的(例如，“管理水健康状况样本”)。
Develop a model of the user interface flow, showing how a given actor from the business process will interact with the system during a typical "session".
开发一个用户界面流程模型，显示在典型“会话”期间来自业务流程的给定参与者如何与系统相交互。
The system: Processes events generated by the Actor; in some use cases, such as this one, the system may need to communicate with other systems and so use a system Interface.
系统：处理参与者生成的事件；在某些用例中(如本文中的用例)可能需要与其他系统进行通信，因此要使用系统接口。
Alternatively, the system may "see" our actor as a more complex element.
系统还可以将我们的参与者“看作”是更复杂的元素。
A hardware or software failure can unintentionally destroy a static life cycle resource, as opposed to a system management actor, which can intentionally destroy the resource.
硬件或软件可能会无意地销毁一个静态生命周期资源，而一个系统管理参与者可以有意地销毁该资源。
All transactions are composed of an actor and a system interacting.
所有的事务处理是由一个参与者和一个系统交互组成。
The context level provides a black box view of the system, external actors, and the boundaries of system/actor interaction.
范围级别提供了一个系统、外部参与者以及系统或参与者交互边界的黑盒。
UML defines a use case as "A description of a set of sequences of actions, including variants, that a system performs that yields an observable result of value to a particular actor.
UML 将一个用例定义为“一个系统执行的一系列行为的描述，包括变量，它将生成特殊参与者所得值的可观测结果。”
In other words, in one transaction the actor performs some action which is input for the system.
换句话说，在一次事务中，用户运行输入系统的一些操作。
While you are in an analysis mindset, your use case description will generally address only the behavior of the system that is externally visible to an actor using the system.
当你在进行分析的时候，你的用例描述只记录了从系统外面的用户角度来看，系统的行为是什么样子的。
In particular, the interaction between the main actor and the system involves a boundary class.
尤其是主要参与者与系统的交互，其包含了边界类。
The number of steps in a use case flow, which describes the interaction between an actor and the system, can also vary widely both across and within scenarios.
在一个用例流程里的步骤的数量，描述了角色与系统之间的关系，也能够发生很大的改变。
This has been represented in Figure 1 by drawing an actor inside of the system which is acting with another system.
在图1中，表示它的方法是把参与者画在参与另一个系统的系统中。
Actor definitions: a textual description of the requestors of services provided by your system, and services provided to your system.
角色定义：用文字描述系统功能，和系统所需的服务。
Another way to look at it is that a use case describes a way in which a real-world actor interacts with the system.
认识它的另一种途径是：用例描述实际参与者与系统交互的方式。
We'll start with an actor that represents an outside system (CreditInstitution) requesting a credit report.
我们将以代表请求一份信用报告的一个外部系统(CreditInstitution)的参与者开始。
The credit bureau system use case, on the other hand, says "the credit institution actor requests a copy of a credit report."
另一方面，商业资信咨询机构系统用例表示“这个信用机构参与者请求信用报告的一个副本。”
The credit bureau system use case, on the other hand, says "the credit institution actor requests a copy of a credit report."
另一方面，商业资信咨询机构系统用例表示“这个信用机构参与者请求信用报告的一个副本。”
应用推荐