|Wagner, Sebastian: A Concept of Human-oriented Workflows. |
Universität Stuttgart, Fakultät Informatik, Elektrotechnik und Informationstechnik, Diplomarbeit Nr. 2987 (2010).
121 Seiten, englisch.
|CR-Klassif.||H.4.1 (Office Automation)|
K.1 (The Computer Industry)
D.2.1 (Software Engineering Requirements/Specifications)
D.2.10 (Software Engineering Design)
D.2.11 (Software Engineering Software Architectures)
D.2.13 (Software Engineering Reusable Software)
C.3 (Special-Purpose and Application-Based Systems)
In industry and research workflow technologies gain more and more attention. One aim of workflows is to bridge the gap between the IT and the business world. In order to do so, business processes are described in workflow languages that can be understood and executed by IT systems to orchestrate the activities of a workflow. In the past a lot of research was done in the area of automated business workflows that can be described with the Business Process Execution Language (BPEL) or other workflow languages. These workflows consist of a set of activities that are performed automatically by a piece of software. However, a variety of scenarios exist where people participate in the execution of business processes. Many workflow languages address the importance of human interactions (e.g. BPEL with the BPEL4People extension) by providing means to model human activities. They also address issues like the assignment of one or more people to a unit of work (i.e. to an activity) and the coordination of human interactions with the activity. Nevertheless, the most workflow languages don not take the special requirements concerning the control-flow of a business process with human interaction into consideration. Especially, workflows that consist solely of activities that have to be performed by humans should be more flexible than automated business workflows. To give them more freedom to decide in which order they want to perform certain activities of the workflow.
|Abteilung(en)||Universität Stuttgart, Institut für Architektur von Anwendungssystemen|
|Eingabedatum||4. Februar 2010|