Herodotos, l'historien de vos défauts

Nicolas Palix

Herodotos, l'historien de vos défauts

Nicolas Palix

Department of Computer Science

Abstract

Software is continually evolving, to improve performance, correct errors, and add new features. Code modifications, however, inevitably lead to the introduction of defects. To prevent the introduction of defects, one has to understand why they occur. Thus, it is important to develop tools and practices that aid in defect finding, tracking and prevention. {I}n this paper, we propose a methodology and associated tool, Herodotos, to study defects over time. Herodotos semi-automatically tracks defects over multiple versions of a software project, independent of other changes in the source files. It builds a graphical history of each defect and gives some statistics based on the results. We have evaluated this approach on the history of a representative range of open source projects over the last three years. For each project, we explore several kinds of defects that have been found by static code analysis. We analyze the generated results to compare the selected software projects and defect kinds.

Original language	French
Title of host publication	7e Conférence Francaise en Systèmes d'Exploitation (CFSE)
Number of pages	12
Publication date	2009
Publication status	Published - 2009
Event	RenPar’19 / SympA’13 / CFSE’7 - Toulouse, France Duration: 9 Sept 2009 → 11 Sept 2009 Conference number: 19

Conference

Conference	RenPar’19 / SympA’13 / CFSE’7
Number	19
Country/Territory	France
City	Toulouse
Period	09/09/2009 → 11/09/2009

Access to Document

http://www.diku.dk/hjemmesider/ansatte/npalix/papers/cfse09-palix.pdf

Cite this

@inproceedings{87dae5b0c2e611debda0000ea68e967b,

title = "Herodotos, l'historien de vos d{\'e}fauts",

abstract = "Software is continually evolving, to improve performance, correct errors, and add new features. Code modifications, however, inevitably lead to the introduction of defects. To prevent the introduction of defects, one has to understand why they occur. Thus, it is important to develop tools and practices that aid in defect finding, tracking and prevention. {I}n this paper, we propose a methodology and associated tool, Herodotos, to study defects over time. Herodotos semi-automatically tracks defects over multiple versions of a software project, independent of other changes in the source files. It builds a graphical history of each defect and gives some statistics based on the results. We have evaluated this approach on the history of a representative range of open source projects over the last three years. For each project, we explore several kinds of defects that have been found by static code analysis. We analyze the generated results to compare the selected software projects and defect kinds.",

author = "Nicolas Palix",

year = "2009",

language = "Fransk",

booktitle = "7e Conf{\'e}rence Francaise en Syst{\`e}mes d'Exploitation (CFSE)",

note = "RenPar{\textquoteright}19 / SympA{\textquoteright}13 / CFSE{\textquoteright}7 ; Conference date: 09-09-2009 Through 11-09-2009",

}

TY - GEN

T1 - Herodotos, l'historien de vos défauts

AU - Palix, Nicolas

N1 - Conference code: 19

PY - 2009

Y1 - 2009

N2 - Software is continually evolving, to improve performance, correct errors, and add new features. Code modifications, however, inevitably lead to the introduction of defects. To prevent the introduction of defects, one has to understand why they occur. Thus, it is important to develop tools and practices that aid in defect finding, tracking and prevention. {I}n this paper, we propose a methodology and associated tool, Herodotos, to study defects over time. Herodotos semi-automatically tracks defects over multiple versions of a software project, independent of other changes in the source files. It builds a graphical history of each defect and gives some statistics based on the results. We have evaluated this approach on the history of a representative range of open source projects over the last three years. For each project, we explore several kinds of defects that have been found by static code analysis. We analyze the generated results to compare the selected software projects and defect kinds.

AB - Software is continually evolving, to improve performance, correct errors, and add new features. Code modifications, however, inevitably lead to the introduction of defects. To prevent the introduction of defects, one has to understand why they occur. Thus, it is important to develop tools and practices that aid in defect finding, tracking and prevention. {I}n this paper, we propose a methodology and associated tool, Herodotos, to study defects over time. Herodotos semi-automatically tracks defects over multiple versions of a software project, independent of other changes in the source files. It builds a graphical history of each defect and gives some statistics based on the results. We have evaluated this approach on the history of a representative range of open source projects over the last three years. For each project, we explore several kinds of defects that have been found by static code analysis. We analyze the generated results to compare the selected software projects and defect kinds.

M3 - Konferencebidrag i proceedings

BT - 7e Conférence Francaise en Systèmes d'Exploitation (CFSE)

T2 - RenPar’19 / SympA’13 / CFSE’7

Y2 - 9 September 2009 through 11 September 2009

ER -