That's right.
UML state diagrams work for this purpose. I worked in large companies, where it was standard practice and with great success (even subject to strict rules and UML practices).
The key is to remember that it is you who want to communicate with your chart, and not try to model too many aspects in one chart. Also remember your audience. If you need to explain UML to them how UML works, then UML is not suitable for your situation.
I strongly disagree with those who consider this to be an βabuseβ of UML. Consider that state diagrams represent various system states and transitions between them caused by events. When you present the user interface navigation, you present the user interface forms as state and user actions, as well as user interface events as events that result in a change in the context of the system user interface instance presented to the user.
You may not agree with me, but please provide evidence or support for your arguments.
source share