CODEWITHSUNDEEP
umluse-caseuse-case-diagram
Udo Gniß
Udo Gniß

Reputation: 63

include or extend in uml use case diagram

The purpose of the application is a displaying a dashboard. I have several actions/use cases like:

My question is which connection exists to the several Dasboards or should it be like one use case ‘show dashboards’ ?

Include or Extend?

enter image description here

Upvotes: 1

Views: 3811

Answers (2)

Christophe
Christophe

Reputation: 73376

For User, I see the following use-case:

  • Get an overview of the situation

That's all: the dashboards and filtering are only means that you propose to address the ends. The login is not a use-case either: it's also a mean to address the constraints that only authorised users can access the information. Single sign on (SSO) or facial identification could be alternatives.

Use-cases are not meant to design user interface. There are much better techniques for that. Use-cases are not features either. User-stories are very suitable for describing features (e.g. "As a user I want to filter data in the dashboard for the purpose of finding more specific insights"). You'd have dozens, if not hundreds of user-stories, but only a few use-cases since these are meant to show the big picture.

If you want to model something action oriented (show this, filter that, ...) or some sequence (first login, then move to dahsboard 01, then ....) you could consider an activity diagram.

Upvotes: 3

Ister
Ister

Reputation: 6318

Neither. You're not mentioning use case nor use case dependency but what seems to be systems dependency.

Depending on what you want to depict either each of the sites is considered a separate system or all those sites are just modules of one system.

In the former case if you are trying to show use cases of A, whatever use case requires pages B, C or D they will have to reach out to separate system, that is B. Since it is a separate system it will be an Actor for A linked to respective use case(s)

In the latter case, the use case offered to the user doesn't present internal implementation. It doesn't matter how many internal modules it has to use, it is always just a single use case.

Now, if you are trying to show that dependency in a more precise manner, it should not happen on the Use Case diagram. Instead the recommended option is usually Sequence Diagram with few other alternatives available (Communication Diagram and Activity Diagram being the most often occurring supplements).

Upvotes: 1

Related Questions