three use cases into one use case

Question

I have one actor (admin), he can perform some actions over other user accounts such as creating the account, editing the account and deleting the account account. Should I do so

Answer 1

I think that in the diagram, the Admin actor should interact with the specialized (child) use cases rather than the more abstract (parent) use case.

Furthermore, it is a good practice to show the system boundary using a frame around all the use cases implemented by your system. This is especially helpful when you have more than one external actor.

This page is also helpful for understanding the concept of generalization.

Answer 2

Second one is a better option to adopt as far as clean code and modularity is concerned.

Answer 3

You can have the abstraction to Manage Accounts by having it generalize the three use cases.

Like so:

You can refer to the abstract use case where you need things to be in compact form, and refer to the much more precise "sub" use cases where you want to show details.