Wednesday, July 29, 2009

"BPMN 2.0 – Marriage Made In Heaven or Trough of Disillusionment" or "Why Software development is like String theory" (BPMfocus)

"By modeling something, we are removing some aspect of the real world in order to represent it. And yet, the IT-oriented folks continue to flail about looking for one true modeling notation and set of semantics to rule them all (like string theory). As though how somehow everything must be translatable and interconnected. I think for most business folks – they don’t really care. They use models to communicate with each other … and yes, they use circles and arrows, and boxes and clouds, and … only a very few have the interest in making them all relate to each other. " "BPMN 2.0 – Marriage Made In Heaven or Trough of Disillusionment" (

I liked the above quote, reminds me of why we have IT in the first place - to support the business. We IT people are so caught up in trying to build perfectly clean, orthogonal and "one true implementation to rule them all" end to end solutions - and the business side just doesn't care about our "OCDs" :)


  1. Someone doesn't work with accountants, who like every artifact very tidy and exhaustively complete

  2. I think the previous comment missed the intention ... I was talking about the way in which all these modeling notations and semantics of process need to be translatable (at the software level).

    Accountants are used interpreting the figures presented to them, and a process model has plenty of fudge factor when it comes to human interpretation. Yet we in IT keep on beating ourselves up to make every element of "process" (whatever definitiion you choose), translatable into every other one.

  3. Which is worse - trough of disillusionment or the the pit of despair?