This paper presents a literature review in the field of summarizing software artifacts, focusing
on bug reports, source code, mailing lists and developer discussions artifacts. From Jan …

Predictive models are one of the most important techniques that are widely applied in many
areas of software engineering. There have been a large number of primary studies that …

Technical debt is a metaphor to describe the situation in which long-term code quality is
traded for short-term goals in software projects. Recently, the concept of self-admitted …

Learning and remembering how to use APIs is difficult. While code-completion tools can
recommend API methods, browsing a long list of API method names and their …

Bug triaging refers to the process of assigning a bug to the most appropriate developer to fix.
It becomes more and more difficult and complicated as the size of software and the number …

Detecting duplicate bug reports helps reduce triaging efforts and save time for developers in
fixing the same issues. Among several automated detection approaches, text-based …

Bug reports represent an important information source for software construction.
Misclassification of these reports inevitably introduces bias. Manual examinations can help …

Consider a question and its answers in Stack Overflow as a knowledge unit. Knowledge
units often contain semantically relevant knowledge, and thus linkable for different purposes …

Software developers access bug reports in a project's bug repository to help with a number
of different tasks, including understanding how previous changes have been made and …

Bugs are prevalent in software systems. Some bugs are critical and need to be fixed right
away, whereas others are minor and their fixes could be postponed until resources are …