May be only for business process (which you could define in use cases and may be collaboration diagrams), but when you start designing your solution, you'll find that class diagrams and stuff are not useful. Mainly because UML focuses on OO languages ... C/AL is not OO at all.
I was trying to draw several UML cases, and Sequence diagrams with Rational Rose Modeler, but... it's much more harder to describe how NAV works in UML, then in simple real life words
Exactly - sometime I create some small diagram for me to make the thoughts clear for myself. We are doing some diagrams of the processes for the customers too to describe the processes, but mainly when doing the ISO 900x implementation...
Comments
May be only for business process (which you could define in use cases and may be collaboration diagrams), but when you start designing your solution, you'll find that class diagrams and stuff are not useful. Mainly because UML focuses on OO languages ... C/AL is not OO at all.
This is only my opinion ...
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
It's also only for me, because my customer (or my boss) doesn't understand it.
I was trying to draw several UML cases, and Sequence diagrams with Rational Rose Modeler, but... it's much more harder to describe how NAV works in UML, then in simple real life words
Dynamics NAV Enthusiast
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.