How to Show a Big Use-Case Diagram – Best Practices
umluse-case
I have the big use-case diagram:
May I pack some use-cases in packages and then show diagram by the following way:
Best Answer
I think you're missing the point of use case diagrams. They aren't to say, here's an actor, here's a use case. Your diagrams should be taking me through the story of a use case. That story should be more than just one oval. Whether you should be bundling multiple use cases together in one diagram has more to do with how complex the use cases are and if they fit on one page.
If you're just looking for a way to abstract similar use cases together because the rest of their story is identical then sure. Use whatever grouping picture you like. Just be consistent.
If you wish to show a multitude of something without giving each one a different label the stack has always been my choice. It's easy to do on the whiteboard as well.
With this you can start to ask, is the package box still needed? Could each oval simply be labeled "basic use case" and "additional use case"? If the oval is known to be a use case can you just use "basic" and "additional"?
I'd say your include arrows are the wrong way round, it's a little odd that Validate membership isn't included in extend return date? and I'd also be tempted to split these into two or three separate diagrams (so we don't have crossing lines).
However, I'd also say that take 'correct uml' with a pinch of salt, if the diagram is useful to you, and to what you want to communicate, then it is doing its job already.
The most important is that it is clear from the use case description that a choice must be made between the search and the browse functionality.
In your diagram, the 'add to basket' use case should <<include>> both the 'search products' and 'browse products' use cases (assuming that the choice for searching or browsing is made from the 'add to basket' use case). If you really want to show that those included use cases are mutually exclusive, you can add a UML constraint { mutually exclusive } linked to the inclusion arrows, but that is completely optional.
Best Answer
I think you're missing the point of use case diagrams. They aren't to say, here's an actor, here's a use case. Your diagrams should be taking me through the story of a use case. That story should be more than just one oval. Whether you should be bundling multiple use cases together in one diagram has more to do with how complex the use cases are and if they fit on one page.
If you're just looking for a way to abstract similar use cases together because the rest of their story is identical then sure. Use whatever grouping picture you like. Just be consistent.
If you wish to show a multitude of something without giving each one a different label the stack has always been my choice. It's easy to do on the whiteboard as well.
With this you can start to ask, is the package box still needed? Could each oval simply be labeled "basic use case" and "additional use case"? If the oval is known to be a use case can you just use "basic" and "additional"?