Managing software evolution through semantic history slicing
Author:
- 1 October 2017
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 1014-1017
Abstract
Software change histories are results of incremental updates made by developers. As a side-effect of the software development process, version history is a surprisingly useful source of information for understanding, maintaining and reusing software. However, traditional commit-based sequential organization of version histories lacks semantic structure and thus are insufficient for many development tasks that require high-level, semantic understanding of program functionality, such as locating feature implementations and porting hot fixes. In this work, we propose to use well-organized unit tests as identifiers for corresponding software functionalities. We then present a family of automated techniques which analyze the semantics of historical changes and assist developers in many everyday practical settings. For validation, we evaluate our approaches on a benchmark of developer-annotated version history instances obtained from real-world open source software projects on GitHub.Keywords
This publication has 19 references indexed in Scilit:
- Selective Bisection Debugging2017
- Development History Granularity Transformations (N)2015
- Early Detection of Collaboration Conflicts and RisksIEEE Transactions on Software Engineering, 2013
- The impact of tangled code changes2013
- Refactoring edit history of source code2012
- How We Refactor, and How We Know ItIEEE Transactions on Software Engineering, 2011
- History slicing2011
- Empirical Evaluation of Hunk Metrics as Bug Predictors2009
- Mining version histories to guide software changes2004
- Analyzing regression test selection techniquesIEEE Transactions on Software Engineering, 1996