Use-case diagrams shall not show any sequence. Return a book is followed by a confirmation email. Sometimes your diagram seems to be a sequence of action: e.g. Course: Digital Logic and Design (CSE1003) 92 Documents. This is not forbidden but strongly discouraged as it leads to too detailed and complex diagrams. University: Vellore Institute of Technology.

more variants using intermediate elements of generalisation. 1 Passport Automation System srs, use case diagram, uml diagrams, class diagrams.

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):.

Associate the normal user to the three specializations and the admin to the deletion only. A use case diagram shows various use cases and different types.

The time to use the < relationship is after you have completed the first cut description of all your main Use Cases. The actor can be a human or other external system. A use case diagram is a graphical depiction of a users possible interactions with a system. The < use case accomplishes this by conceptually inserting additional action sequences into the base use-case sequence.

keep the general use case without actors. A use case diagram contains four main components Actor Actors are usually individuals involved with the system defined according to their roles.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. It is generally shown as a graphic depiction of interactions among different elements in a system. 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. A use case diagram is a way to summarize details of a system and the users within that system. You‘ll find more arguments in this other answer.

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.

Use case diagrams