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 …

Software developers need access to different kinds of information which is often dispersed
among different documentation sources, such as API documentation or Stack Overflow. We …

In theory,(good) documentation is an invaluable asset to any software project, as it helps
stakeholders to use, understand, maintain, and evolve a system. In practice, however …

Automated test generation tools have been widely investigated with the goal of reducing the
cost of testing activities. However, generated tests have been shown not to help developers …

Most software maintenance and evolution tasks require developers to understand the
source code of their software systems. Software developers usually inspect class comments …

Non-recurring traffic congestion is caused by temporary disruptions, such as accidents,
sports games, adverse weather, etc. We use data related to real-time traffic speed, jam …

Source code summaries are concise representations, in form of text and/or code, of complex
code elements and are meant to help developers gain a quick understanding that in turns …

This paper describes the results of a large (+ 1100 responses) survey of professional
software developers concerning standards for naming source code methods. The various …

Despite software history being indispensable for developers, there is little empirical
knowledge about how they examine software history. Without such knowledge, researchers …

Software developers often do not possess the knowledge needed to understand a piece of
code at hand, and the lack of code comments and outdated documentation exacerbates the …