参与者和用例之间关系的 UML 用例图问题
我已经为论坛系统创建了下图，但我不确定用例和参与者之间的关系是否正确。
所以我想知道我的图表是否正确，或者我是否在图表中添加了太多复杂性。我是否正确地了解了用例与参与者的关系？更好地说，它到底正确吗？
非常感谢任何帮助。
i've been created the following diagram for forums system but i'm not sure if the relation between use cases and actors is correct.
so i want to know if my diagram is correct or if i've added too much complexity to my diagram. did i got my use cases relation with the actors correctly? well to better say, is it correct at all?
any help is really appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
对于第一次尝试来说，这还算不错，但我想说它有点过于复杂。当您使用用例或其他方法进行分析时，您确实希望保持简单并避免进入设计模式，此时您开始考虑事物之间的关系。
在我看来，你的演员不应该一概而论。论坛上的“发帖者”并不是一种更具体的“阅读帖子的人”：它们是同一个人在不同时间可能扮演的不同角色，而不是彼此的扩展。所以我建议你放弃这些概括。
用例本身也是如此。通常，用例通过
<> 或<> 关系相互关联，但是否泛化通常使用。用例与类不同，并且实际上没有抽象的选择，因此“管理”用例本身需要有意义，但它们实际上并没有这样做。另一方面，您的“具体”用例非常有意义。为了将相关用例分组在一起，最好使用单独的图表和/或将用例收集到称为“后期管理”、“站点管理”等的包中。没有什么说你必须将所有将用例合并到单个图表中。
Not a bad effort for a first attempt, but I'd say it is a bit over complex. When you do analysis, using use cases or some other method, you really do want to keep it simple and avoid going into design mode, which is when you start thinking about relationships between things.
In my opinion, your actors should not be generalizations of one another. A "person who posts" on a forum is not a a more specific type of a "person who reads posts": they are different roles which the same person might take on at different times, not expansions on one another. So I'd advise you to drop those generalizations.
The same goes for the use cases themselves. Normally, use cases relate to one another by way of either the
<<extend>>or<<include>>relationship, but generalizations or not normally used. Use cases aren't like classes and don't really have the option of being abstract, so the "manage" use cases need to make sense on their own, and they don't really do that. Your "concrete" use cases, on the other hand, make perfect sense.In order to group related use cases together, it's a better idea to use separate diagrams and / or gather the use cases into packages called "post management", "site administration", etc. There is nothing which says you have to put all your use cases into a single diagram.
我支持你的用例图方法。不久前我曾为这个问题苦苦挣扎。向每个参与者展示一个用例的每个关联会变得很混乱。通过概括参与者，它将关联整合为一种美观、易于阅读的格式。因此，其他人更容易使用该信息。
I support your method of use case diagrams. I struggled with this very issue a while back. To show each association from one use case to each of the actors was getting messy. By generalizing the actors, it consolidated the associations into a nice, easily readable format. Thus, the information is easier for others to consume.