On the Analysis of Co-Occurrence of Anti-Patterns and Clones. Jaafar, F., Lozano, A., Guéhéneuc, Y., & Mens, K. In Nuñez, M., Dohi, T., & Bai, X., editors, Proceedings of the 3<sup>rd</sup> International Conference on Software Quality, Reliability, and Security (QRS), pages 274–284, July, 2017. IEEE CS Press. 10 pages.Paper abstract bibtex One of the most important tasks in software maintenance is debugging. Developers perform debugging to fix faults and implement new features. Usually they use interactive development environments to perform their debugging sessions. To start an interactive debugging session, developers must set breakpoints. Choosing where to set breakpoints is a non-trivial task, yet few studies have investigated how developers set breakpoints during interactive debugging sessions. To understand how developers set breakpoints, we analysed more than 10 hours of 45 video-recorded debugging sessions, where a total of 307 breakpoints were set. We used the videos from two independent studies involving three software systems. We could observe that: (1) considerable time is spent by developers until they are able to set the first breakpoint; (2) when developers toggle breakpoints carefully, they complete tasks faster than developers who set (potential useless) breakpoints quickly; and (3) different developers set breakpoints in similar locations while working (independently) on the same tasks or different tasks. We discuss some implications of our observations for debugging activities.
@INPROCEEDINGS{Jaafar17-QRS-CloneAntipatterns,
author = {Fehmi Jaafar and Angela Lozano and Yann-Ga{\"e}l Gu{\'e}h{\'e}neuc and Kim Mens},
title = {On the Analysis of Co-Occurrence of Anti-Patterns and Clones},
booktitle = {Proceedings of the 3<sup>{rd}</sup> International Conference on Software Quality, Reliability, and Security ({QRS})},
year = {2017},
month = {July},
editor = {Manuel Nu{\~n}ez and Tadashi Dohi and Xiaoying Bai},
publisher = {IEEE CS Press},
note = {10 pages.},
abstract = {One of the most important tasks in software maintenance is debugging. Developers perform debugging to fix faults and implement new features. Usually they use interactive development environments to perform their debugging sessions. To start an interactive debugging session, developers must set breakpoints. Choosing where to set breakpoints is a non-trivial task, yet few studies have investigated how developers set breakpoints during interactive debugging sessions. To understand how developers set breakpoints, we analysed more than 10 hours of 45 video-recorded debugging sessions, where a total of 307 breakpoints were set. We used the videos from two independent studies involving three software systems. We could observe that: (1) considerable time is spent by developers until they are able to set the first breakpoint; (2) when developers toggle breakpoints carefully, they complete tasks faster than developers who set (potential useless) breakpoints quickly; and (3) different developers set breakpoints in similar locations while working (independently) on the same tasks or different tasks. We discuss some implications of our observations for debugging activities.},
grant = {NSERC DG and CRC on Multi-language Systems},
keywords = {Code and design smells ; QRS},
kind = {MISA},
language = {english},
url = {http://www.ptidej.net/publications/documents/QRS17b.doc.pdf},
pdf = {http://www.ptidej.net/publications/documents/QRS17b.ppt.pdf},
pages = {274--284}
}
Downloads: 0
{"_id":"JzKZrJEN4HxXLkQxg","bibbaseid":"jaafar-lozano-guhneuc-mens-ontheanalysisofcooccurrenceofantipatternsandclones-2017","downloads":0,"creationDate":"2018-01-17T20:29:42.160Z","title":"On the Analysis of Co-Occurrence of Anti-Patterns and Clones","author_short":["Jaafar, F.","Lozano, A.","Guéhéneuc, Y.","Mens, K."],"year":2017,"bibtype":"inproceedings","biburl":"http://www.yann-gael.gueheneuc.net/Work/BibBase/guehene (automatically cleaned).bib","bibdata":{"bibtype":"inproceedings","type":"inproceedings","author":[{"firstnames":["Fehmi"],"propositions":[],"lastnames":["Jaafar"],"suffixes":[]},{"firstnames":["Angela"],"propositions":[],"lastnames":["Lozano"],"suffixes":[]},{"firstnames":["Yann-Gaël"],"propositions":[],"lastnames":["Guéhéneuc"],"suffixes":[]},{"firstnames":["Kim"],"propositions":[],"lastnames":["Mens"],"suffixes":[]}],"title":"On the Analysis of Co-Occurrence of Anti-Patterns and Clones","booktitle":"Proceedings of the 3<sup>rd</sup> International Conference on Software Quality, Reliability, and Security (QRS)","year":"2017","month":"July","editor":[{"firstnames":["Manuel"],"propositions":[],"lastnames":["Nuñez"],"suffixes":[]},{"firstnames":["Tadashi"],"propositions":[],"lastnames":["Dohi"],"suffixes":[]},{"firstnames":["Xiaoying"],"propositions":[],"lastnames":["Bai"],"suffixes":[]}],"publisher":"IEEE CS Press","note":"10 pages.","abstract":"One of the most important tasks in software maintenance is debugging. Developers perform debugging to fix faults and implement new features. Usually they use interactive development environments to perform their debugging sessions. To start an interactive debugging session, developers must set breakpoints. Choosing where to set breakpoints is a non-trivial task, yet few studies have investigated how developers set breakpoints during interactive debugging sessions. To understand how developers set breakpoints, we analysed more than 10 hours of 45 video-recorded debugging sessions, where a total of 307 breakpoints were set. We used the videos from two independent studies involving three software systems. We could observe that: (1) considerable time is spent by developers until they are able to set the first breakpoint; (2) when developers toggle breakpoints carefully, they complete tasks faster than developers who set (potential useless) breakpoints quickly; and (3) different developers set breakpoints in similar locations while working (independently) on the same tasks or different tasks. We discuss some implications of our observations for debugging activities.","grant":"NSERC DG and CRC on Multi-language Systems","keywords":"Code and design smells ; QRS","kind":"MISA","language":"english","url":"http://www.ptidej.net/publications/documents/QRS17b.doc.pdf","pdf":"http://www.ptidej.net/publications/documents/QRS17b.ppt.pdf","pages":"274–284","bibtex":"@INPROCEEDINGS{Jaafar17-QRS-CloneAntipatterns,\n author = {Fehmi Jaafar and Angela Lozano and Yann-Ga{\\\"e}l Gu{\\'e}h{\\'e}neuc and Kim Mens},\n title = {On the Analysis of Co-Occurrence of Anti-Patterns and Clones},\n booktitle = {Proceedings of the 3<sup>{rd}</sup> International Conference on Software Quality, Reliability, and Security ({QRS})},\n year = {2017},\n month = {July},\n editor = {Manuel Nu{\\~n}ez and Tadashi Dohi and Xiaoying Bai},\n publisher = {IEEE CS Press},\n note = {10 pages.},\n abstract = {One of the most important tasks in software maintenance is debugging. Developers perform debugging to fix faults and implement new features. Usually they use interactive development environments to perform their debugging sessions. To start an interactive debugging session, developers must set breakpoints. Choosing where to set breakpoints is a non-trivial task, yet few studies have investigated how developers set breakpoints during interactive debugging sessions. To understand how developers set breakpoints, we analysed more than 10 hours of 45 video-recorded debugging sessions, where a total of 307 breakpoints were set. We used the videos from two independent studies involving three software systems. We could observe that: (1) considerable time is spent by developers until they are able to set the first breakpoint; (2) when developers toggle breakpoints carefully, they complete tasks faster than developers who set (potential useless) breakpoints quickly; and (3) different developers set breakpoints in similar locations while working (independently) on the same tasks or different tasks. We discuss some implications of our observations for debugging activities.},\n grant = {NSERC DG and CRC on Multi-language Systems},\n keywords = {Code and design smells ; QRS},\n kind = {MISA},\n language = {english},\n url = {http://www.ptidej.net/publications/documents/QRS17b.doc.pdf},\n pdf = {http://www.ptidej.net/publications/documents/QRS17b.ppt.pdf},\n pages = {274--284}\n}\n","author_short":["Jaafar, F.","Lozano, A.","Guéhéneuc, Y.","Mens, K."],"editor_short":["Nuñez, M.","Dohi, T.","Bai, X."],"key":"Jaafar17-QRS-CloneAntipatterns","id":"Jaafar17-QRS-CloneAntipatterns","bibbaseid":"jaafar-lozano-guhneuc-mens-ontheanalysisofcooccurrenceofantipatternsandclones-2017","role":"author","urls":{"Paper":"http://www.ptidej.net/publications/documents/QRS17b.doc.pdf"},"keyword":["Code and design smells ; QRS"],"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,"html":""},"search_terms":["analysis","occurrence","anti","patterns","clones","jaafar","lozano","guéhéneuc","mens"],"keywords":["code and design smells ; qrs"],"authorIDs":["AfJhKcg96muyPdu7S","xkviMnkrGBneANvMr"],"dataSources":["Sed98LbBeGaXxenrM","8vn5MSGYWB4fAx9Z4"]}