ESEM Registered ReportsESEIW 2024
Call for Registrations
Empirical Software Engineering Journal (EMSE), in conjunction with the ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM), is continuing the RR track. The RR track of ESEM 2024 has two goals: (1) to prevent HARKing (hypothesizing after the results are known) for empirical studies; (2) to provide early feedback to authors in their initial study design. For papers submitted to the RR track, methods and proposed analyses are reviewed prior to execution. Pre-registered studies follow a two-step process:
-
Stage 1: A report is submitted that describes the planned study. The submitted report is evaluated by the reviewers of the RR track of ESEM 2024. Authors of accepted pre-registered studies will be given the opportunity to present their work at ESEM.
-
Stage 2: Once a report has passed Phase 1, the study will be conducted and actual data collection and analysis take place. The results may also be negative! The full paper is submitted for review to EMSE.
Paper Types, Evaluation Criteria, and Acceptance Types
The RR track of ESEM 2024 supports two types of papers:
Confirmatory : The researcher has a fixed hypothesis (or several fixed hypotheses) and the objective of the study is to find out whether the hypothesis is supported by the facts/data.
An example of a completed confirmatory study:
- Inozemtseva, L., & Holmes, R. (2014, May). Coverage is not strongly correlated with test suite effectiveness. In Proceedings of the 36th international conference on software engineering (pp. 435-445).
Exploratory : The researcher does not have a hypothesis (or has one that may change during the study). Often, the objective of such a study is to understand what is observed and answer questions such as WHY, HOW, WHAT, WHO, or WHEN. We include in this category registrations for which the researcher has an initial proposed solution for an automated approach (e.g., a new deep-learning-based defect prediction approach) that serves as a starting point for his/her exploration to reach an effective solution.
Examples of completed exploratory studies:
-
Gousios, G., Pinzger, M., & Deursen, A. V. (2014, May). An exploratory study of the pull-based software development model. In Proceedings of the 36th International Conference on Software Engineering (pp. 345-355).
-
Rodrigues, I. M., Aloise, D., Fernandes, E. R., & Dagenais, M. (2020, June). A Soft Alignment Model for Bug Deduplication. In Proceedings of the 17th International Conference on Mining Software Repositories (pp. 43-53).
The reviewers will evaluate RR track submissions based on the following criteria:
-
The importance of the research question(s).
-
The logic, rationale, and plausibility of the proposed hypotheses.
-
The soundness and feasibility of the methodology and analysis pipeline (including statistical power analysis where appropriate).
-
(For confirmatory study) Whether the clarity and degree of methodological detail is sufficient to exactly replicate the proposed experimental procedures and analysis pipeline.
-
(For confirmatory study) Whether the authors have pre-specified sufficient outcome-neutral tests for ensuring that the results obtained can test the stated hypotheses, including positive controls and quality checks.
-
(For exploratory study, if applicable) The description of the data set that is the base for exploration.
The outcome of the RR report review is one of the following:
-
In-Principal Acceptance (IPA): The reviewers agree that the study is relevant, the outcome of the study (whether confirmation / rejection of hypothesis) is of interest to the community, the protocol for data collection is sound, and that the analysis methods are adequate. The authors can engage in the actual study for Stage 2. If the protocol is adhered to (or deviations are thoroughly justified), the study is published. Of course, this being a journal submission, a revision of the submitted manuscript may be necessary. Reviewers will especially evaluate how precisely the protocol of the accepted pre-registered report is followed, or whether deviations are justified.
-
Continuity Acceptance (CA): The reviewers agree that the study is relevant, that the (initial) methods appear to be appropriate. However, for exploratory studies, implementation details and post-experiment analyses or discussion (e.g., why the proposed automated approach does not work) may require follow-up checks. We’ll try our best to get the original reviewers. All PC members will be invited on the condition that they agree to review papers in both, Stage 1 and Stage 2. Four (4) PC members will review the Stage 1 submission, and three (3) will review the Stage 2 submission.
-
Rejection The reviewers do not agree on the relevance of the study or are not convinced that the study design is sufficiently mature. Comments are provided to the authors to improve the study design before starting it.
Note : For ESEM 2024, only confirmatory studies are granted an IPA. Exploratory study in software engineering often cannot be adequately assessed until after the study has been completed and the findings are elaborated and discussed in a full paper. For example, consider a study in an RR proposing defect prediction using a new deep learning architecture. This work falls under the exploratory category. It is difficult to offer IPA, as we do not know whether it is any better than a traditional approach based on e.g., decision trees. Negative results are welcome; however, it is important that the negative results paper goes beyond presenting “we tried and failed”, but rather provide interesting insights to readers, e.g., why the results are negative or what that means for further studies on this topic (following criteria of REplication and Negative Results (RENE) tracks, e.g., https://saner2023.must.edu.mo/negativerestrack). Furthermore, it is important to note that authors are required to document all deviations (if any) in a section of the paper.
Submission Process and Instructions
The timeline for ESEM 2024 RR track will be as follows:
Mon 06 May 2024 : Authors submit their initial report. Submissions must not exceed 6 pages (plus 1 additional page of references). The page limit is strict.
All authors should use the official “ACM Primary Article Template”, as can be obtained from the ACM Proceedings Template page. LaTeX users should use the sigconf option, as well as the review (to produce line numbers for easy reference by the reviewers). To that end, the following LaTeX code can be placed at the start of the LaTeX document: \documentclass[sigconf,review]{acmart}
Wed 29 May 2024 : Authors receive PC members’ reviews.
Wed 19 Jun 2024 : Authors submit a response letter + revised report in a single PDF.
-
The response letter should address reviewer comments and questions.
-
The response letter + revised report must not exceed 12 pages (plus 1 additional page of references).
-
The response letter does not need to follow ACM formatting instructions.
Wed 17 Jul 2024: Notification of Stage 1
- (Outcome: in-principal acceptance, continuity acceptance, or rejection).
Wed 28 Aug 2024 : Authors submit their accepted RR report to arXiv
-
To be checked by PC members for Stage 2
-
Note: RR reports will not be published in the ESEM 2024 proceedings.
Before Mon 12 May 2025 : Authors submit a full paper to EMSE. Instructions will be provided later. However, the following constraints will be enforced:
-
Justifications need to be given to any change of authors. If the authors are added/removed or the author order is changed between the original Stage 1 and the EMSE submission, all authors will need to complete and sign a “Change of authorship request form”. The Editors in Chief of EMSE and chairs of the RR track reserve the right to deny author changes. If you anticipate any authorship changes please reach out to the chairs of the RR track as early as possible.
-
PC members who reviewed an RR report in Stage 1 and their directly supervised students cannot be added as authors of the corresponding submission in Stage 2.
Submissions can be made via the submission site (https://easychair.org/my/conference?conf=esem24) by the submission deadline. Any submission that does not comply with the aforementioned instructions and the mandatory information specified in the Author Guide is likely to be desk rejected. In addition, by submitting, the authors acknowledge that they are aware of and agree to be bound by the following policies:
- The ACM Policy and Procedures on Plagiarism and the IEEE Plagiarism FAQ. In particular, papers submitted to ESEM 2024 must not have been published elsewhere and must not be under review or submitted for review elsewhere whilst under consideration for ESEM 2024. Contravention of this concurrent submission policy will be deemed a serious breach of scientific ethics, and appropriate action will be taken in all such cases (including immediate rejection and reporting of the incident to ACM/IEEE). To check for double submission and plagiarism issues, the chairs reserve the right to (1) share the list of submissions with the PC Chairs of other conferences with overlapping review periods and (2) use external plagiarism detection software, under contract to the ACM or IEEE, to detect violations of these policies. The authorship policy of the ACM and the authorship policy of the IEEE.
Thu 24 OctDisplayed time zone: Brussels, Copenhagen, Madrid, Paris change
09:00 - 10:30 | Opening and KeynoteESEIW ESEM at Sala d'actes de Camins (C2 Building) Chair(s): Maya Daneva University of Twente, Xavier Franch Universitat Politècnica de Catalunya, Silverio Martínez-Fernández UPC-BarcelonaTech | ||
09:00 30mOther | Conference Opening ESEIW ESEM Xavier Franch Universitat Politècnica de Catalunya, Maya Daneva University of Twente, Silverio Martínez-Fernández UPC-BarcelonaTech | ||
09:30 60mKeynote | The Method Behind the Magic: Ensuring Reliability in Software Engineering Empirical Results ESEIW ESEM Sira Vegas Universidad Politecnica de Madrid File Attached |
10:30 - 11:00 | |||
10:30 30mCoffee break | Break Catering |
12:30 - 14:00 | |||
12:30 90mLunch | Lunch Catering |
14:00 - 15:30 | Posters: research projects and registered reportsESEM Registered Reports / ESEM Research Projects at Agora (in front of Plaça Telecos) Chair(s): Andreas Jedlitschka Fraunhofer IESE | ||
14:00 3mPoster | MSR4SBOM: Mining Software Repositories for enhanced Software Bills of Materials ESEM Research Projects Giuseppe Scanniello University of Salerno, Massimiliano Di Penta University of Sannio, Italy, Simone Romano University of Salerno, Rita Francese , Sabato Nocera University of Salerno, Daniele Bifolco University of Sannio, Fiorella Zampetti University of Sannio, Italy, Pietro Cassieri University of Salerno | ||
14:03 3mPoster | Edge-AI Assurance in the REBECCA Project ESEM Research Projects Clara Ayora Universidad de Castilla La Mancha, Arturo S. García Universidad de Castilla La Mancha, Jose Luis de la Vara Universidad de Castilla - La Mancha | ||
14:06 3mPoster | MOOD: Mindfulness fOr sOftware Developers ESEM Research Projects Simone Romano University of Salerno, Giuseppe Scanniello University of Salerno, Alessandro Marchetto Università di Trento, Paolo Giorgini University of Trento, Gloria Guidetti University of Torino, Daniela Converso University of Torino, Sara Viotti University of Torino | ||
14:09 3mPoster | Continuous Quality Improvement of AI-based Systems: the QualAI Project ESEM Research Projects Nicole Novielli University of Bari, Rocco Oliveto University of Molise, Fabio Palomba University of Salerno, Fabio Calefato University of Bari, Giuseppe Colavito University of Bari, Italy, Vincenzo De Martino University of Salerno, Antonio Della Porta University of Salerno, Giammaria Giordano University of Salerno, Emanuela Guglielmi University of Molise, Filippo Lanubile University of Bari, Luigi Quaranta University of Bari, Italy, Gilberto Recupito University of Salerno, Simone Scalabrino University of Molise, Angelica Spina University of Molise, Antonio Vitale University of Molise, Italy | ||
14:12 3mPoster | FRINGE: context-aware FaiRness engineerING in complex software systEms ESEM Research Projects Fabio Palomba University of Salerno, Andrea Di Sorbo University of Sannio, Davide Di Ruscio University of L'Aquila, Filomena Ferrucci University of Salerno, Gemma Catolino University of Salerno, Giammaria Giordano University of Salerno, Dario Di Dario University of Salerno, Gianmario Voria University of Salerno, Viviana Pentangelo University of Salerno, Maria Tortorella University of Sannio, Arnaldo Sgueglia , Claudio Di Sipio University of l'Aquila, Giordano d'Aloisio University of L'Aquila, Antinisca Di Marco University of L'Aquila | ||
14:15 3mPoster | Evidence-Based Commit Message Generation with Deep Learning Techniques (EvidenCoM) ESEM Research Projects Sira Vegas Universidad Politecnica de Madrid, Xavier Ferré Universidad Politécnica de Madrid, Hongming Zhu | ||
14:18 3mPoster | In Search of Metrics to Guide Developer-Based Refactoring Recommendations. A Registered Report ESEM Registered Reports Mikel Robredo University of Oulu, Matteo Esposito University of Oulu, Fabio Palomba University of Salerno, Rafael Peñaloza , Valentina Lenarduzzi University of Oulu DOI Pre-print | ||
14:21 3mPoster | Virtual Reality vs. 2D Visualizations for Software Ecosystem Dependency Analysis -- A Controlled Experiment ESEM Registered Reports David Moreno-Lumbreras Universidad Rey Juan Carlos, Jesus M. Gonzalez-Barahona Universidad Rey Juan Carlos, Gregorio Robles Universidad Rey Juan Carlos | ||
14:24 3mPoster | Measuring Information Diffusion in Code Review at Spotify ESEM Registered Reports Michael Dorner Blekinge Institute of Technology, Daniel Mendez Blekinge Institute of Technology and fortiss, Ehsan Zabardast Blekinge Institute of Technology, Nicole Valdez Spotify, Marcin Floryan Spotify DOI Pre-print | ||
14:27 3mPoster | Validation of an Analysability Model in Hybrid Quantum Software ESEM Registered Reports Ana Díaz Muñoz AQCLab Software Quality, Jose Antonio Cruz-Lemus University of Castilla-La Mancha, Moisés Rodrígez Monje UCLM | AQCLab, Mario Piattini University of Castilla-La Mancha, Spain, Maria Teresa Baldassarre Department of Computer Science, University of Bari | ||
14:30 3mPoster | Usefulness of data flow diagrams and large language models for security threat validation: a registered report ESEM Registered Reports | ||
14:33 3mPoster | Local Software Buildability across Java Versions ESEM Registered Reports Matúš Sulír Technical University of Košice, Jaroslav Porubän Technical University of Košice, Slovakia, Sergej Chodarev Technical University of Košice Link to publication Pre-print | ||
14:36 54mPoster | Research projects and registered reports presentations and discussions ESEM Registered Reports |
15:30 - 16:00 | |||
15:30 30mCoffee break | Break Catering |
Accepted Papers
Title | |
---|---|
In Search of Metrics to Guide Developer-Based Refactoring Recommendations. A Registered Report ESEM Registered Reports DOI Pre-print | |
Local Software Buildability across Java Versions ESEM Registered Reports Link to publication Pre-print | |
Measuring Information Diffusion in Code Review at Spotify ESEM Registered Reports DOI Pre-print | |
Usefulness of data flow diagrams and large language models for security threat validation: a registered report ESEM Registered Reports | |
Validation of an Analysability Model in Hybrid Quantum Software ESEM Registered Reports | |
Virtual Reality vs. 2D Visualizations for Software Ecosystem Dependency Analysis -- A Controlled Experiment ESEM Registered Reports |