根据用例<<查看报告>>，我们可以说图表是正确的吗? [英] According to the Use case <<view reports>>, can we say that the diagram is correct?

问题描述

在我的项目中，用户(管理员和教育专家)能够查看动态报告.这些报告是在报告文件管理器中创建的.

In my project, users (admins and education expert) are able to see dynamic reports. These reports are created in the Report File Manager.

现在，要制定一个用例查看报告，下图是否正确?

Now, to draw up a use case view reports, Is the following diagram correct?

需要注意的是，管理员可以查看所有报告，教育专家可以查看自己的报告.这会改变用例图吗?

It should be noted that the admin are able to view all the reports and the education expert is able to view his self report. Will this change use case diagram?

//////根据答案，我画了一个新图.

//////According to the answers,I've drawn a new diagram.

推荐答案

我注意到的第一件事是你从未在任何地方见过的奇怪的演员符号.演员表现为简单的火柴人.

The first thing I notice is your strange actor notation which I never have seen anywhere. An actor is shown as simple stickman.

您需要添加一个限制条件来说明管理员可以查看所有报告.这可能只是一个大括号中的文本注释，例如 { admin can view all reports} 附加到演员和 UC 之间的关联.

You will need to add a constraint to describe that the admin can view all reports. This could simply be a textual note in curly brackets like { admin can view all reports} attached to the association between actor and UC.

除此之外，考虑将所有这些单一的 CRUD 用例合并到一个Manage Report 中，因为我猜所有这些都是紧密相连的.否则你很可能会被功能分解综合症所震惊.

Besides that, think about collapsing all these single CRUD use cases into a single Manage Report since I guess that all are strongly connected. Else you're likely to be struck by the functional-descomposition-syndrome.

这篇关于根据用例<<查看报告>>，我们可以说图表是正确的吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！