Tuesday, May 21, 2002 09:00 AM
Think of a use case as a little "story", and keep thinking from the perspective of the person, who is actually trying to use your stuff to accomplish something (a "meaningful result" in the UML references).
Once upon a time, in a galaxy far away, there was a person who sat down to use your system. Here's what they wanted to do, and here's what happened.
For the different kinds of things they want to do, there are different little stories, and these become different use cases.
When someone sits down at your system, do they first decide, hmm today do I want to do some "customer management" or "warehouse management" or maybe do I want to do some "orders management" instead?
If so, then yes you could start with those three at the top in your first diagrams.
But, does someone ever need to accomplish something which involves more than one of those, in the same session?
Maybe they need to track an order, for a customer, involving warehouse status, all together?
... and so on ...