| Abstract [eng] |
To define long-running, service-oriented business process fully and correctly, it is necessary to specify following properties: data flows, business partners along with their actions, and state dynamics of entire process. Also, it is required to define mechanics which can be used to compensate failed long-running transactions. This can be achieved by combining SAGA and Communicative Action Loop models. To gain robustness, it was suggested to use two types of strictly formatted diagrams. A formal metamodel was proposed as a basis for a graphical editor which can be used to define a service-oriented business process and its properties. Finally, a prototype of graphical editor was developed and used to specify example business processes. |
