My friend Bob was troubled when I blogged "Object Only Programming is Silly". Bob knows from experience that life after OO is dramatically better than life was before OO... so my criticisms just don't sit well with him.
Fill in the blank in the following statement:
Most Software Development Obstacles are ______
If you answered (A), then I am intensely jealous :-)
When I became a programmer, my answer definitely would have been (A) and I probably wouldn't have had a clue why (B)
Tom Baeyens, of JBoss jBPM fame, published a great overview of BPM's past and possible future in his article: Process Component Models: The Next Generation In Workflow ? over at InfoQ.
Check it out!
Every so often I come across a blog entry that makes my own attempts to put my thoughts in writing seem pathetically inadequate.
NetBeans (6.1) Page Flows may be a small step towards Model Driven development: Read more here.
I've had a surprisingly difficult time conveying my own definition of "Iterative Development" in the context of BPM development. If you are interested in such things, please take a look at my other blog for an explanation via analogy....
Still don't quite understand what's different between "normal" programming and developing managed business processes?
Perhaps this blog on Task Routing in a Managed Process will help you to understand the issues that Business Process Developers have to deal with.