Open Topics

The Workflow Systems and Technologies Group offers topics for bachelor and master theses as well as Master Praktikum. The following list contains a number of current suggestions for topics.

To discuss one of those or any other topic in this research field, please contact the particulary named supervisor.

» Jump to Bachelor thesis topics

» Jump to Master thesis topics

Master Praktikum

Supervision Univ.-Prof. Dr. Stefanie Rinderle-Ma

If you are interested in doing a Master Praktikum (053021) at the WST research group, have a look at the available topics.



  • Distributed business processes (including the topic on the C3Pro (see C3Pro project) project online)

  • Process Mining in Network Data

  • Identification of (Political) Bots in Social Network Data

  • Blockchain and BPM


Master thesis topics

Supervision Univ.-Prof. Dr. Stefanie Rinderle-Ma

Topic 1: Implementing a web-based C3Pro editor (see C3Pro project)

Change is one of the main focus points in the C3Pro project, which stands for "Change and Compliance for Collaborative Processes". In collaborative processes, private processes are the individual business process models of the participating businesses. The public view or public processes abstract the private processes in such a way that only the public activities -- those where another partner is also involved -- are shown. Change in such an inter-organisational context is challenging, as a single modification from one participant in its own private process might impact some partners' related public processes, which in turn could trigger transitive changes to other partners. The correct propagation of change is an important challenge, which is being tackled on in the C3Pro Project.

We have implemented a change propagation library in the Java programming language, which takes into consideration all the changes partners have to perform for various change activities: insert, replace, and delete. Based on this library, we have implemented a desktop-based editor for visualising and simulating various change scenarios. The proposed bachelor project's goal would be implementing the same editor as a web-based prototype. Having a web-based editor for interactive change management would make the topic more accessible for everyone, allowing them to see the effects of changes in an inter-organisational context. This prototype would:

  1. Visualise choreography models as well as participating partner's public processes.
  2. Display related activities on all partners' public processes.
  3. Display the proposed changes and affected fragments (direct as well as transitive).
  4. Display statistics after applying and propagating changes.

Requirements / Programming Languages:

  • Java (server-side) or other JVM-based languages
  • Javascript (client-side) or other languages compiled to Javascript (HaXe, Clojurescript, Coffeescript etc.)
  • Clojure (optional, to understand the current editor)


  • Web Services
  • HTML 5
  • Web Sockets
  • AJAX

Due to the long lifecycle, many things can change even if they change slowly: assets are replaced by new ones; new components and services are added on top of existing systems; companies merge and split; key employees may leave. As a result, even if the system has been commissioned with a clear blueprint, the operators can partially lose track of their IT inventory. Without a clear view of their IT assets (PCs, equipment, field devices, and networks) in the first place, it is impossible to secure them. As such, operators do not have clear visibility into attacks underneath the production monitoring surface.

Bachelor theses topics

Supervision Univ.-Prof. Dr. Erich Schikuta

Thema: Implementierung von eLearning Komponenten in webAD

webAD ist ein interaktives eLearning System zur Visualisierung des dynamischen Verhaltens von Algorithmen und Datenstrukturen.
webAD wurde im Rahmen von mehreren Diplom- und Bachelorarbeiten an der RG WST entwickelt (webAD Projekt Seite).
Ziel ist der Einsatz von webAD im Modul ADS zur Unterstützung der Studierenden.

Spezifisches Ziel der PR Arbeit(en) ist die Realisierung von Algorithmen und/oder Datenstrukturen und deren Visualisierung mit HTML, CSS und JavaScript.

Max. Anzahl von Studierenden: 1

InteressentInnen moegen sich bei Erich Schikuta per email (erich.schikuta(at) zwecks Terminvereinbarung melden.


Supervision Univ.-Prof. Dr. Stefanie Rinderle-Ma


Topic 1a: Implementing a prototype for resolving relations between constraints from text documents


Based on our publication for resolving relations between constraints in text documents, the goal is to re-implement the existing method. Therefore, a comparison of state-of-the-art NLP tools and the use of object oriented programming principles is required. The implementation should be carried out in Python 3.



Topic 1b: Developing a web service for a graph-based representation of relations between constraints


The derived relations between constraints should be visualized using a graph-based representation. Further requirements are to make the visualization accessible via a web service and to set up hyperlinks to the corresponding text passages in the documents.



Topic 2: Process Mining Web Based

Helping to identify the actual executed business processes, process mining is still an emerging topic. A plethora of mining algorithms has already been published during the last years and mostly implemented in the process mining framework ProM. While ProM allows users to apply certain mining algorithms, the results can be only exported as a picture at best. To help researchers, to find every detail of a business process, a web services oriented structure is useful, allowing different services to process the data gathered by the mining algorithms. The goal of this bachelor thesis is the implementation of already elaborated process mining algorithms, as a web service. Following skills come in handy:

  • Knowledge of high level programming languages like Ruby and Python.
  • Knowledge of REST web services.
  • Some general knowledge about business processes and modeling business processes


May the force be with you


Topic 3: Frontend Web-App-Development Technologies in Information Systems for Industrial Software Engineering


The web-app oHA (powered by LuxActive - is a tourism e-service and information system which is particularly efficient in a WiFi where every guest gets the service automatically on it's own mobile device. This is performed with the self-developed optional hardware, the oHA Box. But oHA is also available in the web. oHA bundles many different services (promotion of tourism-provider and partner activities, weather point forecast, GPS navigation, pushup notification in a new way, local news, PDF storage, reservation, time planing, recommendations and much more) and activities (events, tours, POIs), from many different sources as big data service, combined with a semantic search function as individual guest service and marketing channel. Once loaded, oHA works offline as well. The provider gets also statistics about the customer journey.

Your task is to develop a new frontend prototype which contains the semantic search view and the detail view for activities by using modern industrial web-technologies. The backend will be provided by LuxActive. After the implementation task, evaluate the outcome and used technologies against provided metrics (and possibly new developed metrics) in a scientific way.

The oHA semantic search user interface is shown in the following:

Requirements for prototype development

  • Cross browser compatibility
  • Web Components
  • Existing backend API (Java REST over JSON) Documentation for endpoints will be handed out.
Technologies / Frameworks to use (not required as skill):

Metrics for evaluation

  • Initial download size (application ready to use)
  • Maintainability of source code
    • Code complexity
    • Development Time (?Categorize for: rapid development vs product development)
  • Scalability according to concurrent users (Max)
  • Testability

Recommended skills

  • Frontend Web-App-Development with Javascript and HTML5
  • CSS
  • Git


Topic 4: Extended analysis of developer focused workflow engines

Workflows are frequently used in end-user focused environments using end-user focused graphical tools (e.g., jBPM). However, those end-user focused projects typically utilize feature crowded complex server infrastructures so that they can hardly be integrated in small to medium software projects. So, software developers often implement their own small workflow projects based on e.g. the saga or workflow pattern.

Hence, it would be interesting to analyze existing lightweight object oriented developer focused workflow engines to check their applicability in typical small to medium software projects.

A previous bachelor thesis has analyzed multiple workflow engines for their control flow definition and execution capabilities.
The approach would require to extend the results of the previous work!

You will need to:
a) Read up on workflows, workflow engines, and workflow patterns/views and perspectives (Do some study work BEFORE you apply for this thesis so that you have at least some background knowledge on these topics!)

b) Identify at least 5 different workflow which should be analyzed.
Possible sources to identify relevant open source engines are, e.g.: (search, e.g., for workflow engine and java)

The engines should preferably be written in Java (recommended) or any other object oriented programming language, maintained, and you will need to argue why the selected engines were chosen.
In addition some preselected workflow engines, at our choice, will be included!

c) Select a reasonable amount of workflow patterns from the perspective Control, Resource, Data, Exception Handling (see

The total amount of patterns should be larger or equal to 20 and should contain patterns from all 4 perspective (the last three ones are the most important ones for this work!)

d) Analyze if the engines support the selected patterns. Read the engines documentation. If no documentation is available read the code and use it as a reference, analyze given examples, communicate with the authors for examples, and so on.

You will need to IMPLEMENT the patterns, most frequently by writing source code and interacting with the API of the engine. Only modeling the patterns is not sufficient, i.e., a significant amount of code must be written! Note, if you recognize that a pattern is not support you will need to check if it would be possible, with minor self developed additions, if you can add support! For example, if an engine does not support to execute multiple workflows at once you can "add" support for this by using multiple threads spawned by your programming language of choice.

NOTE: You will need to hand in the source code!

e) Write the thesis, add a theoretical background (e.g., why workflows, why worklow engines, why developer focused engines vs larger projects), include your results, describe drawbacks and limitations of the analyzed workflow engines. Compare the results (i.e., the supported patterns) with multiple existing large scale workflow engines.