Software history under the lens: A study on why and how developers examine it

Mihai Codoban, Sruti Srinivasa Ragavan, Danny Dig, Brian Bailey

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

Despite software history being indispensable for developers, there is little empirical knowledge about how they examine software history. Without such knowledge, researchers and tool builders are in danger of making wrong assumptions and building inadequate tools. In this paper we present an in-depth empirical study about the motivations developers have for examining software history, the strategies they use, and the challenges they encounter. To learn these, we interviewed 14 experienced developers from industry, and then extended our findings by surveying 217 developers. We found that history does not begin with the latest commit but with uncommitted changes. Moreover, we found that developers had different motivations for examining recent and old history. Based on these findings we propose 3-LENS HISTORY, a novel unified model for reasoning about software history.

Original languageEnglish (US)
Title of host publication2015 IEEE 31st International Conference on Software Maintenance and Evolution, ICSME 2015 - Proceedings
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages1-10
Number of pages10
ISBN (Electronic)9781467375320
DOIs
StatePublished - Nov 19 2015
Event31st IEEE International Conference on Software Maintenance and Evolution, ICSME 2015 - Bremen, Germany
Duration: Sep 29 2015Oct 1 2015

Publication series

Name2015 IEEE 31st International Conference on Software Maintenance and Evolution, ICSME 2015 - Proceedings

Other

Other31st IEEE International Conference on Software Maintenance and Evolution, ICSME 2015
Country/TerritoryGermany
CityBremen
Period9/29/1510/1/15

Keywords

  • human aspects of software evolution
  • software change management
  • software history
  • user studies

ASJC Scopus subject areas

  • Software

Fingerprint

Dive into the research topics of 'Software history under the lens: A study on why and how developers examine it'. Together they form a unique fingerprint.

Cite this