2005
DOI: 10.1007/11538394_19
|View full text |Cite
|
Sign up to set email alerts
|

A Framework for Document-Driven Workflow Systems

Abstract: Abstract. We propose and demonstrate the feasibility of a framework for document-driven workflow systems that requires no explicit control flow and the execution of the process is driven by input documents. The framework can assist workflow designers to discover the data dependencies between tasks in a process and achieve more efficient control flow design. The framework also provides an architecture to separate the workflow system from application data and facilitate inter-organizational processes. Document-d… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
41
0

Year Published

2008
2008
2020
2020

Publication Types

Select...
8
1
1

Relationship

1
9

Authors

Journals

citations
Cited by 75 publications
(43 citation statements)
references
References 11 publications
0
41
0
Order By: Relevance
“…The process steps follow from the availability of data objects, as production rules indicate how to produce new objects from existing objects or which operations are available based on the current data. The approaches that reside on this level are case handling [1], PBWS [24], and document-driven workflows [26].…”
Section: Data Integrationmentioning
confidence: 99%
“…The process steps follow from the availability of data objects, as production rules indicate how to produce new objects from existing objects or which operations are available based on the current data. The approaches that reside on this level are case handling [1], PBWS [24], and document-driven workflows [26].…”
Section: Data Integrationmentioning
confidence: 99%
“…Purely data-based approaches such as active database systems [20] allow to update data based on event-condition-action rules, but lack a genuine process perspective. Many approaches combine activity-centric process models with object life cycles, but are largely confined to 1:1 relationships between a process instance and the object instances it can handle, e.g., [9,13,22] and also BPMN [16]; some of these techniques allow flexible process execution [19]. Table 11 compares techniques that support at least a basic notion of data integration.…”
Section: Related Workmentioning
confidence: 99%
“…Detailed discussion of an algorithm to determine suitable boundaries is beyond the scope of this chapter. Further discussion of data dependencies appears in [28,30]. In summary, the general procedure for creating and running resource-driven workflows is as follows:…”
Section: Data Dependenciesmentioning
confidence: 99%