To content
Fakultät für Informatik

Bachelor-/Master-Theses

Here you find useful information on bachelor or master theses in our group.

We are currently (WS24/25) over capacity!
If you plan to start in the next Summer contact us in January 2025.

Also, have a look at our Frequently Asked Questions

Things that you might want to know...

Frequently Asked Questions

If the topic falls into our research areas, we might. However, please check your topic according to the following points:

  • Is there a research question?
  • Does you topic involve something else than constructing (e.g. implementing) something? 
  • Does your topic motivate you enough to work on it for roughly 6 month?
  • Do you have a written topic proposal (roughly one page DIN A4)?

If you can answer all of these questions with a strong yes, then please send us your topic for consideration. 

That's a clear no for a Master thesis. 

For a Bachelor thesis: 

  • Check that the proposed topic fulfills the criteria above
  • If it is a company we already work with, then it is generally possible
  • If it is a company we do not work with, then the answer is: it's complicated

What does "it's complicated" mean? We have to clarify expectations with the company. Your thesis project is an academic project within your course of study and, therefore, cannot be something like a work package for that company. This is furthermore complicated by intellectual property laws, as the usual clause of §69b UrhG does not apply here. 

Yes, that is possible and actually preferred. The company advisor needs to fill out the form "Betreuung von Abschlussarbeiten" from the faculty website:
https://www.cs.tu-dortmund.de/nps/de/Studium/Ausschuesse_pp/PA_MZA/Formulare_PA/index.html

Please prepare this form and send it to us. 

There is no official binding restriction on that. So you are free to use whatever you feel best. Please do explain in the beginning of your thesis what you will use.

Given the history and current state in computer science, however, it might be a good idea to use it. 
There is an official recommendation from the university here (but in German): (PDF) Empfehlungen der TU Dortmund zur geschlechtergerechten Sprache
For English there is a good recommendation from the UN: Guidelines for gender-inclusive language in English

And finally there is a very nice informative rant on YouTube from Tom Scott.

In general you are responsible for your own time management for the thesis project. Hence, we will not check if you are still in a time plan and will not create one. However, we will -- of course -- supervise and help with your progress. This means that we will arrange for a 30 minute meeting every 2 weeks. If there is the need for more or longer discussions that of course is always possible, but we found that this is a sustainable pace for most students. The meeting is not meant as a status meeting, but rather to clarify questions or to discuss research results. 

Research Topics

In general, we work on the follwing research topics and offer topics in these areas. For more information have a look at our recent publications

Software Ecosystems
Static Program Analysis
Research Quality (e.g. Artifact Sharing, Reproducibility, ...)


 

Past Thesis Titles

Below you will find a list of titles (partially in German) of past theses.
 

Empirische Untersuchung von Shift-Left-Ansätzen im Kontext von sicherheitsfokussierten Softwareprojekten
Inter-procedural Static Analysis for Unsafe Rust using PhASAR
Analyse der direkten und transitiven Auswirkungen von Schwachstellen im PyPI-Ökosystem
A Qualitative Analysis of Benchmark Creation using Sample Coverage
Systematic Identification of Java Reflection in Static Analysis
Evaluating the benefits of a distributed microservice-oriented implementation for DGMF
Analyzing possible calls from inside libraries to methods that are not known at compile time
Optimization and Evaluation of an Information Retrieval Based Test Selection Approach
Auswertung des Potentials von inkrementeller Callgraph-Analyse auf Ökosystem-Ebene
Automatisierung von Software Supply Chain Security in Softwarekomponentenökosystemen
Detecting vulnerable call chains in JavaScript applications
Using Structural UML Diagrams and Static Code Analysis for Coverage Evaluation of Integration Tests
Detektion von Sicherheitslücken in Installationsskripten des NuGet Ökosystems
Testumgebung für C/C++-basierte statische Programmanalyse
Prädiktive, statische Energieverbrauchsanalyse basierend auf experimentell ermittelten Energiemodellen
Analyzing the security impact of npm dependencies
Comparative Study of Android Library Detection Tools
Analyse der Korrelation der Änderung von Metrik-Werten bei Versionsübergängen unter Semantic Versioning
Prevalence, Shape and Characteristics of Activism in Software Package Ecosystems
Visualizing the Transitive Impact of Vulnerabilities onto Software Ecosystems
Analyse der Speicher- und Abfrageperformance verschiedener Datenbank-Technologien im Kontext großer Callgraphen
Analyse verschiedener objektorientierter Software-Metriken über unterschiedliche Plattformen und Repositories
Breaking Changes in Maven Central – A Partial Replication Study and an Investigation of Version Schemes
Dateisystemkompromittierung durch NPM-Abhängigkeiten / Compromising file systems with npm dependencies