包含或扩展用例关系?

发布于 2024-10-13 12:43:56 字数 154 浏览 7 评论 0原文

我不知道在我的用例中应该使用哪种关系。假设参与者是可以管理帐户的用户:-创建; -删除; -更新;

我是否应该将“管理帐户”作为用例,然后将“创建”、“删除”、“更新”链接到它 - 如果是 - 扩展或包含关系,有什么想法吗?或者如果我将创建、删除、更新作为单独的用例保留会更好?

I can't figure out which relationship I should use in my use case. Let's say the actor is User who can Manage account:-Create; -Delete; -Update;

Any ideas whether I should make Manage Account as a use case and then link Create, delete, update to it - if yes - extend or include relationship? Or it would be better if I leave as separate use cases Create, Delete, Update?

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

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

发布评论

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

评论(3

不念旧人 2024-10-20 12:43:56

我不喜欢“Manage-X”用例。正如您的帖子所暗示的那样,“管理”实际上是许多交替的独立任务的统称。结果是用例主体看起来不正确:

If the User selects 'Create' then {...}
else if the User selects 'Update' then {...}

...等等。

最好单独展示它们。如果您的模型变得很大 - 并且您需要一种组织方式 - 那么为相关 UC 创建一个,而不是“超级 UC”。因此,在您的情况下,名为管理帐户的包包含UC开立帐户更新帐户

I'm not a fan of "Manage-X" Use Cases. As your post suggests, 'Manage' is really a collective term for a number of alternate, independent tasks. The result is a Use Case body that doesn't look right:

If the User selects 'Create' then {...}
else if the User selects 'Update' then {...}

...etc.

Better show them individually. If your model gets big - and you need a way to organise - then create a package for related UCs, not a 'super UC'. So in your case, a package named Manage Account containing UCs Open Account, Update Account, etc.

hth.

意中人 2024-10-20 12:43:56

If/Else 语句不属于用例。

维护或系统管理功能通常被视为系统功能,除了用例模型之外,通常会在游戏后期出现。再加上许多维护功能的相似性,我发现它是一个很好的候选用例,其基本维护流程由一些处理特定需求的用例扩展。通过一些用例,我可以满足系统的整个维护/系统管理需求。 (不包括安全管理。)

If/Else statements don't belong in use cases.

Maintenance, or system management, functionality is generally considered system functionality and, other than on the use case model, usually shows up a little later in the game. Add to that the similarity of many of the maintenance functions and I've found it to be a good candidate for a use case with base maintenance flows extended by a few use cases that deal with specific needs. With a handful of use cases I can address a system's entire maintenance / system management needs. (Not counting security administration.)

归途 2024-10-20 12:43:56

如果您创建一个管理用例并将其他用例与其链接,则看起来所有用户都可以管理(创建、更新、删除)帐户。最好为每个用户创建单独的用例,并概括从一般用户继承的管理员和操作员等用户,并将相关用例链接到专门用户,例如删除帐户不会与操作员链接

If you create a single Manage Use Case and link others with it, it would look that the all users can manage (create, update, delete) accounts. It would be better to create separate uses cases for each and generalize users like admin and operator inherited from a general user and link related use cases to the specialized users e.g. delete account wont be linked with operator

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