每个用例操作都必须包含登录名吗? [英] does every use case action have to include a login?

问题描述

我对用例图的概念很陌生，有点困惑，我有一个用例图每月报告存档"，我想问一下是否使用<<包括>> 一个案例必须通过登录?以及我制作的用例是否正确?

I am very new to the concept of use case diagrams and I am a little confused, I have a use case diagram "Monthly Report Archiving" and I want to ask if the use of << include >> of a case must pass login? and Is the use case that I made correct?

所以就我而言，现在是关于每月报告存档".这流程是:公关收到社区的提案，然后提案数据将由社区关系存储到系统稍后由 X 部门查看并商定是否提案将被接受或拒绝.X师然后可以看到有关提案的信息，然后部门 X 可以选择是否该提案将被接受或拒绝，如果被接受，该提案将被存档.然后，X 部门从提交给经理的存档提案.每个月经理可以查看 X 部门的报告.

so in my case right now it's about "Monthly Report Archiving". The flow is: public relations receives a proposal from the community, then the proposal data will be stored by the community relations into the system to be later seen by Division X and agreed upon whether the proposal will be accepted or rejected. Division X can then see information about the proposal and then division X can choose whether the proposal will be accepted or rejected, if accepted, the proposal will be archived. Division X then makes a monthly report from the archived proposal to be given to the manager. Every month managers can see reports that have been made by division X.

这张图片1

并且此图像 2 每个案例都必须包括登录.

and this image 2 every case must include login.

那么哪个更好?图一还是图二?

So which one is better? Picture 1 or picture 2?

推荐答案

Login 不是用例，因为它没有任何附加值.这只是一个简单的约束.您可以将其附加在阅读 { ;必须登录 } 并构造它<>.或者将其附加到参与者并对其进行描述 { 任何用例都必须登录 }.

Login is no use case since it does not have any added value. This is just a simple constraint. You could attach it in a note reading { <actor> must be logged on } and stereotype it <<invariant>>. Or attach it to the actor and describe it { must be logged on for any use case }.

顺便说一句:不要尝试任何功能分解.用例显示了系统为其参与者带来的附加价值.没有别的，请.另外，使用 ; 描述单个用例.

And by the way: don't try any functional decomposition. Use cases show the added value a system brings to its actors. Nothing else, please. Also, use <verb> <substantive> to describe a single use case.

根据经验:如果您的 UC 图表开始类似于蜘蛛网，则您的设计已损坏.

As a rule of thumb: if your UC diagrams start resembling a spider's web, your design is broken.

这篇关于每个用例操作都必须包含登录名吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！