umluse-caseuse-case-diagram

Use-case diagram: When to decompose use-case and when not to?


For an example, say, I want to draw a use-case diagram for an artificial vending machine like so:

I tried this but not really sure of it, don't know what to keep, what to add or what to remove..

The questions are:


Solution

  • Use cases are about the what and not about the how. The latter goes into Activity and is split to Actions. Use case only show the added value a system under consideration brings to its actors.

    So the only added value is Sell drinkand that's it.

    I recommend reading Bittner/Spence about use cases. They call it synthesis and that's the right word. Not analysis and even less decomposition.

    Strange, that techies always want to decompose things. Well, I know it's hard to learn since I had been scratching my head too. It's probably so complicated because its about simplicity.