如何确定用户/参与者。例如。用户向管理员提供信息以与系统交互

发布于 2024-12-04 21:37:48 字数 84 浏览 5 评论 0原文

如果客户提供管理员用于与系统交互的信息,我是否将参与者指定为与系统交互的用户或管理员。

同样在事件表中,来源将是与上述问题相同的参与者吗?

In an event like a customer provides information that a admin person uses to interact with system, do i specify the actor as the user or the admin who interacts with system.

Also in Event Table, Source will be the same actor as the above question?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

坚持沉默 2024-12-11 21:37:48

答案是:这取决于您的问题背景。

您设计系统是为了满足客户的需求还是管理员的需求?

  • 如果是客户,那么参与者就是客户。然而在这种情况下,您的用例有效地代表了一个业务流程。第 1 步是手动步骤,客户将信息传递给管理员。在步骤 2 中,管理员输入数据。这意味着步骤 2 实际上本身就是一个系统级用例。
  • 如果是管理员,那么更高级别的业务流程超出了您的范围 - 因此您只需处理系统级别的用例(上面的步骤 2)。在这种情况下,参与者是管理员,并且您不指定客户作为源。

在实践中,即使对于场景 2,在评论中值得注意的是,信息来自客户到管理员。但是,从管理员的角度(而不是客户的角度)设计 UI 非常重要。管理员通常会多次执行相同的操作,因此需要一个高效的界面。客户执行操作的频率可能要低得多,因此需要一个提供更多结构和支持的界面(例如“向导”)。强迫一个人使用为另一个人设计的界面可能会导致挫败感、效率低下和/或失败。

嗯。

Answer is: it depends on your problem context.

Are you designing the system to meet the Customer's needs - or the Administrator's?

  • If it's the Customer, then the Actor is the Customer. However in this case, your Use Case effectively represents a Business Process. Step 1 is a manual step in which the Customer passes the info to the admin. In step 2 the Admin enters the data. Which means step 2 is actually a system-level Use Case in its own right.
  • If it's the Admin then the higher level business process is outside your scope - so you only have to deal with the system level Use Case (step 2 above). In which case the Actor is the admin and you don't specify customer as source.

In practice, even for scenario 2, it's worth noting in comments somewhere that the info comes from the customer to the admin. However, it's important you design the UI from the admin's perspective - not the customer's. An admin will typically perform the same operation many times, so needs an interface that is efficient. A customer might perform the operation much less frequently so needs an interface that provides more structure and support (e.g. "wizards"). Forcing one to use an interface designed for the other can cause frustration, innefficiency and/or failure.

hth.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文