ICSME 2024
Sun 6 - Fri 11 October 2024 Location to be announced

Accepted Papers

Title
An Empirical Study of Automatic Program Repair Techniques for Injection Vulnerabilities
Research Track
A Taxonomy of Self-Admitted Technical Debt in Deep Learning Systems
Research Track
BABLE: a Novel Software Vulnerability Detection Framework for Breaking Language Barriers
Research Track
Blessing or Curse? Investigating Test Code Maintenance through Inheritance and Interface
Research Track
Broken Windows: Exploring the Applicability of a Controversial Theory on Code Quality
Research Track
Can Developers Prompt? A Controlled Experiment for Code Documentation Generation
Research Track
Can We Do Better with What We Have Done? Unveiling the Potential of ML Pipeline in Notebooks
Research Track
Compilation of Commit Changes within Java Source Code Repositories
Research Track
CPLS: Optimizing the Assignment of LLM Queries
Research Track
Decomposing God Header File via Multi-View Graph Clustering
Research Track
Deep Learning-based Code Completion: On the Impact on Performance of Contextual Information
Research Track
Demystifying Device-specific Compatibility Issues in Android Apps
Research Track
Encoding Domain Knowledge in Log Analysis
Research Track
Enhancing Web Test Script Repair using Integrated UI Structural and Visual Information
Research Track
Exploring Pseudo-Testedness: Empirically Evaluating Extreme Mutation Testing at the Statement Level
Research Track
Exploring the Adoption of Fuzz Testing in Open-Source Software: A Case Study of the Go Community
Research Track
Focused: An Approach to Framework-oriented Cross-language Link Specification and Detection
Research Track
How Far Have We Gone in Binary Code Understanding Using Large Language Models
Research Track
Impact of JVM Configurations on Test Runtime
Research Track
Improving long-tail vulnerability detection through data augmentation based on large language models
Research Track
Improving Retrieval-Augmented Code Comment Generation by Retrieving for Generation
Research Track
Investigating Developers' Preferences for Learning and Issue Resolution Resources in the ChatGPT Era
Research Track
Leveraging Large Vision-Language Model For Better Automatic Web GUI Testing
Research Track
Maven Unzipped: Packaging Impacts the Ecosystem
Research Track
Mind the Gap: The Disconnect Between Refactoring Criteria Used in Industry and Refactoring Recommendation Tools
Research Track
New PHP Language Features Make Your Static Code Analysis Tools Miss Vulnerabilities
Research Track
Next-Generation Refactoring: Combining LLM Insights and IDE Capabilities for Extract Method
Research Track
On the Generalizability of Transformer Models to Code Completions of Different Lengths
Research Track
On the Impact of Draft Pull Requests on Accelerating Feedback
Research Track
On the Rationale and Use of Assertion Messages in Test Code: Insights from Software Practitioners
Research Track
On the Use of Deep Learning Models for Semantic Clone Detection
Research Track
OPass: Orchestrating TVM's Passes for Lowering Memory Footprints of Computation Graphs
Research Track
Optimizing Decompiler Output by Eliminating Redundant Data Flow in Self-Recursive Inlining
Research Track
Precos: Project-specific Retrieval for Better Code Summarization
Research Track
Private — Keep Out? Understanding How Developers Account for Code Visibility in Unit Testing
Research Track
RENAS: Prioritizing Co-Renaming Opportunities of Identifiers
Research Track
RetypeR: Integrated Retrieval-based Automatic Program Repair for Python Type Errors
Research Track
Supporting Software Maintenance with Dynamically Generated Document Hierarchies
Research Track
Test Scheduling Across Heterogeneous Machines While Balancing Running Time, Price, and Flakiness
Research Track
The Effectiveness of Compact Fine-Tuned LLMs for Log Parsing
Research Track
The Impact of Program Reduction on Automated Program Repair
Research Track
Toward Debugging Deep Reinforcement Learning Programs with RLExplorer
Research Track
Towards Identifying Python Proficiency to Foster Software Maintenance and Evolution
Research Track
Towards Unmasking LGTM Smells in Code Reviews: A Comparative Study of Comment-Free and Commented Reviews
Research Track
Understanding Code Change with Micro-Changes
Research Track
Understanding Web Application Workloads and Their Applications: Systematic Literature Review and Characterization
Research Track
Unraveling the Impact of Code Smell Agglomerations on Code Stability
Research Track
vFix: Facilitating Software Maintenance of Smart Contracts via Automatically Fixing Vulnerabilities
Research Track
“What Happened to my Models?” History-Aware Co-Existence and Co-Evolution of Metamodels and Models
Research Track

Call for Papers

Goal and Scope

The 40th IEEE International Conference on Software Maintenance and Evolution (ICSME 2024) is the premier forum for researchers and practitioners to present and discuss the most recent innovations, trends, experiences, and challenges in software maintenance and evolution. We invite high quality submissions describing significant and unpublished results related to but not limited to any of the following software maintenance and evolution topics (in alphabetical order):

  • Change and defect management
  • Code cloning and provenance
  • Concept and feature location
  • Continuous integration/deployment
  • Empirical studies of software maintenance and evolution
  • Evolution of non-code artifacts
  • Evolution and maintenance of AI-based applications
  • Human aspects of software maintenance and evolution
  • Large Language Models for software evolution and maintenance tasks
  • Maintenance and evolution of model-based methods
  • Maintenance and evolution of mobile apps
  • Maintenance and evolution of service-oriented and cloud computing systems
  • Maintenance and evolution processes
  • Maintenance versus release process
  • Mining software repositories
  • Productivity of software engineers during maintenance and evolution
  • Release engineering
  • Reverse engineering and re-engineering
  • Run-time evolution and dynamic configuration
  • Software and system comprehension
  • Software migration and renovation
  • Software quality assessment
  • Software refactoring and restructuring
  • Software testing theory and practice
  • Source code analysis and manipulation
  • Technical Debt

ICSME welcomes innovative ideas that are timely, well-presented, and evaluated. All submissions must position themselves within the existing literature, describe the relevance of the results to specific software engineering goals, and include a clear motivation and presentation of the work. All submissions must be in English and follow the paper submission guidelines below.

All papers must be full papers.

Evaluation

Submissions that are not in compliance with the required submission format or that are out of the scope of the conference will be desk-rejected without being reviewed. All submissions that meet the submission criteria and fit the scope of the conference will be reviewed by three members of the program committee. The importance of contribution, originality, quality of presentation, soundness, evaluation (where applicable), and appropriate comparison to related work will be assessed for all submissions. Where applicable (e.g., empirical studies and other technical contributions with an evaluation), the replicability of the work will be assessed.

Author Response Period

ICSME 2024 will offer a seven-day author response period. In this period, the authors will have the opportunity to inspect the reviews and answer specific questions raised by the program committee. This period is scheduled after all reviews have been completed and discussed, to inform the subsequent decision-making process. Authors will be able to see the full reviews, including the reviewer scores as part of the author response process.

NEW IN 2024: Early Decisions

To reduce the author and reviewer burden of unnecessary writing/reading of author responses, ICSME 2024 is introducing early decisions: * If reviewers already decide that a paper can be accepted in its current state without requiring any further input from the authors, the authors will receive an “Accept” decision at the beginning of the author response period and will not be required to submit a response. * Conversely, if the paper is perceived to be in a highly deficient state by the reviewers, leading them to conclude that the authors’ response is unlikely to alter their evaluation significantly, the authors will receive a “Reject” decision at the beginning of the author response period and will not be asked to submit a response. * All other papers will receive a “Response Recommended” notification at the beginning of the author response period. However, as customary, it is still up to the authors to decide if they want to submit an author response.

This approach ensures that author responses are primarily reserved for cases with some controversy or where the reviewers have specific and pertinent inquiries to be addressed.

Publication and Presentation

Accepted papers will be published in the conference proceedings and submitted for inclusion in the IEEE Xplore Digital Library. All authors of all accepted papers will be asked to complete an electronic IEEE Copyright form and will receive further instructions for preparing their camera-ready versions. At least one author of each accepted paper must register for the conference and present the paper at the conference. Failure of at least one author to register by the early registration date will result in the paper being withdrawn from the conference proceedings. IEEE reserves the right to exclude a paper from distribution after the conference (e.g., by not placing it in the IEEE Xplore Digital Library) if the paper is not presented at the conference. Presentation details will follow notifications of acceptance.

Paper Submission

Submitted papers must comply with IEEE plagiarism policy and procedures. Papers submitted to ICSME 2024 must not have been published elsewhere and must not be under review, or submitted for review elsewhere while under consideration for ICSME 2024. Submitting the same paper to different tracks of ICSME 2024 is also not allowed. ICSME 2024 will use a double anonymous reviewing process. Submitted papers must adhere to the following rules:

  • Author names and affiliations must be omitted. (The track co-chairs will check compliance before reviewing begins.)
  • References to authors’ own related work must be in the third person. (For example, instead of “We build on our previous work…”, use “We build on the work of…”)
  • The title of the submission must be different from the preprints of the authors on arXiv or similar sites. During the review period, authors must not publicly use the submission title.
  • Please see the Double-Anonymous Reviewing FAQ for more information and guidance.

Papers must strictly adhere to the two-column IEEE conference proceedings format. Please use the templates available here. LaTeX users should use the following configuration: \documentclass[conference]{IEEEtran}. Microsoft Word users should use the US Letter format template. Papers must not exceed 10 pages (including figures and appendices) plus up to 2 pages that contain ONLY references. All submissions must be in PDF and must be submitted online by the deadline via the ICSME 2024 EasyChair link. All authors, reviewers, and organizers are expected to uphold the IEEE Code of Conduct.

Authors of select papers from the research track will be invited to submit extended versions of their work to a special issue of the Springer International Journal of Empirical Software Engineering (EMSE). Invited papers will be expected to comply with the standard guidelines when publishing an extended version of a paper, including the addition of about 30% new material.

Submission

Please use the following link to submit to the research track: https://easychair.org/conferences/?conf=icsme2024

Open Science Policy

ICSME encourages open science practices. While sharing of data sets, replication packages, or preprints is not required, it is expected to be the default, and non-sharing needs to be justified, for example, in the case of industry data subject to confidentiality issues or legal requirements. PC members are not required to run code and check details of the artifact, but are asked to comment on its inclusion (specifically whether the data/code promised in the paper is available in the artifact). Upon submission, authors should do one of the following: (1) make their data available to the program committee via an online archival (see below), (2) include in the paper an explanation as to why this is not possible or desirable, or (3) indicate that they intend to make their data publicly available upon acceptance. Note that, even if not intentional, the last option can create doubt in reviewers’ minds as to why the data is not made available for review. Accordingly, we strongly encourage following one of the first two options.

When sharing data, please use an online archival site such as zenodo.org, figshare.com, or https://osf.io/. These sites ensure that the content is archived and they generate a DOI for the content, enabling it to be cited. To learn more about how to share data while maintaining double-anonymous, read the explanation provided by Daniel Graziotin. One resource that may be helpful in accomplishing this task is this blog post. We recognize that anonymizing artifacts such as source code is more difficult than preserving anonymity in a paper. We ask authors to take a best-effort approach to not reveal their identities. We will also ask reviewers to avoid trying to identify authors by looking at commit histories and other such information that is not easily anonymized. Authors wanting to share GitHub repositories may want to look into using https://anonymous.4open.science, which is an open-source tool that helps you quickly double anonymous your repository.

ICSME supports and encourages Green Open Access (also called self-archiving). We encourage authors to self-archive a preprint of their accepted manuscript in an e-print server such as arXiv.org. Open access increases the availability of your work and increases citation impact. To learn more about open access, please read the Green Open Access FAQ by Arie van Deursen. Note that if your research includes scraped GitHub data, the GitHub Terms of Service require that “publications resulting from that research are open access”. If possible, we recommend that you archive your paper (e.g., on arXiv or on your website) only after the ICSME reviewing process is completed, to avoid undermining the double-anonymous reviewing process.

Authors of papers accepted into ICSME 2024 will be invited to submit their artifacts to the Artifact Evaluation Track. Papers with accepted artifacts will be awarded badges and invited to present lightning talks at the ROSE (Recognising and Rewarding Open Science in Software Engineering) Festival. Please see the Call for Participation for the Artifact Evaluation Track.

For inquiries, we invite you to reach out to the ROSE Festival and artifacts chairs, Massimiliano di Penta (dipenta@unisannio.it) and Fernanda Madeiral (f.madeiral.delfim@vu.nl).

Important Dates

** All submission dates are at 23:59 AoE (Anywhere on Earth) **

  • Abstract submission: April 4, 2024
  • Paper submission: April 11, 2024
  • Early decision notification: May 30, 2024
  • Final notification: June 13, 2024
  • Camera-ready submission: July 29, 2024

Track Co-Chairs

Fabio Calefato (fabio.calefato@uniba.it), University of Bari, Italy

Sarah Nadi (sarah.nadi@nyu.edu), New York University Abu Dhabi, UAE