The MENTOR workbench for enterprise-wide workflow management

  • Authors:
  • Dirk Wodtke;Jeanine Weissenfels;Gerhard Weikum;Angelika Kotz Dittrich;Peter Muth

  • Affiliations:
  • University of the Saarland, Department of Computer Science P.O.Box 151150, D-66041 Saarbrücken, Germany;University of the Saarland, Department of Computer Science P.O.Box 151150, D-66041 Saarbrücken, Germany;University of the Saarland, Department of Computer Science P.O.Box 151150, D-66041 Saarbrücken, Germany;Union Bank of Switzerland, P.O.Box 2336, CH-8033 Zurich, Switzerland;University of the Saarland, Department of Computer Science P.O.Box 151150, D-66041 Saarbrücken, Germany

  • Venue:
  • SIGMOD '97 Proceedings of the 1997 ACM SIGMOD international conference on Management of data
  • Year:
  • 1997

Quantified Score

Hi-index 0.00

Visualization

Abstract

MENTOR (“Middleware for Enterprise-Wide Workflow Management”) is a joint project of the University of the Saarland, the Union Bank of Switzerland, and ETH Zurich [1, 2, 3]. The focus of the project is on enterprise-wide workflow management. Workflows in this category may span multiple organizational units each unit having its own workflow server, involve a variety of heterogeneous information systems, and require many thousands of clients to interact with the workflow management system (WFMS). The project aims to develop a scalable and highly available environment for the execution and monitoring of workflows, seamlessly integrated with a specification and verification environment.For the specification of workflows, MENTOR utilizes the formalism of state and activity charts. The mathematical rigor of the specification method establishes a basis for both correctness reasoning and for partitioning of a large workflow into a number of subworkflows according to the organizational responsibilities of the enterprise. For the distributed execution of the partitioned workflow specification, MENTOR relies mostly on standard middleware components and adds own components only where the standard components fall short of functionality or scalability. In particular, the run-time environment is based on a TP monitor and a CORBA implementation.