用例图 登录用例 [英] Use Case Diagram Log On Use Case

问题描述

假设我有以下演员:

• 用户

假设我有以下用例:

• 注册
• 登录
• 完成人口统计调查
• 选择模块

我对如何正确建模登录用例感到困惑.目前我有一个图表，在用户和登录之间有关系.

I'm confused as to how to properly model the Log On use case. Currently I have a diagram that has a relationship between the User and Log On.

由于用户需要登录才能完成这些功能，因此是否应该将登录用例包含在每个用例(注册除外)中(包括关系)?

Should the Log On use case be included (includes relationship) with each use case (with the exception of Register) since the user needs to be logged in to complete those functions?

推荐答案

如果用户需要登录作为另一个用例的一部分(例如 Complete Demographics Survey 开始如果用户尚未登录，则提示用户登录)，然后是(因为 Log On 的常见行为就像执行子例程调用一样).

If the user is required to login as part of another use case (e.g. Complete Demographics Survey begins with prompting the user for login if they were not already logged), then yes (because the common behavior of Log On is executed as if it were a subroutine call).

另一方面，如果用户只要求登录(例如，如果他们没有登录，操作将被拒绝)，那么它更多是一个前提而不是包含关系.

On the other hand, if the user is only required to be logged in (e.g. if they are not logged the operation is rejected), then it is more a precondition than a include relationship.

这篇关于用例图 登录用例的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！