CODEWITHSUNDEEP
umluse-caseuse-case-diagram
Daniel H
Daniel H

Reputation: 21

UML Use Case - Do I use it right?

I am to create a UseCase diagram for an existing web program. Unfortunately I am very unsure about UseCase, I like to mix it with other UMLs.

For this purpose, I have picked out the order page.

There are 3 different users, the admin, driver and customer.

The admin can view all orders and has the ability to create a new order. The driver can see his own orders, as well as orders he can accept. The customer can see his own orders, as well as place a new order.

There is a possibility to choose between the standard view (row view) and a widget view of the meta information of the order.

Last but not least, there is the possibility to click on one of the orders and a single order overview will open.

Based on this I have now created a UseCase diagram, my first question would be: Is this all correct, with the informations i gave?

UseCase-Example-Picture

Will this then become a huge UseCase diagram? Or should this rather be done page by page for web applications? For example, if this is the order overview and I now have the use case that I change the page (In this case, when I go to the single order overview). And is there a way to make this look cleaner? All these extends/includes on 1 place looks confusing.

I'm afraid I don't know if I'm doing this only partially right, or completely missing the point.

Upvotes: 1

Views: 486

Answers (1)

qwerty_so
qwerty_so

Reputation: 36333

What you need to remember is that Use Cases are about added value and not about technical realization. That's really hard for tech people and that's why they always start functional decomposition. So looking at the above, the only use case is Show Order and nothing else.

Login is no use case from that perspective. It is just a constraint you apply to certain use cases.

You just have focused on the Show aspect but likely there's also add/edit/delete. Such CRUD can be dealed with in variuous ways and there's no general rule. There might be a Manage and a Show or what ever combination along with constraints.

Basically, when your UC diagram resembles a spider web your design is likely broken.

Upvotes: 1

Related Questions