多个参与者，相同的用例[用例] [英] Multiple Actors, Same Use Case [Use Case]

问题描述

我试图描述一个用例，其中系统中的多个参与者可以执行相同的活动。
例如

I'm trying to depict an use case where several actors within a system can perform the same activity. e.g.

让我们说（作为示例）我想将用例设为 Update Clients，但几个确定的参与者可以做到这一点。

Let's say (as an example) I want to make the use case "Update Clients" but several identified actors can do this.

Manager
Chief Executive
Customer Service Representative
System Administrator
Clerk

-我是否需要通过响应相同用例的角色来描述所有这些参与者？

-Do I need to depict all these actors by their roles ponting to the same use case?

Manager ------------------------------>  |-----------------|
Chief Executive ---------------------->  |                 |
Customer Service Representative ------>  | (Update Clients)|
System Administrator ----------------->  |                 |
Clerk -------------------------------->  |_________________|

-我需要为每个参与者创建不同的用例吗？

-Do I need to make a different use case for each actor?

                                         |-----------------|
                                         |                 |
Manager ------------------------------>  | (Update Clients)|
                                         |                 |
                                         |_________________|

                                         |-----------------|
                                         |                 |
Chief Executive ---------------------->  | (Update Clients)|
                                         |                 |
                                         |_________________|

...

                                         |-----------------|
                                         |                 |
Clerk -------------------------------->  | (Update Clients)|
                                         |                 |
                                         |_________________|

我是否需要通过使用一般演员来使所有演员全球化（如果是，如何是吗？）？

Do I need to globalize all actors by using a "general" actor (If so, How do I do it?)?

                                         |-----------------|
                                         |                 |
General Actor ------------------------>  | (Update Clients)|
                                         |                 |
                                         |_________________|

推荐答案

也许有更多解决此问题的方法，但以下推荐似乎是最合逻辑的。

There are perhaps more approaches to this problem, but following recommendation seems most logical.

在这种情况下，您应该只使用一个具有名称的Actor，例如用户。将公司的所有不同职位加为演员，您将一事无成。

In this case you should use just one Actor with name e.g. User. You will gain nothing adding all different positions in company as actors.

但这并不意味着您必须始终只有一位演员，请参见下图：

But it does not mean that you must allways have only one Actor, see following diagram:

将用例绑定到业务流程图更为重要。这样就可以记录支持业务流程的所有用例。

It is more important to bind your Use cases to Bussiness process diagram. Thus you can document, how all the use cases are needed to support business processes.

从BPMN模型到用例的链接很重要，因为您可以文档，什么情况/过程使用户需要使用系统。

The link from BPMN model to the Use case is important because there you can document, what situation/process makes the user need to use the system. Something happens outside the modeled system (IS) that creates the need to run that particular Use case.

但是，用例与对象中的类或方法不同。程序。当寻找用例时，您可能会在第一阶段和第二阶段中对它们进行建模，以寻找它们之间的关系-请参阅检查客户数据，编辑客户和编辑客户资料中的所有图片更新客户端用例。

But the Use case is not the same thing as class or method in a program. When you look for Use cases you will probably model more of them at the first and in the second phase you look for relation between them - see the picture where "Check client data", "Edit clients" and "Edit client profile" all include the "Update client" use case.

因此，我认为您不必担心建模更多的用例，而不需要在程序中有屏幕或方法。结束。稍后，您可以使用包含，扩展...对用例进行内部建模，然后在此处记录它们的共同点。

So I think you do not need to worry that you model more Use cases than there will be screens or methods in your program at the end. Later you can model the inside of Use cases using Include, Extends... and there you can document what they have in common.

这篇关于多个参与者，相同的用例[用例]的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！