![]() ![]() ![]() |
![]() |
|
|
![]() ![]() ![]() ![]() ![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Return to Posters Due to business process automation development, process interconnection becomes an important matter. Actually, if a wide spectrum of business process management systems (BPMS) exist (e.g. workflows, shared agendas, project managers, to do lists, etc.), they have been mainly developed to suit the internal needs of enterprises. Moreover, if we focus particularly on workflow management systems (WFMS), existing interconnection solutions are mostly static, proprietary, and depend on specific business process definition languages, specific WFMS platforms, private data exchange formats, etc. ![]() DiSC'03 © 2003 Association for Computing Machinery |