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.
Belongs the notation to chose to the project charter?
Some days ago I visited a potential customer here in Germany. They already developed a good number of models and want to build a "real" enterprise architecture now. One content they already have are Business Rules. Very good - it is for sure a great idea to separate Business Rules and Business Process Models. They described the rules in natural language for the business users - but in English. I think this misses the point of using natural language for business rule representation. The argument was that English is more precise than German. It seems so at least. But any natural language leaves room for misunderstanding. And addressing business users in a foreign language misses the point.
RuleSpeak™ was developed by Ron Ross to allow business users to build and use their own Business Rules in natural language. Keywords and principles for building the rules should ensure precision. Sometimes you have to make compromises between precision and easy understanding for the business user.
RuleSpeak™ is available in multiple languages - e.g. Dutch. Spanish, Polish, Norwegian. The German version can be found on our company website or together with the other languages on www.rulespeak.com.