Last year, after reading a book about UML, I wrote a set of posts with distilled UML guidelines. Now it is the time to look at them again and put some comments on usage.
I tend to create vertical activity diagrams, so I usually place the start on top and in center. This way looks more visual.
What? No ending point? So activity never ends? I always have at least one ending point
The whole goal of activity diagrams is to visualize and, if possibly, simplify the process.
I would question any activities. It is very usual to have some unneccesary work only because analyst and/or client do not fully understand what is needed and what is achievable
If there is no guard then what this flow is trying to decide?
And if they not - why do you have decision point, by the way?
This one support the thesis about having the complete set of the guards next to each decision point.
If you don't have real guards - you should not have the decision point in this place
Not always true - some of the forked processes may be terminated before they go to the join. Messaging is a good example.
It is all about logic, why say more?
I would say that is you trying to add fourth swimlane, you are already creating something bigger, than anybody in your team can comprehend without asking you more questions. It is time to simplify the activity.
Consider to use UML2 and include sub-activities in this activity
Yes, very good point.
Well, it depends on business process and your preference.
Good point. If you don't have key activities in the primary swimlane chances are that you modeling incorrect activity.
And use color, if your modelling program allows it.