Ammonia: an approach for deriving project-specific bug patterns

Hayashi, Shinpei ; Higo, Yoshiki ; et al.

In: Empirical Software Engineering, Jg. 25 (2020-03-07), S. 1951-1979

Online unknown

Zugriff:

Finding and fixing buggy code is an important and cost-intensive maintenance task, and static analysis (SA) is one of the methods developers use to perform it. SA tools warn developers about potential bugs by scanning their source code for commonly occurring bug patterns, thus giving those developers opportunities to fix the warnings (potential bugs) before they release the software. Typically, SA tools scan for general bug patterns that are common to any software project (such as null pointer dereference), and not for project specific patterns. However, past research has pointed to this lack of customizability as a severe limiting issue in SA. Accordingly, in this paper, we propose an approach called Ammonia, which is based on statically analyzing changes across the development history of a project, as a means to identify project-specific bug patterns. Furthermore, the bug patterns identified by our tool do not relate to just one developer or one specific commit, they reflect the project as a whole and compliment the warnings from other SA tools that identify general bug patterns. Herein, we report on the application of our implemented tool and approach to four Java projects: Ant, Camel, POI, and Wicket. The results obtained show that our tool could detect 19 project specific bug patterns across those four projects. Next, through manual analysis, we determined that six of those change patterns were actual bugs and submitted pull requests based on those bug patterns. As a result, five of the pull requests were merged.

Comment: 28 pages, Empirical Software Engineering

Titel:	Ammonia: an approach for deriving project-specific bug patterns
Autor/in / Beteiligte Person:	Hayashi, Shinpei ; Higo, Yoshiki ; Hata, Hideaki ; Nagappan, Meiyappan
Link:	View record in OpenAIRE (Volltext) E-Journal im Bestand der UB Hagen? https://doi.org/10.1007/s10664-020-09807-w
Zeitschrift:	Empirical Software Engineering, Jg. 25 (2020-03-07), S. 1951-1979
Veröffentlichung:	Springer Science and Business Media LLC, 2020
Medientyp:	unknown
ISSN:	1573-7616 (print) ; 1382-3256 (print)
DOI:	10.1007/s10664-020-09807-w
Schlagwort:	FOS: Computer and information sciences Source code Java Computer science Fix recommendation media_common.quotation_subject 02 engineering and technology Change patterns Task (project management) Computer Science - Software Engineering Software Pattern mining 020204 information systems 0202 electrical engineering, electronic engineering, information engineering Code (cryptography) computer.programming_language media_common business.industry 020207 software engineering Static analysis Software Engineering (cs.SE) Project-specific bug patterns Software engineering business computer
Sonstiges:	Nachgewiesen in: OpenAIRE Rights: OPEN

Klicken Sie ein Format an und speichern Sie dann die Daten oder geben Sie eine Empfänger-Adresse ein und lassen Sie sich per Email zusenden.

BibTeX Citavi, JabRef, u.a.
(Literaturverwaltung)

PDF kein Volltext!
(Merkzettel, Notizen)

RIS Endnote, Citavi u.a.
(Literaturverwaltung)

MODS
(XML zur Weiterverarbeitung)

oder

Wählen Sie das für Sie passende Zitationsformat und kopieren Sie es dann in die Zwischenablage, lassen es sich per Mail zusenden oder speichern es als PDF-Datei.

Gewünschter Zitations-Stil:

oder

Bitte prüfen Sie, ob die Zitation formal korrekt ist, bevor Sie sie in einer Arbeit verwenden. Benutzen Sie gegebenenfalls den "Exportieren"-Dialog, wenn Sie ein Literaturverwaltungsprogramm verwenden und die Zitat-Angaben selbst formatieren wollen.