Short Papers and Artefacts Track - Evaluation and Assessment in Software Engineering
Short Paper Track
The short paper category invites submission of insightful research that can often go unrecognized under the standard review process. This includes, but is not limited to, for instance:
- Critique of established methodology and/or practice.
- Research on controversial topics.
- “Folklore confirmations”: when a sound research finds “what everyone knows already”. We will consider “common sense” findings that may not have been scientifically proven, but might be considered “not new enough” under traditional peer review.
- Unexpected results: when an empirical evaluation results diverge dramatically from the expectations, and the researchers do not find what they were looking for.
- Confirmation studies, when a new study confirms previously well-known results.
- Methodological failure reports, where poor design invalidates otherwise interesting findings (both the findings and study design flaws need to be discussed).
- Preliminary results: the early results of an on-going research.
Submission
- Submissions should be limited to 4 – 6 pages, including figures, tables, and references.
- Please use submit manuscripts via EasyChair in pdf format: (https://easychair.org/my/conference?conf=ease2020) and choose the Short Paper Track option form the submission menu.
- All accepted papers will be published by ACM in the ACM International Conference Proceedings Series. The ACM offers options for Open Access (https://www.acm.org/openaccess).
- The Short Paper Track will follow a double-blind review process.
Artifacts Track
The artifact category encourages submission of artifacts which can provide value to the broader empirical research. Given ACM’s definition, an artifact refers to a "digital object that was either created by the authors to be used as part of the study or generated by the experiment itself. For example, artifacts can be software systems, scripts used to run experiments, input datasets, raw data collected in the experiment, or scripts used to analyse results." Considering the classification of artifact submissions proposed by well-known software engineering venues (e.g., ICSE), we are interested in the following artifacts:
- Software, which are implementations of systems or algorithms potentially useful in other studies.
- Data repositories, which are data (e.g., logging data, system traces, survey raw data) that can be used for multiple software engineering approaches.
- Frameworks, which are tools and services illustrating new approaches to software engineering that could be used by other researchers in different contexts.
The artifacts should be submitted along with a paper explaining the artifact, how it is created and how it can be reused.
EASE aims to promote artifact reuse, and, to this end, will build a topic- specific community-wide catalogue to support empirical research.
Guideline
The submissions should include:
- The artifacts should be archived on proper repositories that can provide a DOI for reliable citation (e.g., archive.org, figshare.com). We do not restrict the choice of repository; however, the authors must provide evidence that the archive remains accessible permanently. For example, private websites / repositories are not considered as a proper archive repository. The artifacts should be made available by the camera-ready deadline. All the artifacts should be accompanied with a ReadMe file indicating details of installation/ configuration.
- A paper that is limited to 4-6 pages, including figures, tables, and references. The paper should clearly explain a) what the artifact is; b) how it was created (e.g., description of tools/environment/scripts that were used); c) how it can be reproduced and re-used for evaluation; d) what are the potential applications of the artifact; and, e) limitations of the artifact and how to mitigate them in future. It should also highlight that how the presented artifact differs from the existing ones if there is any.
- If the artifact has been already used in other research papers, it should be stated. It is appreciated if the authors also make available the tools/scripts that are used for creating the data repositories. In that case, please make sure to provide related URLs in the paper with clear instructions.
Submission
- A zip file including the paper in pdf format + artifact should be submitted via Easy Chair: (https://easychair.org/my/conference?conf=ease2020 ) after choosing the Artifact track option form the submission menu.
- The artifacts specially software and frameworks, should be submitted with proper packaging (e.g., docker container, VM) and guideline to ensure the submission can be run on other systems for review purpose. We do not guarantee a follow-up with authors for technical details if the program committee members cannot run the submitted artifact.
- In case the artifact is too large to be summitted via Easy Chair, the authors must provide a URL for downloading the artifacts for review. The authors should accompany their paper with a one-pager stating how to access the artifact for review. In order to maintain the anonymity of reviewers, the track-chairs collect the data and share with program committee.
- All accepted papers will be published by ACM in the ACM International Conference Proceedings Series. The ACM offers options for Open Access (https://www.acm.org/openaccess).
- The artifacts will follow a single-blind review process.
- Abstract submission: December 17, 2019
- Full submission: December 22, 2019
- Author notification: February 3, 2020
- Camera-ready: February 15, 2020
Track Co-Chairs
Mansooreh Zahedi, The University of Adelaide, Australia
Xianoying Bai, Tsinghua University, China
Program Committee - Short Papers Track
Ronald Jabangwe, Maersk Mc-Kinney Moller Institute, SDU Software Engineering, University of Southern Denmark
Cagatay Catal, Wageningen University
George Grispos, University of Nebraka at Omaha
Amiangshu Bosu, Wayne State University
Jose Luis de la Vara, University of Castilla-La Mancha
Said Assar, Institut Mines-Telecom Business School
Noel Carroll, National University of Ireland Galway
Xiaofeng Wang, Free University of Bozen-Bolzano
Damian Andrew Tamburri, Technical University of Eindhoven - Jeronimus Academy of Data Science
Carmine Gravino, Department of Computer Science - University of Salerno
Rafael Prikladnicki, PUCRS
Cheng Zhang, Anhui University
Uirá Kulesza, UFRN
Eduardo Figueiredo, Federal University of Minas Gerais
Silvia T. Acuña, Universidad Autonoma de Madrid
Beatriz Marín, Universidad Diego Portales
Monalessa Barcellos, UFES
Peter Andras, Keele University
Foutse Khomh, DGIGL, École Polytechnique de Montréal
Gustavo Pinto, UFPA
Davide Fucci, HITeC, University of Hamburg
Breno de França, UNICAMP
Markus Borg, RISE SICS AB
Aaron Massey, University of Maryland, Baltimore County
Norah Power, University of Limerick
João M. Fernandes, University of Minho
Emelie Engstrom, Lund University, Sweden
Siim Karus, University of Tartu
Valentina Lenarduzzi, Tampere University of Technology
Davide Taibi,Tampere University of Technology
Jose Antonio Cruz-Lemus, University of Castilla-La Mancha
Filippo Ricca, DIBRIS, Università di Genova - Italy
Claudia P. Ayala, Universitat Politècnica de Catalunya
Raula Gaikovina Kula, Nara Institute of Science and Technology
Ewan Tempero, The University of Auckland
Hideaki Hata, Nara Institute of Science and Technology
Paolo Tell, IT University of Copenhagen
Program Committee - Artefacts Track
Sebastian Baltes, The University of Adelaide, Australia
Jason Xue, The University of Adelaide, Australia
Li Li, Monash University, Australia
Monika Gupta, IBM Research India
Efthimia Aivaloglou, University of Leiden, Netherlands
Hitesh Sajnani, University of California, Irvine; Microsoft
Triet Huynh Minh Le, The University of Adelaide, Australia
Dionysis Athanasopoulos, Queen's University of Belfast, UK