Hi K,
I have a clear picture now
Thank you
here are 2 useful articles on the strengths and weaknesses of use cases. They each have different views.
Craig:
I say that both authors fail to mention the primary weakness of use cases: They are functional modeling based on a forced, artificial partitioning. (They both kind of hint around at this issue in saying that, with use cases, the question "How do we know when we are done?" arises, but thats it.)
Tony
I agree, using Use Cases in isolation does raise the "how do I know I have all of them" question. I start with a business process or workflow, and each one of those will have steps that say things like Create CustomerIn System; that's your Use Case. You have one for each of these kinds of steps, and when you reach the end of the process definition, you have all the use cases.
brought to you by enabling practitioners & organizations to achieve their goals using: