Abstract

Enterprises are lining up into virtual enterprises to meet the ever-increasing customer's demands in a more flexible and effective way than before. Hence, the business processes as well as supporting workflow systems need to be tightly embedded into streamlined, virtual value chains that can transcend organizational boundaries.

It is generally recognized that the combination of workflow with business-object component technology provides the required solution. However, today's widespread business workflow modeling techniques suffer from an object bias, ignoring the most essential coordination vehicle in the enterprise: communication, and the resulting commitments. In this paper, we present contracts that encapsulate (formal) commitments laid down as a set of obligations to coordinate and control the interaction between business workflows. We use the business contract specification language XLBC to formally link the Component Definition Language (CDL) specification of business object-based workflow systems. XLBC is an extension of the Formal Language for Business Communication (FLBC) and a framework for the semantics of XLBC transactions is described. Finally, we indicate a feasible implementation architecture on the basis of an emerging internet-enabled business process architecture, ebXML and Trading Partner Agreements (TPAs).

Author Keywords: Workflow integration; Contracts; Deontic logic; FLBC; TPA; ebXML

Article Outline

1. Introduction

2. Running case: integration of a semiconductor supplier and a PC-assembler

3. The integrated enterprise architecture

3.1. Business objects

3.2. Business tasks

3.3. Business workflows

4. Contracts: the glue to link inter-organizational workflows

4.1. The contract specification language: the Formal Language for Business Communication

4.2. Workflow control and execution

4.2.1. Security aspects for contract objects

4.3. The CDL/XLBC metamodel

4.4. The contract specification

5. Semantics

6. Implementation aspects

7. Summary and future research

Acknowledgements

Appendix A. XML fragment of contract definition

References

Vitae