@ARTICLE{Jaafar14-ECEASST-AntipatternRelationships,
   AUTHOR       = {Fehmi Jaafar and Yann-Ga�l Gu�h�neuc and Sylvie Hamel and 
      Foutse Khomh},
   JOURNAL      = {Electronic Communications of the EASST (ECEASST)},
   TITLE        = {Analysing Anti-patterns Static Relationships with Design 
      Patterns},
   YEAR         = {2014},
   MONTH        = {August},
   NOTE         = {26 pages.},
   OPTNUMBER    = {},
   OPTPAGES     = {},
   VOLUME       = {59},
   EDITOR       = {Aminata Saban� and Wei Wu and Tiziana Margaria and 
      Julia Padberg and Gabriele Taentzer},
   KEYWORDS     = {Topic: <b>Code and design smells</b>, 
      Venue: <b>ECEASST</b>},
   PUBLISHER    = {European Association of Software Science and Technology},
   URL          = {http://www.ptidej.net/publications/documents/ECEASST14.doc.pdf},
   ABSTRACT     = {Anti-patterns are motifs that are usually thought to be 
      good solutions to some design or implementation problems, but 
      back-fires badly when applied. Previous studies have reported that 
      anti-patterns make object oriented systems hard to maintain. 
      Anti-patterns motifs usually have dependencies with other classes in 
      the system. In this paper, we propose to analyse these dependencies 
      (with in particular design patterns) in order to understand how 
      developers can maintain programs containing anti-patterns. To the 
      best of our knowledge, no substantial investigation of anti-pattern 
      dependencies with design patterns has been done before. This paper 
      presents the results of a study that we performed on three different 
      systems, ArgoUML, JFreeChart, and XercesJ, written in Java, and of 
      size ranges from 1,191 to 3,325 classes, to analyse the static 
      relationships between anti-patterns and design patterns. We found 
      that these relationships (1) exist, but (2) are temporary and (3) 
      classes participating in such relationships are more change-prone but 
      less fault-prone than other anti-pattern classes.}
}

{"_id":"E8cnRLn3PoCmGbbia","bibbaseid":"jaafar-guhneuc-hamel-khomh-analysingantipatternsstaticrelationshipswithdesignpatterns-2014","downloads":0,"creationDate":"2018-01-17T20:29:42.267Z","title":"Analysing Anti-patterns Static Relationships with Design Patterns","author_short":["Jaafar, F.","Gu�h�neuc, Y.","Hamel, S.","Khomh, F."],"year":2014,"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":[]}],"journal":"Electronic Communications of the EASST (ECEASST)","title":"Analysing Anti-patterns Static Relationships with Design Patterns","year":"2014","month":"August","note":"26 pages.","optnumber":"","optpages":"","volume":"59","editor":[{"firstnames":["Aminata"],"propositions":[],"lastnames":["Saban�"],"suffixes":[]},{"firstnames":["Wei"],"propositions":[],"lastnames":["Wu"],"suffixes":[]},{"firstnames":["Tiziana"],"propositions":[],"lastnames":["Margaria"],"suffixes":[]},{"firstnames":["Julia"],"propositions":[],"lastnames":["Padberg"],"suffixes":[]},{"firstnames":["Gabriele"],"propositions":[],"lastnames":["Taentzer"],"suffixes":[]}],"keywords":"Topic: <b>Code and design smells</b>, Venue: <b>ECEASST</b>","publisher":"European Association of Software Science and Technology","url":"http://www.ptidej.net/publications/documents/ECEASST14.doc.pdf","abstract":"Anti-patterns are motifs that are usually thought to be good solutions to some design or implementation problems, but back-fires badly when applied. Previous studies have reported that anti-patterns make object oriented systems hard to maintain. Anti-patterns motifs usually have dependencies with other classes in the system. In this paper, we propose to analyse these dependencies (with in particular design patterns) in order to understand how developers can maintain programs containing anti-patterns. To the best of our knowledge, no substantial investigation of anti-pattern dependencies with design patterns has been done before. This paper presents the results of a study that we performed on three different systems, ArgoUML, JFreeChart, and XercesJ, written in Java, and of size ranges from 1,191 to 3,325 classes, to analyse the static relationships between anti-patterns and design patterns. We found that these relationships (1) exist, but (2) are temporary and (3) classes participating in such relationships are more change-prone but less fault-prone than other anti-pattern classes.","bibtex":"@ARTICLE{Jaafar14-ECEASST-AntipatternRelationships,\r\n AUTHOR = {Fehmi Jaafar and Yann-Ga�l Gu�h�neuc and Sylvie Hamel and \r\n Foutse Khomh},\r\n JOURNAL = {Electronic Communications of the EASST (ECEASST)},\r\n TITLE = {Analysing Anti-patterns Static Relationships with Design \r\n Patterns},\r\n YEAR = {2014},\r\n MONTH = {August},\r\n NOTE = {26 pages.},\r\n OPTNUMBER = {},\r\n OPTPAGES = {},\r\n VOLUME = {59},\r\n EDITOR = {Aminata Saban� and Wei Wu and Tiziana Margaria and \r\n Julia Padberg and Gabriele Taentzer},\r\n KEYWORDS = {Topic: <b>Code and design smells</b>, \r\n Venue: <b>ECEASST</b>},\r\n PUBLISHER = {European Association of Software Science and Technology},\r\n URL = {http://www.ptidej.net/publications/documents/ECEASST14.doc.pdf},\r\n ABSTRACT = {Anti-patterns are motifs that are usually thought to be \r\n good solutions to some design or implementation problems, but \r\n back-fires badly when applied. Previous studies have reported that \r\n anti-patterns make object oriented systems hard to maintain. \r\n Anti-patterns motifs usually have dependencies with other classes in \r\n the system. In this paper, we propose to analyse these dependencies \r\n (with in particular design patterns) in order to understand how \r\n developers can maintain programs containing anti-patterns. To the \r\n best of our knowledge, no substantial investigation of anti-pattern \r\n dependencies with design patterns has been done before. This paper \r\n presents the results of a study that we performed on three different \r\n systems, ArgoUML, JFreeChart, and XercesJ, written in Java, and of \r\n size ranges from 1,191 to 3,325 classes, to analyse the static \r\n relationships between anti-patterns and design patterns. We found \r\n that these relationships (1) exist, but (2) are temporary and (3) \r\n classes participating in such relationships are more change-prone but \r\n less fault-prone than other anti-pattern classes.}\r\n}\r\n\r\n","author_short":["Jaafar, F.","Gu�h�neuc, Y.","Hamel, S.","Khomh, F."],"editor_short":["Saban�, A.","Wu, W.","Margaria, T.","Padberg, J.","Taentzer, G."],"key":"Jaafar14-ECEASST-AntipatternRelationships","id":"Jaafar14-ECEASST-AntipatternRelationships","bibbaseid":"jaafar-guhneuc-hamel-khomh-analysingantipatternsstaticrelationshipswithdesignpatterns-2014","role":"author","urls":{"Paper":"http://www.ptidej.net/publications/documents/ECEASST14.doc.pdf"},"keyword":["Topic: <b>Code and design smells</b>","Venue: <b>ECEASST</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":"https://bibbase.org/show?bib=http://www.yann-gael.gueheneuc.net/Work/BibBase/guehene%20(automatically%20cleaned).bib"}},"downloads":0},"search_terms":["analysing","anti","patterns","static","relationships","design","patterns","jaafar","gu�h�neuc","hamel","khomh"],"keywords":["topic: <b>code and design smells</b>","venue: <b>eceasst</b>"],"authorIDs":["AfJhKcg96muyPdu7S","xkviMnkrGBneANvMr"],"dataSources":["Sed98LbBeGaXxenrM","8vn5MSGYWB4fAx9Z4"]}