CODEWITHSUNDEEP
umluse-caseuse-case-diagram
Joseph Joester JoJo
Joseph Joester JoJo

Reputation: 41

Usecase diagram for catalog, category and product management

So each menu has different categories and each category has products. I'm a bit confused of what usecase I should use.

option 1

option 3

option 3

Upvotes: 1

Views: 173

Answers (1)

Christophe
Christophe

Reputation: 73446

Use cases are not meant to be used for designing user interfaces and menus. For this purpose, it is better to use more appropriate design practices such as for example wireframe and storyboards.

Use cases are not either meant to present a workflow or a sequence or event, like first do that, then chose then, then that. For this activity diagrams are better options.

Use cases should represent actor goals. The last option seems in this regard acceptable, since a user may be interested to manage each of these items, independently of the user interface and the order it is done.

The second option corresponds to the narrative. But it corresponds to a functional decomposition. Moreover it is misleading, as it suggest that managing products is dependent on the others, whereas one could well imagine an independent management of products.

The first option would be an alternative if the main goal of the actor is to manage products, and navigation through menus and categories would just be means to manage the products. Looking at the context (especially the "reservation" use-case) I understand however, that it's for a restaurant management system, and managing product is only one part of the goals. This option would therefore be misleading.

Upvotes: 1

Related Questions