Etienne's picture

 Just a thought, as most of you will know, the BPMN model done for implementation (private processes) contain many more objects and detail and does not look the same as the BPMN model the business signed off. Now the question, do you maintain one model and potentially confuse the business or do you keep a logical design and a physical design with common objects where applicable?

In my opinion 2 models would be better and I’m playing with the idea that from your parent process object i.e. value chain object, the logical design would be represented by an assigned BPMN collaboration diagram (private & public) and the physical design would be represented by assigning a BPMN process diagram (private)? Common objects i.e. tasks would appear on both, but if the physical model is enhanced by including extra service objects, they won’t appear on the logical model. This way the logical & physical can be compared and what should be the same on the 2 diagrams should be the:

User tasks – representing consumer processes

Sub processes – representing long running processes

Transactions – representing short running processes

What can differ are automated activities (service or script tasks) that belong to a transaction (short running) or stand alone service or script tasks.

Hope this makes sense?

Tags: BPMN