We are talking of Model-Based Business Engineerin. Models are base for many working techniques as described in the White Paper "Model-Based Business Engineering - A Positioning". Based on models we define, measure, optimize Business Processes, for development of workflow-based systems and much more. One of my favorite quotes by John Zachman is "If you can't describe it, you can't uild it".
We use different Standard Notations by the OMG for Model Development. They offer a good number of benfits: exchangeability, defined meaning of model elements, tool support, ... Sure, all notations also have shortcomings. But discussing endless abou the shortcomings is boring. Notations are a mean to an end. They are a tool. It is very important, what our goal, our end for our models is.The mean (the notation) will be determined by this.
In one of my customer projects I found a Project Charter saying that the goal of the project is to introduce BPMN 2. I don't think that this is a real goal. We want to minimise risk, improve processes, alow measuring processes and much more. To find out if BPMN supports this should be part o the project.