如何确定用户/参与者。例如。用户向管理员提供信息以与系统交互
如果客户提供管理员用于与系统交互的信息,我是否将参与者指定为与系统交互的用户或管理员。
同样在事件表中,来源将是与上述问题相同的参与者吗?
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 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
答案是:这取决于您的问题背景。
您设计系统是为了满足客户的需求还是管理员的需求?
在实践中,即使对于场景 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?
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.