TY - JOUR
T1 - A reference model for team-enabled workflow management systems
AU - Van der Aalst, W. M.P.
AU - Kumar, A.
N1 - Copyright:
Copyright 2007 Elsevier B.V., All rights reserved.
PY - 2001/9
Y1 - 2001/9
N2 - Today's workflow systems assume that each work item is executed by a single worker. From the viewpoint of the system, a worker with the proper qualifications selects a work item, executes the associated work, and reports the result. There is usually no support for teams, i.e., groups of people collaborating by jointly executing work items (e.g., the program committee of a conference, the management team of a company, a working group, and the board of directors). In this paper, we propose the addition of a team concept to today's workflow management systems. Clearly, this involves a marriage of workflow and groupware technology. To shed light on the introduction of teams, we extend the traditional organizational meta model with teams and propose a team-enabled workflow reference model. For this reference model and to express constraints with respect to the distribution of work to teams, we use object constraint language (OCL).
AB - Today's workflow systems assume that each work item is executed by a single worker. From the viewpoint of the system, a worker with the proper qualifications selects a work item, executes the associated work, and reports the result. There is usually no support for teams, i.e., groups of people collaborating by jointly executing work items (e.g., the program committee of a conference, the management team of a company, a working group, and the board of directors). In this paper, we propose the addition of a team concept to today's workflow management systems. Clearly, this involves a marriage of workflow and groupware technology. To shed light on the introduction of teams, we extend the traditional organizational meta model with teams and propose a team-enabled workflow reference model. For this reference model and to express constraints with respect to the distribution of work to teams, we use object constraint language (OCL).
UR - http://www.scopus.com/inward/record.url?scp=0035444738&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=0035444738&partnerID=8YFLogxK
U2 - 10.1016/S0169-023X(01)00034-9
DO - 10.1016/S0169-023X(01)00034-9
M3 - Article
AN - SCOPUS:0035444738
SN - 0169-023X
VL - 38
SP - 335
EP - 363
JO - Data and Knowledge Engineering
JF - Data and Knowledge Engineering
IS - 3
ER -