An Exploratory Study of the Impact of Antipatterns on Class Change- and Fault-Proneness

An Exploratory Study of the Impact of Antipatterns on Class Change- and Fault-Proneness. Khomh, F., Di Penta, M., Gu�h�neuc, Y., & Antoniol, G. Empirical Software Engineering (EMSE), 17(3):243–275, Springer, June, 2012. 27 pages.

Paper abstract bibtex

Context: Antipatterns are poor design choices that are conjectured to make object-oriented systems harder to maintain.
Aim: We investigate the impact of antipatterns on classes in object-oriented systems by studying the relation between the presence of antipatterns and the change- and fault-proneness of the classes.
Method: We detect 13 antipatterns in 54 releases of ArgoUML, Eclipse, Mylyn, and Rhino, and analyse (1) to what extent classes participating in antipatterns have higher odds to change or to be subject to fault-fixing than other classes, (2) to what extent these odds (if higher) are due to the sizes of the classes or to the presence of antipatterns, and (3) what kinds of changes affect classes participating in antipatterns.
Results: We show that, in almost all releases of the four systems, classes participating in antipatterns are more change- and fault-prone than others. We also show that size alone cannot explain the higher odds of classes with antipatterns to underwent a (fault-fixing) change than other classes. Finally, we show that structural changes affect more classes with antipatterns than others. We provide qualitative explanations of the increase of change- and fault-proneness in classes participating in antipatterns using release notes and bug reports.
Conclusions: The obtained results justify a posteriori previous work on the specification and detection of antipatterns and could help to better focus quality assurance and testing activities.

@ARTICLE{Khomh11-EMSE-AntiPatternsImpact,
   AUTHOR       = {Foutse Khomh and Di Penta, Massimiliano and 
      Yann-Ga�l Gu�h�neuc and Giuliano Antoniol},
   JOURNAL      = {Empirical Software Engineering (EMSE)},
   TITLE        = {An Exploratory Study of the Impact of Antipatterns on 
      Class Change- and Fault-Proneness},
   YEAR         = {2012},
   MONTH        = {June},
   NOTE         = {27 pages.},
   NUMBER       = {3},
   PAGES        = {243&ndash;275},
   VOLUME       = {17},
   EDITOR       = {Victor R. Basili and Lionel C. Briand},
   KEYWORDS     = {Topic: <b>Code and design smells</b>, 
      Rubrique : <b>mauvaises pratiques</b>, Journal: <b>EMSE</b>},
   PUBLISHER    = {Springer},
   URL          = {http://www.ptidej.net/publications/documents/EMSE11b.doc.pdf},
   ABSTRACT     = {Context: Antipatterns are poor design choices that are 
      conjectured to make object-oriented systems harder to maintain. 
      <br/>Aim: We investigate the impact of antipatterns on classes in 
      object-oriented systems by studying the relation between the presence 
      of antipatterns and the change- and fault-proneness of the classes. 
      <br/>Method: We detect 13 antipatterns in 54 releases of ArgoUML, 
      Eclipse, Mylyn, and Rhino, and analyse (1) to what extent classes 
      participating in antipatterns have higher odds to change or to be 
      subject to fault-fixing than other classes, (2) to what extent these 
      odds (if higher) are due to the sizes of the classes or to the 
      presence of antipatterns, and (3) what kinds of changes affect 
      classes participating in antipatterns. <br/>Results: We show that, in 
      almost all releases of the four systems, classes participating in 
      antipatterns are more change- and fault-prone than others. We also 
      show that size alone cannot explain the higher odds of classes with 
      antipatterns to underwent a (fault-fixing) change than other classes. 
      Finally, we show that structural changes affect more classes with 
      antipatterns than others. We provide qualitative explanations of the 
      increase of change- and fault-proneness in classes participating in 
      antipatterns using release notes and bug reports. <br/>Conclusions: 
      The obtained results justify a posteriori previous work on the 
      specification and detection of antipatterns and could help to better 
      focus quality assurance and testing activities.}
}

Downloads: 0

{"_id":"277v7fK9hJ82TjSCB","bibbaseid":"khomh-dipenta-guhneuc-antoniol-anexploratorystudyoftheimpactofantipatternsonclasschangeandfaultproneness-2012","downloads":0,"creationDate":"2018-01-17T20:29:42.366Z","title":"An Exploratory Study of the Impact of Antipatterns on Class Change- and Fault-Proneness","author_short":["Khomh, F.","Di Penta, M.","Gu�h�neuc, Y.","Antoniol, G."],"year":2012,"bibtype":"article","biburl":"http://www.yann-gael.gueheneuc.net/Work/Publications/Biblio/complete-bibliography.bib","bibdata":{"bibtype":"article","type":"article","author":[{"firstnames":["Foutse"],"propositions":[],"lastnames":["Khomh"],"suffixes":[]},{"propositions":[],"lastnames":["Di","Penta"],"firstnames":["Massimiliano"],"suffixes":[]},{"firstnames":["Yann-Ga�l"],"propositions":[],"lastnames":["Gu�h�neuc"],"suffixes":[]},{"firstnames":["Giuliano"],"propositions":[],"lastnames":["Antoniol"],"suffixes":[]}],"journal":"Empirical Software Engineering (EMSE)","title":"An Exploratory Study of the Impact of Antipatterns on Class Change- and Fault-Proneness","year":"2012","month":"June","note":"27 pages.","number":"3","pages":"243–275","volume":"17","editor":[{"firstnames":["Victor","R."],"propositions":[],"lastnames":["Basili"],"suffixes":[]},{"firstnames":["Lionel","C."],"propositions":[],"lastnames":["Briand"],"suffixes":[]}],"keywords":"Topic: Code and design smells, Rubrique : mauvaises pratiques, Journal: EMSE","publisher":"Springer","url":"http://www.ptidej.net/publications/documents/EMSE11b.doc.pdf","abstract":"Context: Antipatterns are poor design choices that are conjectured to make object-oriented systems harder to maintain. Aim: We investigate the impact of antipatterns on classes in object-oriented systems by studying the relation between the presence of antipatterns and the change- and fault-proneness of the classes. Method: We detect 13 antipatterns in 54 releases of ArgoUML, Eclipse, Mylyn, and Rhino, and analyse (1) to what extent classes participating in antipatterns have higher odds to change or to be subject to fault-fixing than other classes, (2) to what extent these odds (if higher) are due to the sizes of the classes or to the presence of antipatterns, and (3) what kinds of changes affect classes participating in antipatterns. Results: We show that, in almost all releases of the four systems, classes participating in antipatterns are more change- and fault-prone than others. We also show that size alone cannot explain the higher odds of classes with antipatterns to underwent a (fault-fixing) change than other classes. Finally, we show that structural changes affect more classes with antipatterns than others. We provide qualitative explanations of the increase of change- and fault-proneness in classes participating in antipatterns using release notes and bug reports. Conclusions: The obtained results justify a posteriori previous work on the specification and detection of antipatterns and could help to better focus quality assurance and testing activities.","bibtex":"@ARTICLE{Khomh11-EMSE-AntiPatternsImpact,\r\n AUTHOR = {Foutse Khomh and Di Penta, Massimiliano and \r\n Yann-Ga�l Gu�h�neuc and Giuliano Antoniol},\r\n JOURNAL = {Empirical Software Engineering (EMSE)},\r\n TITLE = {An Exploratory Study of the Impact of Antipatterns on \r\n Class Change- and Fault-Proneness},\r\n YEAR = {2012},\r\n MONTH = {June},\r\n NOTE = {27 pages.},\r\n NUMBER = {3},\r\n PAGES = {243–275},\r\n VOLUME = {17},\r\n EDITOR = {Victor R. Basili and Lionel C. Briand},\r\n KEYWORDS = {Topic: Code and design smells, \r\n Rubrique : mauvaises pratiques, Journal: EMSE},\r\n PUBLISHER = {Springer},\r\n URL = {http://www.ptidej.net/publications/documents/EMSE11b.doc.pdf},\r\n ABSTRACT = {Context: Antipatterns are poor design choices that are \r\n conjectured to make object-oriented systems harder to maintain. \r\n Aim: We investigate the impact of antipatterns on classes in \r\n object-oriented systems by studying the relation between the presence \r\n of antipatterns and the change- and fault-proneness of the classes. \r\n Method: We detect 13 antipatterns in 54 releases of ArgoUML, \r\n Eclipse, Mylyn, and Rhino, and analyse (1) to what extent classes \r\n participating in antipatterns have higher odds to change or to be \r\n subject to fault-fixing than other classes, (2) to what extent these \r\n odds (if higher) are due to the sizes of the classes or to the \r\n presence of antipatterns, and (3) what kinds of changes affect \r\n classes participating in antipatterns. Results: We show that, in \r\n almost all releases of the four systems, classes participating in \r\n antipatterns are more change- and fault-prone than others. We also \r\n show that size alone cannot explain the higher odds of classes with \r\n antipatterns to underwent a (fault-fixing) change than other classes. \r\n Finally, we show that structural changes affect more classes with \r\n antipatterns than others. We provide qualitative explanations of the \r\n increase of change- and fault-proneness in classes participating in \r\n antipatterns using release notes and bug reports. Conclusions: \r\n The obtained results justify a posteriori previous work on the \r\n specification and detection of antipatterns and could help to better \r\n focus quality assurance and testing activities.}\r\n}\r\n\r\n","author_short":["Khomh, F.","Di Penta, M.","Gu�h�neuc, Y.","Antoniol, G."],"editor_short":["Basili, V. R.","Briand, L. C."],"key":"Khomh11-EMSE-AntiPatternsImpact","id":"Khomh11-EMSE-AntiPatternsImpact","bibbaseid":"khomh-dipenta-guhneuc-antoniol-anexploratorystudyoftheimpactofantipatternsonclasschangeandfaultproneness-2012","role":"author","urls":{"Paper":"http://www.ptidej.net/publications/documents/EMSE11b.doc.pdf"},"keyword":["Topic: Code and design smells","Rubrique : mauvaises pratiques","Journal: EMSE"],"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":"https://bibbase.org/show?bib=http://www.yann-gael.gueheneuc.net/Work/BibBase/guehene%20(automatically%20cleaned).bib"}},"downloads":0},"search_terms":["exploratory","study","impact","antipatterns","class","change","fault","proneness","khomh","di penta","gu�h�neuc","antoniol"],"keywords":["topic: code and design smells","rubrique : mauvaises pratiques","journal: emse"],"authorIDs":["AfJhKcg96muyPdu7S","xkviMnkrGBneANvMr"],"dataSources":["Sed98LbBeGaXxenrM","8vn5MSGYWB4fAx9Z4"]}