Use Case diagram of Withdrawal (UML diagrams)

Question

Can you check this diagram! If there is any mistake or suggestions, let me know please

https://www.sololearn.com/post/1747827/?ref=app

Answer 1

maybe you can draw several diagrams. One very simple, showing only high level process blocks. Then draw additional ones showing more detailed inner process within each block. This way, the diagram would avoid spaghetti arrows and information overload.

Answer 2

1. Don't ever draw these diagrams by hand. Even from your picture it is obvious that they are very problematic to fix or rearrange, I can see the corrector marks :)
My favorite approach is "diagram as code" but you could use just about any drawing tool, even powerpoint is better than pen and paper.

https://www.structurizr.com/

https://youtu.be/OKd0i08hcP0?si=JaStsHNOKQxaOgTA

2. UML is a very complex framework and each type of diagram serves a particular purpose. In a use case diagram, you only want to present really high level processes, and not show the details. For example, listing the possible currencies of the account is completely out of place, I think even showing the Account as a separate entity is too much. You only want to show the main activities the user can do, maybe the process of navigation.

https://www.lucidchart.com/pages/uml-use-case-diagram

Answer 3

Tibor Santa

Thanks for your help!

Yeah, it's difficult but my professor demanded a hand written assignment.