Developing a UML activity diagram for a search application

I have to create a UML activity diagrams for a searching application for a semantic database. Easy to guess, users can search and select a file, but they can also browse and refine the retrieved results by开发者_高级运维 clicking the categories the results belong to. They can even select a file just by browsing without actually entering any keyword. Should I create one single 'large' activity diagram showing the different possible workflows or a series of smaller ones, such as "perform a search", "browse the collection" or "select a file"?

I think, what you have mentioned is more likely to be a sequence diagram ("perform a search", "browse the collection" or "select a file"), and I would recommend you to have several sequence diagrams that you listed. My argument for this is: these diagrams are consumed by testers at design stage, so they can write tests for it.

And the major activities you can put into overall activity diagram, that will show the possibilities of what user can do at a given step/stage (if I can logged in, I can perform a search, browse the collection, etc).

Personally I would create a large UML providing an "over-view" of functions that are provided by your application. I would then create smaller more detailed UML diagrams so that the application's functions can be studied in detail.

Hope that helps with your decision.

Regards, Mike.

Edit: I find Microsoft Visio particularly useful in which to create the UML diagrams too.