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�l Gu�h�neuc and
Kim Mens},
BOOKTITLE = {Proceedings of the 3<sup>rd</sup> International Conference on Software Quality, Reliability, and Security (QRS)},
TITLE = {On the Analysis of Co-occurrence of Anti-Patterns and
Clones},
YEAR = {2017},
OPTADDRESS = {},
OPTCROSSREF = {},
EDITOR = {Manuel Nu�ez and Tadashi Dohi and Xiaoying Bai},
MONTH = {July},
NOTE = {10 pages.},
OPTNUMBER = {},
OPTORGANIZATION = {},
PAGES = {274--284},
PUBLISHER = {IEEE CS Press},
OPTSERIES = {},
OPTVOLUME = {},
KEYWORDS = {Topic: <b>Code and design smells</b>, Venue: <c>QRS</c>},
URL = {http://www.ptidej.net/publications/documents/QRS17b.doc.pdf},
PDF = {http://www.ptidej.net/publications/documents/QRS17b.ppt.pdf},
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.}
}
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/Publications/Biblio/complete-bibliography.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":[]}],"booktitle":"Proceedings of the 3<sup>rd</sup> International Conference on Software Quality, Reliability, and Security (QRS)","title":"On the Analysis of Co-occurrence of Anti-Patterns and Clones","year":"2017","optaddress":"","optcrossref":"","editor":[{"firstnames":["Manuel"],"propositions":[],"lastnames":["Nu�ez"],"suffixes":[]},{"firstnames":["Tadashi"],"propositions":[],"lastnames":["Dohi"],"suffixes":[]},{"firstnames":["Xiaoying"],"propositions":[],"lastnames":["Bai"],"suffixes":[]}],"month":"July","note":"10 pages.","optnumber":"","optorganization":"","pages":"274–284","publisher":"IEEE CS Press","optseries":"","optvolume":"","keywords":"Topic: <b>Code and design smells</b>, Venue: <c>QRS</c>","url":"http://www.ptidej.net/publications/documents/QRS17b.doc.pdf","pdf":"http://www.ptidej.net/publications/documents/QRS17b.ppt.pdf","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.","bibtex":"@INPROCEEDINGS{Jaafar17-QRS-CloneAntipatterns,\r\n AUTHOR = {Fehmi Jaafar and Angela Lozano and Yann-Ga�l Gu�h�neuc and \r\n Kim Mens},\r\n BOOKTITLE = {Proceedings of the 3<sup>rd</sup> International Conference on Software Quality, Reliability, and Security (QRS)},\r\n TITLE = {On the Analysis of Co-occurrence of Anti-Patterns and \r\n Clones},\r\n YEAR = {2017},\r\n OPTADDRESS = {},\r\n OPTCROSSREF = {},\r\n EDITOR = {Manuel Nu�ez and Tadashi Dohi and Xiaoying Bai},\r\n MONTH = {July},\r\n NOTE = {10 pages.},\r\n OPTNUMBER = {},\r\n OPTORGANIZATION = {},\r\n PAGES = {274--284},\r\n PUBLISHER = {IEEE CS Press},\r\n OPTSERIES = {},\r\n OPTVOLUME = {},\r\n KEYWORDS = {Topic: <b>Code and design smells</b>, Venue: <c>QRS</c>},\r\n URL = {http://www.ptidej.net/publications/documents/QRS17b.doc.pdf},\r\n PDF = {http://www.ptidej.net/publications/documents/QRS17b.ppt.pdf},\r\n ABSTRACT = {One of the most important tasks in software maintenance \r\n is debugging. Developers perform debugging to fix faults and \r\n implement new features. Usually they use interactive development \r\n environments to perform their debugging sessions. To start an \r\n interactive debugging session, developers must set breakpoints. \r\n Choosing where to set breakpoints is a non-trivial task, yet few \r\n studies have investigated how developers set breakpoints during \r\n interactive debugging sessions. To understand how developers set \r\n breakpoints, we analysed more than 10 hours of 45 video-recorded \r\n debugging sessions, where a total of 307 breakpoints were set. We \r\n used the videos from two independent studies involving three software \r\n systems. We could observe that: (1) considerable time is spent by \r\n developers until they are able to set the first breakpoint; (2) when \r\n developers toggle breakpoints carefully, they complete tasks faster \r\n than developers who set (potential useless) breakpoints quickly; and \r\n (3) different developers set breakpoints in similar locations while \r\n working (independently) on the same tasks or different tasks. We \r\n discuss some implications of our observations for debugging \r\n activities.}\r\n}\r\n\r\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":["Topic: <b>Code and design smells</b>","Venue: <c>QRS</c>"],"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":["analysis","occurrence","anti","patterns","clones","jaafar","lozano","gu�h�neuc","mens"],"keywords":["topic: <b>code and design smells</b>","venue: <c>qrs</c>"],"authorIDs":["AfJhKcg96muyPdu7S","xkviMnkrGBneANvMr"],"dataSources":["Sed98LbBeGaXxenrM","8vn5MSGYWB4fAx9Z4"]}