Doubts on Depicting Use Case

[sc_kew]

I am having doubts on illustrating the use cases description. For instances, the system consists of different modules and each module is equip with a search function and reporting tool. The available search function and reporting tool in each module may contain different criteria or field names. In this case, should I define these two (2) use cases based on the individual modules or only describes the UC: Perform Search and UC: Run Report in one time, and later use <<inclusion>> relationship whenever there is applicable to other use cases.

If I define the use cases based on the individual modules, then all the description of use case in the respective modules will seem to be duplicated.

If I use the inclusion relationship, there will seem to be confusion among end-users and programmers because each search and reporting file containing different criteria and field name. Which method is preferred to use and why? If possible, please give me a sample of writing UC at the above mentioned.

Many Thanks!

Best wishes,
sc_kew

[angel-o-sphere]

The first thing IMHO to do is to write *all* UCs down with at least a name and a short description. Just fill up to 3 sentences into the note field for that.

As long as you have not fully understood/communicated the overall requirements it is jumping to conclusions to use <<extends>> and <<include>>.

As your included "Search" UC varies from include to include, it looks to me that an extends relation ould be the right one. However: if the extended UC is just a 3 step UC: enter search criteria, search, display result, it is not complex enough to be quallified worth of extending. (The extension point "enter search criteria" is likely no extension point at all).

So: is it the case that you just can trigger the "Search UC" from every module in your application? In that case you likely jsut have one "Search UC" and there are no <<include>> or other relations involved.

Note: UCs in general have no relations to each other.

Summary: if in doubt, write every use case down(include every UC on the diagramm) optimize later in the fourth fivth or even later iteration.

angel'o'sphere