@ARTICLE{Wu14-EMSE-EyeTrackingTraceability,
   AUTHOR       = {Wei Wu and Adrien Serveaux and Yann-Ga�l Gu�h�neuc and 
      Giuliano Antoniol},
   JOURNAL      = {Empirical Software Engineering (EMSE)},
   TITLE        = {The Impact of Imperfect Change Rules on Framework API 
      Evolution Identification: An Empirical Study},
   YEAR         = {2015},
   MONTH        = {August},
   NOTE         = {32 pages.},
   NUMBER       = {4},
   PAGES        = {1126--1158},
   VOLUME       = {20},
   EDITOR       = {Victor R. Basili and Lionel C. Briand},
   KEYWORDS     = {Topic: <b>Evolution patterns</b>, Venue: <b>EMSE</b>},
   PUBLISHER    = {Springer},
   URL          = {http://www.ptidej.net/publications/documents/EMSE14b.doc.pdf},
   ABSTRACT     = {Software frameworks keep evolving. It is often 
      time-consuming for developers to keep their client code up-to-date. 
      Not all frameworks have documentation about the upgrading process. 
      Many approaches have been proposed to ease the impact of 
      non-documented framework evolution on developers by identifying 
      change rules between two releases of a framework, but these change 
      rules are imperfect, \textit{i.e.}, not 100\% correct. To the best of 
      our knowledge, there is no empirical study to show the usefulness of 
      these imperfect change rules. Therefore, we design and conduct an 
      experiment to evaluate their impact. In the experiment, the subjects 
      must find the replacements of 21 missing methods in the new releases 
      of three open-source frameworks with the help of (1) all-correct, (2) 
      imperfect, and (3) no change rules. The statistical analysis results 
      show that the precision of the replacements found by the subjects 
      with the three sets of change rules are significantly different. The 
      precision with all-correct change rules is the highest while that 
      with no change rules is the lowest, while imperfect change rules give 
      a precision in between. The effect size of the difference between the 
      subjects with no and imperfect change rules is large and that between 
      the subjects with imperfect and correct change rules is moderate. The 
      results of this study show that the change rules generated by 
      framework API evolution approaches do help developers, even they are 
      not always correct. The imperfect change rules can be used by 
      developers upgrading their code when documentation is not available 
      or as a complement to partial documentation. The moderate difference 
      between results from subjects with imperfect and all-correct change 
      rules also suggests that improving precision of change rules will 
      still help developers.}
}

{"_id":"EenvYiqiaufhb8Pet","bibbaseid":"wu-serveaux-guhneuc-antoniol-theimpactofimperfectchangerulesonframeworkapievolutionidentificationanempiricalstudy-2015","downloads":0,"creationDate":"2018-01-17T20:29:42.218Z","title":"The Impact of Imperfect Change Rules on Framework API Evolution Identification: An Empirical Study","author_short":["Wu, W.","Serveaux, A.","Gu�h�neuc, Y.","Antoniol, G."],"year":2015,"bibtype":"article","biburl":"http://www.yann-gael.gueheneuc.net/Work/Publications/Biblio/complete-bibliography.bib","bibdata":{"bibtype":"article","type":"article","author":[{"firstnames":["Wei"],"propositions":[],"lastnames":["Wu"],"suffixes":[]},{"firstnames":["Adrien"],"propositions":[],"lastnames":["Serveaux"],"suffixes":[]},{"firstnames":["Yann-Ga�l"],"propositions":[],"lastnames":["Gu�h�neuc"],"suffixes":[]},{"firstnames":["Giuliano"],"propositions":[],"lastnames":["Antoniol"],"suffixes":[]}],"journal":"Empirical Software Engineering (EMSE)","title":"The Impact of Imperfect Change Rules on Framework API Evolution Identification: An Empirical Study","year":"2015","month":"August","note":"32 pages.","number":"4","pages":"1126–1158","volume":"20","editor":[{"firstnames":["Victor","R."],"propositions":[],"lastnames":["Basili"],"suffixes":[]},{"firstnames":["Lionel","C."],"propositions":[],"lastnames":["Briand"],"suffixes":[]}],"keywords":"Topic: <b>Evolution patterns</b>, Venue: <b>EMSE</b>","publisher":"Springer","url":"http://www.ptidej.net/publications/documents/EMSE14b.doc.pdf","abstract":"Software frameworks keep evolving. It is often time-consuming for developers to keep their client code up-to-date. Not all frameworks have documentation about the upgrading process. Many approaches have been proposed to ease the impact of non-documented framework evolution on developers by identifying change rules between two releases of a framework, but these change rules are imperfect, <i>i.e.</i>, not 100% correct. To the best of our knowledge, there is no empirical study to show the usefulness of these imperfect change rules. Therefore, we design and conduct an experiment to evaluate their impact. In the experiment, the subjects must find the replacements of 21 missing methods in the new releases of three open-source frameworks with the help of (1) all-correct, (2) imperfect, and (3) no change rules. The statistical analysis results show that the precision of the replacements found by the subjects with the three sets of change rules are significantly different. The precision with all-correct change rules is the highest while that with no change rules is the lowest, while imperfect change rules give a precision in between. The effect size of the difference between the subjects with no and imperfect change rules is large and that between the subjects with imperfect and correct change rules is moderate. The results of this study show that the change rules generated by framework API evolution approaches do help developers, even they are not always correct. The imperfect change rules can be used by developers upgrading their code when documentation is not available or as a complement to partial documentation. The moderate difference between results from subjects with imperfect and all-correct change rules also suggests that improving precision of change rules will still help developers.","bibtex":"@ARTICLE{Wu14-EMSE-EyeTrackingTraceability,\r\n AUTHOR = {Wei Wu and Adrien Serveaux and Yann-Ga�l Gu�h�neuc and \r\n Giuliano Antoniol},\r\n JOURNAL = {Empirical Software Engineering (EMSE)},\r\n TITLE = {The Impact of Imperfect Change Rules on Framework API \r\n Evolution Identification: An Empirical Study},\r\n YEAR = {2015},\r\n MONTH = {August},\r\n NOTE = {32 pages.},\r\n NUMBER = {4},\r\n PAGES = {1126--1158},\r\n VOLUME = {20},\r\n EDITOR = {Victor R. Basili and Lionel C. Briand},\r\n KEYWORDS = {Topic: <b>Evolution patterns</b>, Venue: <b>EMSE</b>},\r\n PUBLISHER = {Springer},\r\n URL = {http://www.ptidej.net/publications/documents/EMSE14b.doc.pdf},\r\n ABSTRACT = {Software frameworks keep evolving. It is often \r\n time-consuming for developers to keep their client code up-to-date. \r\n Not all frameworks have documentation about the upgrading process. \r\n Many approaches have been proposed to ease the impact of \r\n non-documented framework evolution on developers by identifying \r\n change rules between two releases of a framework, but these change \r\n rules are imperfect, \\textit{i.e.}, not 100\\% correct. To the best of \r\n our knowledge, there is no empirical study to show the usefulness of \r\n these imperfect change rules. Therefore, we design and conduct an \r\n experiment to evaluate their impact. In the experiment, the subjects \r\n must find the replacements of 21 missing methods in the new releases \r\n of three open-source frameworks with the help of (1) all-correct, (2) \r\n imperfect, and (3) no change rules. The statistical analysis results \r\n show that the precision of the replacements found by the subjects \r\n with the three sets of change rules are significantly different. The \r\n precision with all-correct change rules is the highest while that \r\n with no change rules is the lowest, while imperfect change rules give \r\n a precision in between. The effect size of the difference between the \r\n subjects with no and imperfect change rules is large and that between \r\n the subjects with imperfect and correct change rules is moderate. The \r\n results of this study show that the change rules generated by \r\n framework API evolution approaches do help developers, even they are \r\n not always correct. The imperfect change rules can be used by \r\n developers upgrading their code when documentation is not available \r\n or as a complement to partial documentation. The moderate difference \r\n between results from subjects with imperfect and all-correct change \r\n rules also suggests that improving precision of change rules will \r\n still help developers.}\r\n}\r\n\r\n","author_short":["Wu, W.","Serveaux, A.","Gu�h�neuc, Y.","Antoniol, G."],"editor_short":["Basili, V. R.","Briand, L. C."],"key":"Wu14-EMSE-EyeTrackingTraceability","id":"Wu14-EMSE-EyeTrackingTraceability","bibbaseid":"wu-serveaux-guhneuc-antoniol-theimpactofimperfectchangerulesonframeworkapievolutionidentificationanempiricalstudy-2015","role":"author","urls":{"Paper":"http://www.ptidej.net/publications/documents/EMSE14b.doc.pdf"},"keyword":["Topic: <b>Evolution patterns</b>","Venue: <b>EMSE</b>"],"metadata":{"authorlinks":{"gu�h�neuc, y":"https://bibbase.org/show?bib=http%3A%2F%2Fwww.yann-gael.gueheneuc.net%2FWork%2FPublications%2FBiblio%2Fcomplete-bibliography.bib&msg=embed","guéhéneuc, y":"http://www.yann-gael.gueheneuc.net/"}}},"search_terms":["impact","imperfect","change","rules","framework","api","evolution","identification","empirical","study","wu","serveaux","gu�h�neuc","antoniol"],"keywords":["topic: <b>evolution patterns</b>","venue: <b>emse</b>"],"authorIDs":["AfJhKcg96muyPdu7S","xkviMnkrGBneANvMr"],"dataSources":["Sed98LbBeGaXxenrM","8vn5MSGYWB4fAx9Z4"]}