Identifying bug duplicates in the unified project model

Bachelorarbeit am Lehrstuhl für angewandte Softwaretechnik

11.03.2010, Abschlussarbeiten, Bachelor- und Masterarbeiten

Bug reports keep track of the bugs that a software product was delivered with and allow the development team to plan upcoming releases. Regardless of who submits the bug, there always is a certain risk that the bug already exists. So it is crucial to identify duplicate bugs...

... in order to reduce planning overhead and to avoid unnecessary efforts of developers: When there is no possibility to identify bug duplicates, two developers might be working in parallel on the solution of the problem. This risk would even increase when developers are globally distributed. Usually the problem is addressed by defining a process in which incoming bug reports or feature request are checked manually for their uniqueness. With a growing size of the bug database, this approach is error prone. However, recent research has found methods to deal with this automatically, so bug descriptions could be reliably checked for their uniqueness.

The unified project model of the UNICASE platform allows for the creation of bug reports and feature requests. In particular, it enables the linking of project artifacts to elements of the software system model, i.e. a bug report could be linked to the implementation classes it affects. This feature might be used to improve existing approaches to identify bug reports.

Mehr Information: Beschreibung der Arbeit
Betreuer: Florian Schneider

Kontakt: Florian Schneider