I'm make a use case for a user authentication for a website, and when the user register a new account the website send a verification email to the user.

Is this use case correct? If not, how can I improve it?

This is the use case I made:

CodePudding user response：

In short, the diagram is correct, but it is also true that it depends on the level of detail you want to go into with the UML diagram. Generally, in the case of login or registration, we tend to represent more in detail. For example credential check, password recovery and other events.

CodePudding user response：

This diagram is syntactically wrong: the dashed lines should be arrows which are either «includes» or «extends» to explain the dependencies between use cases.

Semantically the diagram could be correct (depending on how you decide for the dependencies) with the following remarks:

• The actor service would be an external autonomous system and not an internal verification service.
• The use cases are independent and have no order between them. Hence, it could be possible to login and then register.
• Moreover, breaking a functionality (e.g. registration) in smaller ones (e.g. send email) is called "functional decomposition". Although it is not wrong, it is not recommended, as it leads to overly complex diagrams.

Last but not least, we still don't know what the goals of the system's user are. Use case should focus on actor goals. Login is not a goal, but only a necessary step to do something more meaningful.