While I was watching a tutorial on use case diagrams, I thought it easier for me to simply write in text what the process should be. Besides, that is the first step of creating a use case diagram.
UML is not meant to be a strict protocol. It's meant to be a tool that makes it easy to communicate ideas. If text ends up being the easiest way to do that in your case, then do that. Just be aware that some use cases end up having some common intersection points. How you will represent that in text maybe interesting.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.