Unfolding the Rationale for Code Commits
| dc.contributor.author | Alsafwan, Khadijah Ahmad | en |
| dc.contributor.committeechair | Servant Cortes, Francisco Javier | en |
| dc.contributor.committeemember | Meng, Na | en |
| dc.contributor.committeemember | Tilevich, Eli | en |
| dc.contributor.department | Computer Science | en |
| dc.date.accessioned | 2019-11-29T07:00:33Z | en |
| dc.date.available | 2019-11-29T07:00:33Z | en |
| dc.date.issued | 2018-06-06 | en |
| dc.description.abstract | One of the main reasons why developers investigate code history is to search for the rationale for code commits. Existing work found that developers report that rationale is one of the most important aspects to understand code changes and that it can be quite difficult to find. While this finding strongly points out the fact that understanding the rationale for code commits is a serious problem for software engineers, no current research efforts have pursued understanding in detail what specifically developers are searching for when they search for rationale. In other words, while the rationale for code commits is informally defined as, "Why was this code implemented this way?" this question could refer to aspects of the code as disparate as, "Why was it necessary to implement this code?"; "Why is this the way in which it was implemented?"; or "Why was the code implemented at that moment?" Our goal with this study is to improve our understanding of what software developers mean when they talk about the rationale for code commits, i.e., how they "unfold" rationale. We additionally study which components of rationale developers find important, which ones they normally need to find, which ones they consider specifically difficult to find, and which ones they normally record in their own code commits. This new, detailed understanding of the components of the rationale for code commits may serve as inspiration for novel techniques to support developers in seeking and accurately recording rationale. | en |
| dc.description.degree | MS | en |
| dc.format.medium | ETD | en |
| dc.identifier.other | vt_gsexam:15234 | en |
| dc.identifier.uri | http://hdl.handle.net/10919/95887 | en |
| dc.publisher | Virginia Tech | en |
| dc.rights | In Copyright | en |
| dc.rights.uri | http://rightsstatements.org/vocab/InC/1.0/ | en |
| dc.subject | software engineering | en |
| dc.subject | revision control systems | en |
| dc.subject | rationale | en |
| dc.subject | empirical study | en |
| dc.title | Unfolding the Rationale for Code Commits | en |
| dc.type | Thesis | en |
| thesis.degree.discipline | Computer Science and Applications | en |
| thesis.degree.grantor | Virginia Polytechnic Institute and State University | en |
| thesis.degree.level | masters | en |
| thesis.degree.name | MS | en |
Files
Original bundle
1 - 1 of 1