问题
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?
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.
this image 1
and this image 2 every case must include login.
So which one is better? Picture 1 or picture 2?
回答1:
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.
As a rule of thumb: if your UC diagrams start resembling a spider's web, your design is broken.
来源：https://stackoverflow.com/questions/53907281/does-every-use-case-action-have-to-include-a-login