Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Last revision Both sides next revision
blogs:pub2008:constraint-based_workflow_management_systems_shifting_control_to_users [2009/05/28 07:01]
127.0.0.1 external edit
blogs:pub2008:constraint-based_workflow_management_systems_shifting_control_to_users [2017/11/30 16:31]
hverbeek
Line 8: Line 8:
 ===== Abstract ===== ===== Abstract =====
  
-//todo.. (plus upload PDFsee link below)//+Many organizations use information technology to support various aspects of 
 +their business processes: the operational aspect, collaboration between employees, 
 +etc. Workflow management systems aim at //supporting// the operational aspect 
 +of complex business processes by using process models to automate the ordering 
 +of activities (i.e., flow of work). The term ‘support’ here relates to the ability of 
 +workflow management systems to control the execution of business processes. 
 + 
 +Contemporary workflow management systems lack //flexibility//, i.e., the system 
 +controls in detail how employees should execute business processes. While workflow 
 +management systems deal well with predictable business processes, they are 
 +not able to handle unforeseen situations, which occur often in real-life business 
 +processes. Although employees mostly have the knowledge and experience that 
 +enables them to deal with exceptional situations, they are not able to apply the 
 +right action because the system enforces the standard procedure of work. This often 
 +has various undesired consequences: work is done ‘outside’ the system, work 
 +cannot be done in the appropriate way, dissatisfaction of employees, resistance 
 +towards the system, etc. As a result, workflow management systems cannot be 
 +used properly if it is necessary that employees control the execution of business 
 +processes. 
 + 
 +This thesis proposes a new approach to workflow management systems that 
 +can facilitate contemporary business processes in a better way by enabling a better 
 +balance between flexibility and support. As opposed to traditional approaches 
 +which use //procedural process models// to //explicitly// (i.e.step-by-stepspecify the 
 +execution procedure, the proposed approach aims at the specification of business 
 +processes //using constraints//, i.e., processes are modeled by rules that should be followed while executing business processes. Constraint-based models //implicitly// 
 +specify the execution procedure by means of constraints: any execution that 
 +does not violate constraints is possible. In addition to proposing a constraint-based 
 +approach, a concrete language for specification of constraints is given and 
 +the proof-of-concept prototype **declare** is described.
  
 ===== Links ===== ===== Links =====
  
-{{publications:mpesic_phdthesis.pdf|Download PDF}} (XX MB)+{{publications:.pdf|Download PDF}} (4,535 MB)