Why BPMN
BPMN follows the tradition of flowcharting notations for readability
A Notation Evaluation of BPMN and UML Activity Diagrams (PDF)
Results from the Workflow patterns framework analysis in chapter six showed that
BPMN has a better representation power in control flow and data -patterns. While both
notations give equally weak results in resource patterns, the only real and meaningful
difference seems to be the lack of external interactions support in UML AD. In this light
the representation power of BPMN can be seen better than UML AD.
Results from the BWW-model analysis in chapter seven were not very considerable. In
many respects the BWW-model analyses against these two notations have very similar
results. Depending on the viewpoint, UML AD could be seen better in representation
power, but only little.
When recapturing this research, the differences between the representation power of
BPMN and UML AD are very narrow. On the whole, BPMN could be seen to have only
a little more representation power than UML AD, because of the better Workflow pattern
analysis results.
Thus, we could conclude, that if there should be a need to choose which notation to use,
the decision can not be done based on the representation power. It is better to base the
choice between the notations on other matters like existing experience on some tool and
notation or equal.
Originally posted by Jane Somerfield:
We have been using Activity Diagrams and Use Case Diagrams to the business people very successfully.
Why are you then worried about it? Use whatever works to communicate effectively - there is no "one right" notation. BPMN and BPD then only become an issue once you have a tool that forces you to use it - that tool probably provides its own context to justify the BPMN vs UML AD choice.
[ March 25, 2008: Message edited by: Peer Reynders ]