@INPROCEEDINGS{Abidi19-EuroPLoP-APsforMLS,
   AUTHOR       = {Mouna Abidi and Foutse Khomh and Yann-Ga�l Gu�h�neuc},
   BOOKTITLE    = {Proceedings of the 24<sup>th</sup> European Conference on Pattern Languages of Programs (EuroPLoP)},
   TITLE        = {Anti-patterns for Multi-language Systems},
   YEAR         = {2019},
   OPTADDRESS   = {},
   OPTCROSSREF  = {},
   EDITOR       = {Taichi Isaku},
   MONTH        = {July},
   NOTE         = {14 pages.},
   OPTNUMBER    = {},
   OPTORGANIZATION = {},
   PAGES        = {1--14},
   PUBLISHER    = {ACM Press},
   OPTSERIES    = {},
   OPTVOLUME    = {},
   KEYWORDS     = {Topic: <b>Code and design smells</b>, 
      Venue: <c>PLoP</c>},
   URL          = {http://www.ptidej.net/publications/documents/EuroPLoP19a.doc.pdf},
   ABSTRACT     = {Multi-language systems are common nowadays because most 
      of the systems are developed using components written in different 
      programming languages. These systems could arise from three different 
      reasons: (1) to leverage the strengths and take benefits of each 
      language, (2) to reduce the cost by reusing code written in other 
      languages, (3) to include and accommodate legacy code. However, they 
      also introduce additional challenges, including the increase in the 
      complexity and the need for proper interfaces and interactions 
      between the different languages. To address these challenges, the 
      software-engineering research community, as well as the industry, 
      should describe and provide common guidelines, idioms, and patterns 
      to support the development, maintenance, and evolution of these 
      systems. These patterns are an effective means of improving the 
      quality of multi-language systems. They capture good practices to 
      adopt and bad practices to avoid. In order to help to improve the 
      quality of multi-language systems, we analysed open-source systems, 
      developers' documentation, bug reports, and programming language 
      specifications to extract bad practices of multi-language systems 
      usage. We encoded and cataloged these practices in the form of design 
      anti-patterns. We report here six anti-patterns. These results could 
      help not only researchers but also professional developers 
      considering the use of more than one programming language.}
}

{"_id":"FF24PEzz6ZbDidrsf","bibbaseid":"abidi-khomh-guhneuc-antipatternsformultilanguagesystems-2019","author_short":["Abidi, M.","Khomh, F.","Gu�h�neuc, Y."],"bibdata":{"bibtype":"inproceedings","type":"inproceedings","author":[{"firstnames":["Mouna"],"propositions":[],"lastnames":["Abidi"],"suffixes":[]},{"firstnames":["Foutse"],"propositions":[],"lastnames":["Khomh"],"suffixes":[]},{"firstnames":["Yann-Ga�l"],"propositions":[],"lastnames":["Gu�h�neuc"],"suffixes":[]}],"booktitle":"Proceedings of the 24^th European Conference on Pattern Languages of Programs (EuroPLoP)","title":"Anti-patterns for Multi-language Systems","year":"2019","optaddress":"","optcrossref":"","editor":[{"firstnames":["Taichi"],"propositions":[],"lastnames":["Isaku"],"suffixes":[]}],"month":"July","note":"14 pages.","optnumber":"","optorganization":"","pages":"1–14","publisher":"ACM Press","optseries":"","optvolume":"","keywords":"Topic: <b>Code and design smells</b>, Venue: <c>PLoP</c>","url":"http://www.ptidej.net/publications/documents/EuroPLoP19a.doc.pdf","abstract":"Multi-language systems are common nowadays because most of the systems are developed using components written in different programming languages. These systems could arise from three different reasons: (1) to leverage the strengths and take benefits of each language, (2) to reduce the cost by reusing code written in other languages, (3) to include and accommodate legacy code. However, they also introduce additional challenges, including the increase in the complexity and the need for proper interfaces and interactions between the different languages. To address these challenges, the software-engineering research community, as well as the industry, should describe and provide common guidelines, idioms, and patterns to support the development, maintenance, and evolution of these systems. These patterns are an effective means of improving the quality of multi-language systems. They capture good practices to adopt and bad practices to avoid. In order to help to improve the quality of multi-language systems, we analysed open-source systems, developers' documentation, bug reports, and programming language specifications to extract bad practices of multi-language systems usage. We encoded and cataloged these practices in the form of design anti-patterns. We report here six anti-patterns. These results could help not only researchers but also professional developers considering the use of more than one programming language.","bibtex":"@INPROCEEDINGS{Abidi19-EuroPLoP-APsforMLS,\r\n AUTHOR = {Mouna Abidi and Foutse Khomh and Yann-Ga�l Gu�h�neuc},\r\n BOOKTITLE = {Proceedings of the 24^th European Conference on Pattern Languages of Programs (EuroPLoP)},\r\n TITLE = {Anti-patterns for Multi-language Systems},\r\n YEAR = {2019},\r\n OPTADDRESS = {},\r\n OPTCROSSREF = {},\r\n EDITOR = {Taichi Isaku},\r\n MONTH = {July},\r\n NOTE = {14 pages.},\r\n OPTNUMBER = {},\r\n OPTORGANIZATION = {},\r\n PAGES = {1--14},\r\n PUBLISHER = {ACM Press},\r\n OPTSERIES = {},\r\n OPTVOLUME = {},\r\n KEYWORDS = {Topic: <b>Code and design smells</b>, \r\n Venue: <c>PLoP</c>},\r\n URL = {http://www.ptidej.net/publications/documents/EuroPLoP19a.doc.pdf},\r\n ABSTRACT = {Multi-language systems are common nowadays because most \r\n of the systems are developed using components written in different \r\n programming languages. These systems could arise from three different \r\n reasons: (1) to leverage the strengths and take benefits of each \r\n language, (2) to reduce the cost by reusing code written in other \r\n languages, (3) to include and accommodate legacy code. However, they \r\n also introduce additional challenges, including the increase in the \r\n complexity and the need for proper interfaces and interactions \r\n between the different languages. To address these challenges, the \r\n software-engineering research community, as well as the industry, \r\n should describe and provide common guidelines, idioms, and patterns \r\n to support the development, maintenance, and evolution of these \r\n systems. These patterns are an effective means of improving the \r\n quality of multi-language systems. They capture good practices to \r\n adopt and bad practices to avoid. In order to help to improve the \r\n quality of multi-language systems, we analysed open-source systems, \r\n developers' documentation, bug reports, and programming language \r\n specifications to extract bad practices of multi-language systems \r\n usage. We encoded and cataloged these practices in the form of design \r\n anti-patterns. We report here six anti-patterns. These results could \r\n help not only researchers but also professional developers \r\n considering the use of more than one programming language.}\r\n}\r\n\r\n","author_short":["Abidi, M.","Khomh, F.","Gu�h�neuc, Y."],"editor_short":["Isaku, T."],"key":"Abidi19-EuroPLoP-APsforMLS","id":"Abidi19-EuroPLoP-APsforMLS","bibbaseid":"abidi-khomh-guhneuc-antipatternsformultilanguagesystems-2019","role":"author","urls":{"Paper":"http://www.ptidej.net/publications/documents/EuroPLoP19a.doc.pdf"},"keyword":["Topic: <b>Code and design smells</b>","Venue: <c>PLoP</c>"],"metadata":{"authorlinks":{}}},"bibtype":"inproceedings","biburl":"http://www.yann-gael.gueheneuc.net/Work/Publications/Biblio/complete-bibliography.bib","dataSources":["8vn5MSGYWB4fAx9Z4"],"keywords":["topic: <b>code and design smells</b>","venue: <c>plop</c>"],"search_terms":["anti","patterns","multi","language","systems","abidi","khomh","gu�h�neuc"],"title":"Anti-patterns for Multi-language Systems","year":2019}