Preprocessing CVS data for fine-grained analysis

Zimmermann, Thomas; Weißgerber, Peter

doi:10.1049/ic:20040466

Cited by 176 publications

(135 citation statements)

References 14 publications

Supporting

Mentioning

131

Contrasting

Unclassified

Order By: Relevance

“…The common approach to link the modifications to the bug reports is to look for pointers in the commit messages to the bug tracking database [3], [21], [22]. For Eclipse, we follow a similar approach and employ regular expressions for an accurate reconstruction of the links between the bug reports and the corresponding modifications as follows: 1) Scanning the repository logs, group the files that are modified by the same author with the same commit message with a time fuzziness of 200 seconds [23]. This step is necessary as CVS repositories store the changes made to each file separately.…”

Section: Experimental Evaluationmentioning

confidence: 99%

Assisting code search with automatic Query Reformulation for bug localization

Sisman

Kak

2013

2013 10th Working Conference on Mining Software Repositories (MSR)

View full text Add to dashboard Cite

Abstract-Source code retrieval plays an important role in many software engineering tasks. However, designing a query that can accurately retrieve the relevant software artifacts can be challenging for developers as it requires a certain level of knowledge and experience regarding the code base. This paper demonstrates how the difficulty of designing a proper query can be alleviated through automatic Query Reformulation (QR) -an under-the-hood operation for reformulating a user's query with no additional input from the user. The proposed QR framework works by enriching a user's search query with certain specific additional terms drawn from the highest-ranked artifacts retrieved in response to the initial query. The important point here is that these additional terms injected into a query are those that are deemed to be "close" to the original query terms in the source code on the basis of positional proximity. This similarity metric is based on the notion that terms that deal with the same concepts in source code are usually proximal to one another in the same files. We demonstrate the superiority of our QR framework in relation to the QR frameworks wellknown in the natural language document retrieval by showing significant improvements in bug localization performance for two large software projects using more than 4,000 queries.

show abstract

Section: Experimental Evaluationmentioning

confidence: 99%

Assisting code search with automatic Query Reformulation for bug localization

Sisman

Kak

2013

2013 10th Working Conference on Mining Software Repositories (MSR)

View full text Add to dashboard Cite

show abstract

“…We converted the commit stream into a sequence of transactions. Following common practice for mining CVS repositories [21], we considered all commits sharing a user and log message performed during a given time window to constitute a transaction. After this step, the change history of the system can be abstracted as a series of We then considered that each set of changed elements associated with a transaction formed a basic concern mapping.…”

Section: Methodsmentioning

confidence: 99%

Reusing Program Investigation Knowledge for Code Understanding

Robillard

Manggala

2008

2008 16th IEEE International Conference on Program Comprehension

View full text Add to dashboard Cite

show abstract

“…Such information includes details such as how the code was changed, the files affected by the change, when the change was made, who made the change, and an optional explanation (known as the log message) as to why the change was made. Several files submitted to the version archive by the same developer, at the same time, with the same log message, are said to be part of the same commit transaction [18]. Reasons for changes to the code include feature additions, bug fixes, or refactoring.…”

Section: Version Archivesmentioning

confidence: 99%