Theses

This page collects some information for students interested in doing a thesis with out team.

General advice

• Have a look at this OLAT pseudo-course for thesis topics.
• Talk to the team to find out about topics.
• Eventually, you would need to author an expose, but let's talk first.
• We offer some advice on the structure of a thesis.
• Please consider using the Softlang Style for your thesis.
• We consider thesis projects with industry under certain conditions.

Illustrative topics

The following list is TERRIBLY outdated. That is, some of these topics led to theses several years ago. (Some of the descriptions may require a uniko login.) You really want to check out our OLAT pseudo-course for thesis topics.

• A declarative build system for a language repository (.html)
• A Web API for Linked Software Data (.html)
• Topic analysis for conferences (.html)
• DSL for SSS in document management (.html)
• Co-evolution for a development stack (.html)
• Software analysis in IT controlling (.pdf)
• The notion of projectional editing (.pdf)
• A messaging-based IDE (.pdf)
• A potpourri of software analyses (.pdf)
• A potpourri of software transformations (.pdf)
• Types checking web apps (.html)
• Co-evolving web apps (.pdf)
• Analysis of chrestomathies in linguistics (.pdf)
• IT enterprise profiling (.pdf)
• Migration to the cloud (.pdf)
• Licensing in academic OS development (.pdf)
• Domain-specific languages in space (.pdf)
• Package platform integration (.pdf)
• A systematic SL(E) survey (.pdf)
• Software ontology mining (.pdf)
• Software ontology re-engineering (.pdf)
• Literate deployment scripting (.pdf)
• Language-parametric fact extraction and fragment location (.pdf)
• Metrics-based comparison across languages (.pdf)
• Build automation for large heterogeneous software repositories (.pdf)
• Model-based wiki page validation (.pdf)
• An AOP-centric 101theme (.pdf)
• Managing similarity and variability in a software chrestomathy (.pdf)
• Best SE practices for heterogenous Java projects (.pdf)
• Technology study on semantic wikis (.pdf)
• Wikipedia’s ontology of software languages (.pdf)
• Integrate 101companies and StackOverflow (.pdf)
• Vocabulary mining for a software product (.pdf)
• Metrics-based comparison of a software chrestomathy (.pdf)
• Technology adoption for a versioned corpus (.pdf)
• Semi-automatic feature tagging (.pdf)
• An iOS-based 101theme (.pdf)
• Binding of megamodels for software technologies (.html)
• Business models for “CS academics teach IT professionals” (.pdf)
• Screaming fast model transformations with deforestation (.pdf)
• The state of the art in DSL implementation in the wild (.pdf)
• Analysis of the privacy vocabulary of gmail, FB, et al.
• Binding generator for Eclipse’s object model for Java
• Megamodels for popular programming technologies
• Language extensions for programmable object-model mappings
• Analysing the scope of API usage scenarios in source code
• The role of annotations & XML in framework usage
• Managing variability in a repository with programming samples
• Re-hosting 101companies from Sourceforge (svn) to git
• Risk analysis for industrial use of open-source APIs
• A transformation language for Wiki evolution (.pdf)
• Characterization of BigData and noSQL technologies
• Technologies for API usage analysis and transformation (Joachim Pehl)
• Haskell programming technologies (Thomas Schmorleiz)
• Reproducible wrapper for API migration (Malte Knauf)
• Clone detection for course work (Michael Lellmann)
• Deltas for MapReduce computations (David Saile)
• Systematic comparison of web-programming technologies (Tobias Zimmer) (.pdf)
• Bulk load in data warehousing (Mehmet-Sefa Usta)
• An aspect-oriented programming approach for PHP (Markus Schulte)
• Corpus engineering for fact extraction from Java projects (David Klauer)
• Analysis of frameworkiness for open-source Java projects (Jan Baltzer)
• Algebraic properties of MapReduce computations (Andreas Brandt)
• API usage analysis for SourceForge projects (Jürgen Starek)
• API usage analysis for the .NET platform (Rufus Linke)