No Ambiguity, Only Surprises

  • April 1, 2013
  • Scott
  • 0 Comments

There are some interesting observations I had coming out of bpmNEXT that didn’t fit neatly into the summary blog post.

During ITP Commerce’s presentation at bpmNEXT, they talked at some length about the notion of style in BPMN, and a key issue being vagueness – the hardest to determine.  When you’re modeling for business-user understanding, there’s often a fair amount of vagueness in the model – of ambiguity.  And that’s not entirely bad- because it simplifies the explanation of the model.

But it occurred to me – when you’re modeling for execution, there’s no ambiguity, only surprises!

Because at execution time, a BPMN engine will always resolve in a deterministic way – the model isn’t “ambiguous” to the execution engine, it is specific.  So what’s left?  Surprises – the difference between what the execution model does, and what the modeler thought it would do.

So if you’re modeling BPMN for execution – keep that in mind.  There’s no ambiguity when you’re done – but if you aren’t careful, there may be surprises!

 

Related Posts
  • November 15, 2017
  • Ariana
  • 0 Comments

When to Use Decision Management from BP3 on Vimeo. When do you use Decision Management What problems are ...

  • November 13, 2017
  • Scott
  • 0 Comments

MWD's insight newsletter is a good one to be reading.  I have subscribed to MWD's research over the years and...

  • November 12, 2017
  • Scott
  • 0 Comments

Phil Gilbert recently spoke at Web Summit. Phil runs Design for IBM.  And he used the opportunity to talk abo...