How can I create a correct use case diagram with inheritance?

Question

I'm on creating use case diagram that contains two actors: Admin and Super admin. The admin can do all the tasks as the super admin except the delete. The use case in the picture below is it right :

the digram is on french:

**gérer  les utilisateurs** = manage users
**modifier un utilisateur**= edit user
**consulter un utilisateur**= view user
**rechercher un utilisateur**= search user
**ajouter un utilisateur**= add user
**supprimer un utilisateur** = delete user

Answer 1

The «extend» approach is not suitable because it requires the use-case Manage users to add value on its own without any of the extensions. You‘ll find more arguments in this other answer. The right way to address this issue — if this level of detail is really desired — is to use generalisation on the use case side as well.

If you would just have the CRUD cases inheriting from the more general Manage users, an Administrator could, by way of use case specialisation, also realize the more sensitive Delete user. There are several ways to address this:

• keep the general use case without actors. Associate the normal user to the three specializations and the admin to the deletion only.
  Online example with plantuml:
• keep only the association of the normal user to the general use case, and use a constraint on the deletion use case, to make clear that it requires the user to be superuser (this would be my preferred one, as it would allow also to get rid of the (too?) detailed uc):
  Example:
• more variants using intermediate elements of generalisation.