Lets say a report will be displayed when an user requests for it. Now an user could be agent or sales leadership or someone within the business. Do i need to create seperate use case for all of them? or just one in this kind of incident??
Thank you for your feedback.
M. Islam:
You bring up a very important issue. The underlying question here is: How do I partition my analysis effort? Partitioning (i.e., determining the extent of pieces of the whole) literally defines analysis, yet, it very seldom reaches the concious mind of a BA.
With use cases, the analyst just says la,la,la,la, repeatedly until the whole issue goes away from his/her mind. This BA then performs what is know as a forced, artificial partitioning. This is more commonly referred to as "sledge hammer" partioning or partitioning "by feeling".
With data flow diagramming the issue of proper partitioning is address in an engineering fashion. The BA first create a rough-cut DFD and then examines the data interfaces between the pieces of the puzzle and then breaks up the initial processes or combines them in a logical, natural way.
The choice is yours: Breakup with a sledge hammer / combine via feeling , or, use data flow diagrams to partition based upon data flow interface analysis. There really are no alternative.
Tony
I suppose you could have a separate use case for each report. Don't need a use case for each actor. In reality the actor is just a general user like "report user" or "general user" or something stupid like that
I never create use cases for each report as the interaction for any report is pretty much the same. So its a waste of time. I just list the reports that are needed somewhere with basic information about each one.
Kimbo
Hi Kimbo, I have read several places exclude and include are part of use case dependency. some other places they are all seperate sections. Can anyone give me a clear answer if they are same or they are different ? an example would be much appreciated. Thanks.
Do you mean <<include>> and <<extend>> ?
brought to you by enabling practitioners & organizations to achieve their goals using: