An examination of software engineering work practices

By Janice Singer, Timothy C. Lethbridge, Norman G. Vinson, Nicolas Anquetil. Conference of the Centre for Advanced Studies on Collaborative Research, 2010

362 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Information Systems

View Paper: https://www.semanticscholar.org/paper/87cc9fb5129781b74750d88f83472f2cd644ca60

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

In Information Systems

Citations in the corpus

Retrieval-based Neural Source Code Summarization (2020, background): “Developers often spend a lot of time on reading and comprehending programs [11, 32, 33, 51] when there is no good software documentation [31, 53].”
What distinguishes great software engineers? (2019, background): “…many studies examining everyday activities of software engineers find that engineers spend significant time performing non-coding activities (Singer et al. 1997; Perry et al. 1994), including conflict resolution (Gobeli et al. 1998), bug triaging (Anvik et al. 2006; Aranda and Venolia 2009)…”
Context2Name: A Deep Learning-Based Approach to Infer Natural Variable Names from Usage Contexts (2017, background): “Developers invest a significant portion of their time in reading and understanding code [35].”
Recovering clear, natural identifiers from obfuscated JS names (2017, background): “3106289 Studies show that programmers spend a large portion of their work time reading code and trying to understand it [43].”
A Study of Visual Studio Usage in Practice (2016, background): “4) A discussion of opportunities to advance the research in IDEs and developer-assistance tools.”
An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks (2006, background): “During this period, software developers spend much of their time exploring unfamiliar parts of a software system’s source code in order to understand the parts of the system that are relevant to their current task [47].”
Asking and Answering Questions during a Programming Change Task (2008, methodology): “In this paper, we report on an analysis of the data from these two user studies.”
How developers search for code: a case study (2015, background): “With a more focused study of one programmer, that same study revealed that a search task is performed on 57% of the days in which a programmer works, and that search is the most frequently-performed activity [29].”
Studying Software Engineers: Data Collection Techniques for Software Field Studies (2005, methodology): “For example, we have performed field studies where we learned about software design and maintenance, and then successfully applied our results to tool design and integration (Singer et al., 1997, 1998).”
Programmers' build errors: a case study (at google) (2014, background): “[16] observed programmer work at a large company, via logging tool use as well as direct observation.”
Deep Code Search (2018, background): “Code search is a very common activity in software development practices [57, 68].”
Maintaining mental models: a study of developer work habits (2006, methodology): “First we ran three experienced developers through the survey using a think-out-loud protocol.”