![]() That’s traditional, and it’s a pragmatic solution during, say, a transitional period that allows your co-workers to adapt. You can eliminate pools and work just with lanes, modeling the message exchange as normal tasks as shown before. What does that signify, however, for purely functional process modeling, in which you also describe processes not controlled by such a process engine? There’s no general answer to that question. Have you heard of service orchestration in connection with Service Oriented Architecture (SOA)? That’s almost exactly the task of a process engine, except that these services are not only fully automated web services they also can be tasks executed by human process participants as directed by the process engine. So the process engine equates to the mysterious, almighty process conductor. In that world, the process engine controls all tasks in the process, even though different task managers may execute them. Even though BPMN lanes look very much like those of other process notations, they represent an entirely different way of thinking, which we attribute to BPMN’s origin in the world of process automation. It reveals a basic principle, however, that you must understand. ![]() That seems complicated – and you don’t have to choose this method for practical modeling. ![]()
0 Comments
Leave a Reply. |