Include or extend use of business?

Question

I can’t understand what kind of relationship I should use in my use case. Let's say an actor is a User who can manage an account: -Create; -Remove; -Update;

Any ideas on whether I should use the Manage Account as a use case, and then create, delete, update it - if so - expand or enable relationships? Or would it be better if I left Create, Delete, Update as separate use cases?

Answer 1

I am not a fan of using Manage-X. As your post suggests, "Management" is a truly collective term for a number of alternative independent tasks. The result is a Use Case body that doesn't look right:

If the User selects 'Create' then {...}
else if the User selects 'Update' then {...}

... etc..

It is better to show them individually. If your model is getting big - and you need a way to organize it - then create a package for the corresponding UC, not a “super UC”. So in your case a package with a name Manage Accountcontaining UCs Open Account, Update Accountetc.

NTN.

Answer 2

If / Else statements are not owned in use cases.

, , , , , . , , , , . . ( .)

Answer 3

If you create one management use and associate others with it, it would be obvious that all users can manage (create, update, delete) accounts. It would be better to create separate use cases for each and summarize users, such as admin and operator, inherited from common user cases and links associated with specific users, for example. delete account will not be associated with the operator