@ARTICLE{Jaafar14-EMSE-PatternDependencies,
   AUTHOR       = {Fehmi Jaafar and Yann-Ga�l Gu�h�neuc and Sylvie Hamel and 
      Foutse Khomh and Mohammad Zulkernine},
   JOURNAL      = {Journal of Empirical Software Engineering (EMSE)},
   TITLE        = {Evaluating the Impact of Design Pattern and Anti-pattern 
      Dependencies on Changes and Faults},
   YEAR         = {2016},
   MONTH        = {February},
   NOTE         = {35 pages.},
   NUMBER       = {3},
   PAGES        = {896--931},
   VOLUME       = {21},
   EDITOR       = {Di Penta, Massimiliano and Rocco Oliveto and 
      Romain Robbes},
   KEYWORDS     = {Topic: <b>Code and design smells</b>, 
      Topic: <b>Design patterns</b>, Venue: <b>EMSE</b>},
   PUBLISHER    = {Springer},
   URL          = {http://www.ptidej.net/publications/documents/EMSE16b.doc.pdf},
   ABSTRACT     = {On the one hand, design patterns are solutions to 
      recurring design problems, aimed at increasing reuse, flexibility, 
      and maintainability. However, numerous previous work found that some 
      patterns, such as the Observer and Singleton, are correlated with 
      large code structures and argued that they are likely to be more 
      fault prone. On the other hand, anti-patterns describe poor solutions 
      to design and implementation problems that highlight weaknesses in 
      the design of software systems and that may slow down maintenance and 
      increase the risk of faults. They have been found to negatively 
      impact change and fault-proneness. Classes participating in design 
      patterns and anti-patterns have dependencies with other classes, 
      \eg{} static and co-change dependencies, that may propagate problems 
      to other classes. We investigate the impact of such dependencies in 
      object-oriented systems by studying the relations between the 
      presence of static and co-change dependencies and (1) the 
      fault-proneness, (2) the types of changes, and (3) the types of 
      faults that these classes undergo. We analyze six design patterns and 
      10 anti-patterns in 39 releases of ArgoUML, JFreeChart, and XercesJ, 
      and investigate to what extent classes having dependencies with 
      design patterns or anti-patterns have higher odds to faults than 
      other classes. We show that in almost all releases of the three 
      systems, classes having dependencies with anti-patterns are more 
      fault-prone than others while it is not always true for classes with 
      dependencies with design patterns. We also observe that structural 
      changes are the most common changes impacting classes having 
      dependencies with anti-patterns. Software developers could use this 
      knowledge about the impact of design pattern and anti-pattern 
      dependencies to better focus their testing and reviewing activities 
      towards the most risky classes and to propagate changes adequately.}
}

{"_id":"2svRn7jbFsSGfutre","bibbaseid":"jaafar-guhneuc-hamel-khomh-zulkernine-evaluatingtheimpactofdesignpatternandantipatterndependenciesonchangesandfaults-2016","downloads":0,"creationDate":"2018-01-17T20:29:42.179Z","title":"Evaluating the Impact of Design Pattern and Anti-pattern Dependencies on Changes and Faults","author_short":["Jaafar, F.","Gu�h�neuc, Y.","Hamel, S.","Khomh, F.","Zulkernine, M."],"year":2016,"bibtype":"article","biburl":"http://www.yann-gael.gueheneuc.net/Work/Publications/Biblio/complete-bibliography.bib","bibdata":{"bibtype":"article","type":"article","author":[{"firstnames":["Fehmi"],"propositions":[],"lastnames":["Jaafar"],"suffixes":[]},{"firstnames":["Yann-Ga�l"],"propositions":[],"lastnames":["Gu�h�neuc"],"suffixes":[]},{"firstnames":["Sylvie"],"propositions":[],"lastnames":["Hamel"],"suffixes":[]},{"firstnames":["Foutse"],"propositions":[],"lastnames":["Khomh"],"suffixes":[]},{"firstnames":["Mohammad"],"propositions":[],"lastnames":["Zulkernine"],"suffixes":[]}],"journal":"Journal of Empirical Software Engineering (EMSE)","title":"Evaluating the Impact of Design Pattern and Anti-pattern Dependencies on Changes and Faults","year":"2016","month":"February","note":"35 pages.","number":"3","pages":"896–931","volume":"21","editor":[{"propositions":[],"lastnames":["Di","Penta"],"firstnames":["Massimiliano"],"suffixes":[]},{"firstnames":["Rocco"],"propositions":[],"lastnames":["Oliveto"],"suffixes":[]},{"firstnames":["Romain"],"propositions":[],"lastnames":["Robbes"],"suffixes":[]}],"keywords":"Topic: <b>Code and design smells</b>, Topic: <b>Design patterns</b>, Venue: <b>EMSE</b>","publisher":"Springer","url":"http://www.ptidej.net/publications/documents/EMSE16b.doc.pdf","abstract":"On the one hand, design patterns are solutions to recurring design problems, aimed at increasing reuse, flexibility, and maintainability. However, numerous previous work found that some patterns, such as the Observer and Singleton, are correlated with large code structures and argued that they are likely to be more fault prone. On the other hand, anti-patterns describe poor solutions to design and implementation problems that highlight weaknesses in the design of software systems and that may slow down maintenance and increase the risk of faults. They have been found to negatively impact change and fault-proneness. Classes participating in design patterns and anti-patterns have dependencies with other classes, \\eg static and co-change dependencies, that may propagate problems to other classes. We investigate the impact of such dependencies in object-oriented systems by studying the relations between the presence of static and co-change dependencies and (1) the fault-proneness, (2) the types of changes, and (3) the types of faults that these classes undergo. We analyze six design patterns and 10 anti-patterns in 39 releases of ArgoUML, JFreeChart, and XercesJ, and investigate to what extent classes having dependencies with design patterns or anti-patterns have higher odds to faults than other classes. We show that in almost all releases of the three systems, classes having dependencies with anti-patterns are more fault-prone than others while it is not always true for classes with dependencies with design patterns. We also observe that structural changes are the most common changes impacting classes having dependencies with anti-patterns. Software developers could use this knowledge about the impact of design pattern and anti-pattern dependencies to better focus their testing and reviewing activities towards the most risky classes and to propagate changes adequately.","bibtex":"@ARTICLE{Jaafar14-EMSE-PatternDependencies,\r\n AUTHOR = {Fehmi Jaafar and Yann-Ga�l Gu�h�neuc and Sylvie Hamel and \r\n Foutse Khomh and Mohammad Zulkernine},\r\n JOURNAL = {Journal of Empirical Software Engineering (EMSE)},\r\n TITLE = {Evaluating the Impact of Design Pattern and Anti-pattern \r\n Dependencies on Changes and Faults},\r\n YEAR = {2016},\r\n MONTH = {February},\r\n NOTE = {35 pages.},\r\n NUMBER = {3},\r\n PAGES = {896--931},\r\n VOLUME = {21},\r\n EDITOR = {Di Penta, Massimiliano and Rocco Oliveto and \r\n Romain Robbes},\r\n KEYWORDS = {Topic: <b>Code and design smells</b>, \r\n Topic: <b>Design patterns</b>, Venue: <b>EMSE</b>},\r\n PUBLISHER = {Springer},\r\n URL = {http://www.ptidej.net/publications/documents/EMSE16b.doc.pdf},\r\n ABSTRACT = {On the one hand, design patterns are solutions to \r\n recurring design problems, aimed at increasing reuse, flexibility, \r\n and maintainability. However, numerous previous work found that some \r\n patterns, such as the Observer and Singleton, are correlated with \r\n large code structures and argued that they are likely to be more \r\n fault prone. On the other hand, anti-patterns describe poor solutions \r\n to design and implementation problems that highlight weaknesses in \r\n the design of software systems and that may slow down maintenance and \r\n increase the risk of faults. They have been found to negatively \r\n impact change and fault-proneness. Classes participating in design \r\n patterns and anti-patterns have dependencies with other classes, \r\n \\eg{} static and co-change dependencies, that may propagate problems \r\n to other classes. We investigate the impact of such dependencies in \r\n object-oriented systems by studying the relations between the \r\n presence of static and co-change dependencies and (1) the \r\n fault-proneness, (2) the types of changes, and (3) the types of \r\n faults that these classes undergo. We analyze six design patterns and \r\n 10 anti-patterns in 39 releases of ArgoUML, JFreeChart, and XercesJ, \r\n and investigate to what extent classes having dependencies with \r\n design patterns or anti-patterns have higher odds to faults than \r\n other classes. We show that in almost all releases of the three \r\n systems, classes having dependencies with anti-patterns are more \r\n fault-prone than others while it is not always true for classes with \r\n dependencies with design patterns. We also observe that structural \r\n changes are the most common changes impacting classes having \r\n dependencies with anti-patterns. Software developers could use this \r\n knowledge about the impact of design pattern and anti-pattern \r\n dependencies to better focus their testing and reviewing activities \r\n towards the most risky classes and to propagate changes adequately.}\r\n}\r\n\r\n","author_short":["Jaafar, F.","Gu�h�neuc, Y.","Hamel, S.","Khomh, F.","Zulkernine, M."],"editor_short":["Di Penta, M.","Oliveto, R.","Robbes, R."],"key":"Jaafar14-EMSE-PatternDependencies","id":"Jaafar14-EMSE-PatternDependencies","bibbaseid":"jaafar-guhneuc-hamel-khomh-zulkernine-evaluatingtheimpactofdesignpatternandantipatterndependenciesonchangesandfaults-2016","role":"author","urls":{"Paper":"http://www.ptidej.net/publications/documents/EMSE16b.doc.pdf"},"keyword":["Topic: <b>Code and design smells</b>","Topic: <b>Design 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":["evaluating","impact","design","pattern","anti","pattern","dependencies","changes","faults","jaafar","gu�h�neuc","hamel","khomh","zulkernine"],"keywords":["topic: <b>code and design smells</b>","topic: <b>design patterns</b>","venue: <b>emse</b>"],"authorIDs":["AfJhKcg96muyPdu7S","xkviMnkrGBneANvMr"],"dataSources":["Sed98LbBeGaXxenrM","8vn5MSGYWB4fAx9Z4"]}