Student Theses and Projects

Below is a list of open topics. Please contact us for further topics.

 


ImitGraphs


ImitGraphs

An Imitgraph is an extended version of a simple graph designed to model software engineering graphical models. The appearance of Imitgraphs is simple, however they are complicated enough to imitate the behavior of graphical models. They are designed to replace graphical models in usability tests of user interfaces of software engineering modeling tools.
The goals of this project are (1) to develop a tool that allows its users to create and manipulate Imitgraphs, and (2) to conduct experiments in order to find the extent to which imitgraphs behave like graphical models.

Contact: Parisa Ghazi

 

 


Flexible Artifact Visualization


FlexiView
Software engineers deal with a great amount of information embedded in artifacts. To overcome the limited screen space, they have to scroll, zoom and open multiple windows.
FlexiView employs a physical metaphor of magnets and springs to (i) shrink the less important objects on the screen, (ii) enlarge the more important objects and (iii) hide the unnecessary details. FlexiView is a new way of visualizing information for applications that can be used to manage and manipulate artifacts.
For more information please visit Flexible Artifact Visualization webpage. If you are interested in doing your master thesis, master project or bachelor project within this project contact Parisa Ghazi.

 

 


Feedback Configuration and Advanced Feedback Mechanisms


Feedback gathering is an emerging topic in research and industry as end-user feedback is a valuable information for software development and software evolution. Thus, existing feedback tools allow a high number of end-users to communicate their needs and opinions about a deployed software system. However, a holistic feedback tool solution that is available for several platforms and supports various end-users in different situations to provide feedback is missing. In the SUPERSEDE EU project, we have developed modular Android and web feedback mechanisms that can be customized based on the needs of the feedback receivers and senders. With our current solution, end-users are able to communicate feedback with text, ratings, selections, annotated screenshots, audio recordings and attachments. As these feedback mechanisms are built-in, the end-users can communicate the feedback easily in the hosting application.

The goal of this master project is to develop a so-called Feedback Configurator which allows even nontechnical feedback receivers (e.g., product owners, designers) to select, adapt and edit the modular feedback mechanisms in a graphical user interface. With the help of the Feedback Configurator the feedback receiver should be able to test which feedback mechanisms support and motivate their end-users best. The existing feedback mechanisms are currently evaluated in the SUPERSEDE EU project and depending on the evaluation results the master project might include to modify and improve the existing feedback mechanisms and to realize new feedback mechanisms.

The master project students should be interested in software evolution, usability engineering, and user involvement. There is the possibility of working with industrial partners.

For more information, contact Norbert Seyff.

 



Feedback Discussion and Negotiation between End-Users and Developers


Built-in feedback tools allow a high number of end-users to communicate their needs and opinions about a deployed software system. For example, in the SUPERSEDE EU project, we have developed modular Android and web feedback mechanisms. However, currently end-users are not informed about the status of their feedback requests. Early research results suggest that replies to feedback can increase the motivation of end-users (i.e., feedback senders) such that they provide feedback continuously. Furthermore, the discussion and negotiation of feedback among end-users and between end-users and developers (i.e., feedback receivers) is not supported by current feedback approaches. For example, end-users currently do not have the option to comment on feedback sent by others and developers cannot ask questions for clarification. This, among other things, is one reason why the quality of the communicated feedback is sometimes low and developers cannot consider it for system evolution. Ideally, feedback sent would result in better ideas for new features or quicker problem solutions.

The goal of this master project is to develop solutions supporting the discussion and negotiation of feedback among feedback senders and between feedback senders and receivers. Moreover, the feedback sender should receive information about the current status of the request.

The master project students should be interested in requirements engineering and user involvement. There is the possibility of working with industrial partners.

For more information, contact Norbert Seyff.

 

 


FlexiSketch (Cross-Platform)


FlexiSketch: Sketch-Based Requirements Modeling Editor

FlexiSketch is an editor that allows for free sketching of diagrams and tagging of distinct objects, includes a sketch recognition algorithm, and supports multitouch. The newest version of FlexiSketch is implemented with the gaming framework CoronaSDK (scripting language LUA) and runs on Android, iOS, Mac, and PC. More about FlexiSketch, including links to the tool and videos, can be found here. Information about the theoretical background can be found here.

We now need to make the newest version of FlexiSketch ready for a release in the App Store and Google Play Store. This includes implementing improvements as well as testing and bugfixing. We are seeking students who would like to do this as a master project. If you are interested, please contact Dustin Wüest.

This project should start as soon as possible and needs to be finished before autum 2017.

 

 


An automated update of software documentation


Software systems evolve constantly. However, the documentation, other than source code, is often left outdated and it is not aligned with the changes that occur. This results in having an inconsistent software that is rather difficult to maintain and, in some cases, this may even result in a project failure. 

The goal of this project is to support product managers, requirements engineers, test engineers and others who are responsible for the documentation management. The support implies detecting and analyzing the changes in one document and generating hints on how to change the impacted documents. 

Besides the documentation management, students should also be interested in NLP (Natural Language Processing), since documents are often written in natural language.

If you are interested in this project, please contact Sofija Hotomski for getting more insights.