This thesis contains a lock flag. I am not allowed t publish this thesis neither completely nor in parts. The handout of this thesis to third persons requires a written approval of SAP.
Software products and projects can become very large and still grow over time. Building one prediction model for a whole software product might be easy but might also limit the prediction accuracy. Different parts of a software product have different duties (GUI, database, kernel,…). We found out that for each of these different code zones […]
One major down side of many defect prediction models is the frequent usability. As an example: A prediction model based on code metrics only, predicts the number of defects based upon the code complexity of each entity. Now, if the programmer fixes the bug, he might change only one line and therefore does not change […]
The IBM® Jazz™ project is a new collaboration and programming environment built on top of the Eclipse platform. The focus here lies not only on the developer himself but also on the team and the project management. This project combines common tools in a sensational way and opens new doors for software and repository mining. […]
Defect predicion is a research with high activity. A lot of work has been done in this area, also in recent months. But even if there exist a lot of approaches and techniques to predict defects and bugs accurately, many of the static approaches suffer from a fundamental flaw.
Make as a tool to control the software build process was introduced in 1979 and since then is the predominant tool for this task. Unlike then, software projects today are usually spread over multiple directories — a situation for which Make was not designed. As a consequence, the current practice of using Make recursively leads […]