@INPROCEEDINGS{Sharafi15-APSEC-EyeTrackingMetrics,
   AUTHOR       = {Zohreh Sharafi and Timothy Shaffer and Bonita Sharif and 
      Yann-Ga�l Gu�h�neuc},
   BOOKTITLE    = {Proceedings of the 22<sup>nd</sup> Asia-Pacific Software Engineering Conference (APSEC)},
   TITLE        = {Eye-tracking Metrics in Software Engineering},
   YEAR         = {2015},
   OPTADDRESS   = {},
   OPTCROSSREF  = {},
   EDITOR       = {Jing Sun and Y. Raghu Reddy},
   MONTH        = {December},
   NOTE         = {8 pages.},
   OPTNUMBER    = {},
   OPTORGANIZATION = {},
   PAGES        = {96--103},
   PUBLISHER    = {IEEE CS Press},
   OPTSERIES    = {},
   OPTVOLUME    = {},
   KEYWORDS     = {Topic: <b>Program comprehension</b>, 
      Venue: <c>APSEC</c>},
   URL          = {http://www.ptidej.net/publications/documents/APSEC15.doc.pdf},
   PDF          = {http://www.ptidej.net/publications/documents/APSEC15.ppt.pdf},
   ABSTRACT     = {Eye-tracking studies are getting more prevalent in 
      software engineering. Researchers often use different metrics when 
      publishing their results in eye-tracking studies. Even when the same 
      metrics are used, they are given different names, causing 
      difficulties in comparing studies. To encourage replications and 
      facilitate advancing the state of the art, it is important that the 
      metrics used by researchers be clearly and consistently defined in 
      the literature. There is therefore a need for a survey of eyetracking 
      metrics to support the (future) goal of standardizing eyetracking 
      metrics. This paper seeks to bring awareness to the use of different 
      metrics along with practical suggestions on using them. It compares 
      and contrasts various eye-tracking metrics used in software 
      engineering. It also provides definitions for common metrics and 
      discusses some metrics that the software engineering community might 
      borrow from other fields.}
}

{"_id":"2va7HzBpX5SXnmNh3","bibbaseid":"sharafi-shaffer-sharif-guhneuc-eyetrackingmetricsinsoftwareengineering-2015","downloads":0,"creationDate":"2018-01-17T20:29:42.246Z","title":"Eye-tracking Metrics in Software Engineering","author_short":["Sharafi, Z.","Shaffer, T.","Sharif, B.","Gu�h�neuc, Y."],"year":2015,"bibtype":"inproceedings","biburl":"http://www.yann-gael.gueheneuc.net/Work/Publications/Biblio/complete-bibliography.bib","bibdata":{"bibtype":"inproceedings","type":"inproceedings","author":[{"firstnames":["Zohreh"],"propositions":[],"lastnames":["Sharafi"],"suffixes":[]},{"firstnames":["Timothy"],"propositions":[],"lastnames":["Shaffer"],"suffixes":[]},{"firstnames":["Bonita"],"propositions":[],"lastnames":["Sharif"],"suffixes":[]},{"firstnames":["Yann-Ga�l"],"propositions":[],"lastnames":["Gu�h�neuc"],"suffixes":[]}],"booktitle":"Proceedings of the 22^nd Asia-Pacific Software Engineering Conference (APSEC)","title":"Eye-tracking Metrics in Software Engineering","year":"2015","optaddress":"","optcrossref":"","editor":[{"firstnames":["Jing"],"propositions":[],"lastnames":["Sun"],"suffixes":[]},{"firstnames":["Y.","Raghu"],"propositions":[],"lastnames":["Reddy"],"suffixes":[]}],"month":"December","note":"8 pages.","optnumber":"","optorganization":"","pages":"96–103","publisher":"IEEE CS Press","optseries":"","optvolume":"","keywords":"Topic: <b>Program comprehension</b>, Venue: <c>APSEC</c>","url":"http://www.ptidej.net/publications/documents/APSEC15.doc.pdf","pdf":"http://www.ptidej.net/publications/documents/APSEC15.ppt.pdf","abstract":"Eye-tracking studies are getting more prevalent in software engineering. Researchers often use different metrics when publishing their results in eye-tracking studies. Even when the same metrics are used, they are given different names, causing difficulties in comparing studies. To encourage replications and facilitate advancing the state of the art, it is important that the metrics used by researchers be clearly and consistently defined in the literature. There is therefore a need for a survey of eyetracking metrics to support the (future) goal of standardizing eyetracking metrics. This paper seeks to bring awareness to the use of different metrics along with practical suggestions on using them. It compares and contrasts various eye-tracking metrics used in software engineering. It also provides definitions for common metrics and discusses some metrics that the software engineering community might borrow from other fields.","bibtex":"@INPROCEEDINGS{Sharafi15-APSEC-EyeTrackingMetrics,\r\n AUTHOR = {Zohreh Sharafi and Timothy Shaffer and Bonita Sharif and \r\n Yann-Ga�l Gu�h�neuc},\r\n BOOKTITLE = {Proceedings of the 22^nd Asia-Pacific Software Engineering Conference (APSEC)},\r\n TITLE = {Eye-tracking Metrics in Software Engineering},\r\n YEAR = {2015},\r\n OPTADDRESS = {},\r\n OPTCROSSREF = {},\r\n EDITOR = {Jing Sun and Y. Raghu Reddy},\r\n MONTH = {December},\r\n NOTE = {8 pages.},\r\n OPTNUMBER = {},\r\n OPTORGANIZATION = {},\r\n PAGES = {96--103},\r\n PUBLISHER = {IEEE CS Press},\r\n OPTSERIES = {},\r\n OPTVOLUME = {},\r\n KEYWORDS = {Topic: <b>Program comprehension</b>, \r\n Venue: <c>APSEC</c>},\r\n URL = {http://www.ptidej.net/publications/documents/APSEC15.doc.pdf},\r\n PDF = {http://www.ptidej.net/publications/documents/APSEC15.ppt.pdf},\r\n ABSTRACT = {Eye-tracking studies are getting more prevalent in \r\n software engineering. Researchers often use different metrics when \r\n publishing their results in eye-tracking studies. Even when the same \r\n metrics are used, they are given different names, causing \r\n difficulties in comparing studies. To encourage replications and \r\n facilitate advancing the state of the art, it is important that the \r\n metrics used by researchers be clearly and consistently defined in \r\n the literature. There is therefore a need for a survey of eyetracking \r\n metrics to support the (future) goal of standardizing eyetracking \r\n metrics. This paper seeks to bring awareness to the use of different \r\n metrics along with practical suggestions on using them. It compares \r\n and contrasts various eye-tracking metrics used in software \r\n engineering. It also provides definitions for common metrics and \r\n discusses some metrics that the software engineering community might \r\n borrow from other fields.}\r\n}\r\n\r\n","author_short":["Sharafi, Z.","Shaffer, T.","Sharif, B.","Gu�h�neuc, Y."],"editor_short":["Sun, J.","Reddy, Y. R."],"key":"Sharafi15-APSEC-EyeTrackingMetrics","id":"Sharafi15-APSEC-EyeTrackingMetrics","bibbaseid":"sharafi-shaffer-sharif-guhneuc-eyetrackingmetricsinsoftwareengineering-2015","role":"author","urls":{"Paper":"http://www.ptidej.net/publications/documents/APSEC15.doc.pdf"},"keyword":["Topic: <b>Program comprehension</b>","Venue: <c>APSEC</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":["eye","tracking","metrics","software","engineering","sharafi","shaffer","sharif","gu�h�neuc"],"keywords":["topic: <b>program comprehension</b>","venue: <c>apsec</c>"],"authorIDs":["AfJhKcg96muyPdu7S","xkviMnkrGBneANvMr"],"dataSources":["Sed98LbBeGaXxenrM","8vn5MSGYWB4fAx9Z4"]}