Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
events:workshops:esecfse2013 [2013/03/29 17:38] – [Submission Summary] abergelevents:workshops:esecfse2013 [2013/08/26 18:14] – [Artifact Evaluation at ESEC/FSE 2013] abergel
Line 5: Line 5:
 Results presented in technical papers are often validated or supported by software artifacts. To reward the effort of creating artifacts, authors of accepted research paper may, if they wish, have their tools, data or model evaluated by the Artifact Evaluation Committee. Results presented in technical papers are often validated or supported by software artifacts. To reward the effort of creating artifacts, authors of accepted research paper may, if they wish, have their tools, data or model evaluated by the Artifact Evaluation Committee.
  
-After the research paper notification, authors of accepted papers will be contacted to submit their artifact for evaluation. Evaluation of the artifact will be sent to the authors before the camera ready deadline.+After the research paper notification of [[http://esec-fse.inf.ethz.ch|ESEC/FSE 2013]], authors of accepted papers will be contacted to submit their artifact for evaluation. Evaluation of the artifact will be sent to the authors before the camera ready deadline.
  
 Artifacts that are positively evaluated, will be formally recognized in the proceedings and at the conference. Artifacts that are positively evaluated, will be formally recognized in the proceedings and at the conference.
 +
 +====== Distinguished Artifacts ======
 +There are 2 artifacts that deserved to be distinguished:
 +  - Paul Marinescu and Cristian Cadar. KATCH: High-Coverage Testing of Software Patches
 +  - Aravind Machiry, Rohan Tahiliani and Mayur Naik. Dynodroid: An Input Generation System for Android Apps
 +
 ====== Submission Summary ====== ====== Submission Summary ======
-  * Due on: Monday July 1st, 2013 (beginning of  the following week after the paper notification) +  * Due on: Sunday June 2nd 2013 (end of the week of the paper notification) **-- CLOSED** 
-  * Notification from the AEC: Tuesday June 25, 2013 (one week before the camera ready version)+  * Notification from the AEC: Monday June 24, 2013 (one week before the camera ready version) **-- PASSED**
   * Format: [[events/workshops/esecfse2013/guidelines|Guidelines for Packaging AEC Submissions]]    * Format: [[events/workshops/esecfse2013/guidelines|Guidelines for Packaging AEC Submissions]] 
-  * Contact: [[mailto:abergel@dcc.uchile.cl|Alexandre Bergel]] and [[mailto:bettini@dsi.unifi.it|Lorenzo Bettini]]+  * Contact: [[mailto:abergel@dcc.uchile.cl|Alexandre Bergel]] and [[mailto:bettini@di.unito.it|Lorenzo Bettini]]
 ====== Process ====== ====== Process ======
 Artifacts will be evaluated in a similar fashion than papers are. They will be reviewed by a committee (the Artifact Evaluation Committee, AEC) and graded according to what your accepted paper describes. Artifacts will be evaluated in a similar fashion than papers are. They will be reviewed by a committee (the Artifact Evaluation Committee, AEC) and graded according to what your accepted paper describes.
Line 18: Line 24:
 Software artifacts who successfully passed our evaluation will be officially recognized (in the proceedings, during the conference, during the social event presentation). Fireworks will be for the distinguished software artifacts. Software artifacts who successfully passed our evaluation will be officially recognized (in the proceedings, during the conference, during the social event presentation). Fireworks will be for the distinguished software artifacts.
  
 +====== Artifacts Meeting Expectation ======
 +In total we have received 22 artifacts. 12 have been assessed as "met expectation" or "Exceeded expectations". Below is the list of artifacts that have been positively evaluated.
 +
 +Out of the 12 positively evaluated artifacts, 8 will be presented on Friday 23 August 2013, during a dedicated slot 17:00 - 17:40.
 +Each presentation will have 5 minutes:
 +  * Paul Marinescu and Cristian Cadar -- //KATCH: High-Coverage Testing of Software Patches//
 +  * Dirk Beyer, Stefan Löwe, Evgeny Novikov, Andreas Stahlbauer and Philipp Wendler -- //Linux Driver Revisions for Regression Verification - [[http://www.sosy-lab.org/~dbeyer/cpa-reuse/regression-benchmarks/|online]]//
 +  * Shahar Maoz, Jan Oliver Ringert and Bernhard Rumpe -- //Synthesis of Component and Connector Models from Crosscutting Structural Views//
 +  * Marin Silic, Goran Delac and Sinisa Srbljic -- //Prediction of Atomic Web Services Reliability Based on K-means Clustering [[http://ccl.fer.hr/wordpress/people/research-assistants/marin-silic/clus-evaluation-dataset/|online]]//
 +  * Nishant Sinha and Rezwana Karim -- //Compiling Mockups to Flexible UIs//  [[https://www.youtube.com/watch?v=OoPdw0kWRcA|online video]]
 +  * Alex Gyori, Danny Dig, Lyle Franklin and Jan Lahoda -- //Crossing the gap from imperative to functional programming through refactoring [[http://refactoring.info/tools/LambdaFicator/|online]]//
 +  * Peng Liu -- //Finding Incorrect Compositions of Atomicity//
 +  * Yunhui Zheng, Xiangyu Zhang and Vijay Ganesh -- //Z3-str: A String Theory Plugin on Z3 for Web Application Analysis//
  
-====== Guidelines for Packaging AEC Submissions ======+The remaining 4 artifacts will be presented during their paper presentation slot: 
 +  * Meiyappan Nagappan, Thomas Zimmermann and Christian Bird -- //Diversity in Software Engineering Research -- [[http://sailhome.cs.queensu.ca/replication/representativeness/|online]]// 
 +  * Chengnian Sun and Siau-Cheng Khoo -- //Mining Succinct Predicated Bug Signatures// 
 +  * Aravind Machiry, Rohan Tahiliani and Mayur Naik -- //Dynodroid: An Input Generation System for Android Apps [[http://pag-www.gtisc.gatech.edu/dynodroid/data/|online]]// 
 +  * Pietro Braione, Giovanni Denaro and Mauro Pezze' -- //Enhancing Symbolic Execution with Built-in Term Rewriting and Constrained Lazy Initialization//
  
-TODO 
 ====== Artifact Evaluation Committee ====== ====== Artifact Evaluation Committee ======
 The committee has been carefully selected by the chairs to reflect the relevant topics of ESEC/FSE.  The committee has been carefully selected by the chairs to reflect the relevant topics of ESEC/FSE.