Write a Blog >>

Call for Papers

We invite high-quality submissions describing original and unpublished results of theoretical, empirical, conceptual, and experimental software engineering research. Contributions should describe innovative and significant original research. Papers describing groundbreaking approaches to emerging problems will also be considered. Submissions that facilitate reproducibility by using available datasets or making the described tools and datasets publicly available are especially encouraged. We are interested in submissions from both industry and academia on all topics related to software engineering. For a list of topics, please see the end of this call. Papers submitted to ESEC/FSE for consideration should not have been already published elsewhere and should not be under review or submitted for review elsewhere during the reviewing period. Specifically, authors are required to adhere to the ACM Policy and Procedures on Plagiarism and the ACM Policy on Prior Publication and Simultaneous Submissions.

How to Submit

At the time of submission all papers must conform to the ESEC/FSE 2020 Format and Submission Guidelines, and must not exceed 10 pages for all text and figures plus 2 pages for references. All submissions must be in English and in PDF format. You can submit, optionally, an additional file containing supplementary material (see details below). Submissions that do not comply with the above instructions will be desk rejected without review. Papers must be submitted electronically through the ESEC/FSE submission site:

https://esecfse2020.hotcrp.com

Each submission will be reviewed by at least three members of the program committee. Authors will have an opportunity to respond to reviews during a rebuttal period. Submissions will be evaluated on the basis of originality, importance of contribution, soundness, evaluation, quality of presentation and appropriate comparison to related work. The program committee as a whole will make final decisions about which submissions to accept for presentation at the conference. ESEC/FSE 2020 will employ a double-blind review process. The papers submitted must not reveal the authors’ identities in any way:

  • Authors should leave out author names and affiliations from the body of their submission.
  • Authors should ensure that any citations to related work by themselves is written in third person, that is, “the prior work of XYZ” as opposed to “our prior work”.
  • Authors should not include URLs to author-revealing sites (tools, datasets).
  • You are encouraged to submit a link to a Web site or repository containing supplementary material (raw data, datasets, experiments, etc.), as long as it is blinded. The visit of such sites should not be needed to conduct the review. The program committee will not necessarily consider it in the paper review process. For more information, please read How to disclose data for double-blind review and make it archived open data upon acceptance.
  • Authors should anonymize author-revealing company names. Authors should provide general characteristics of the organizations involved needed to understand the context of the paper.

The paper anonymity will be maintained during the reviewers’ discussion period and the authors’ rebuttal period. Authors must therefore maintain the anonymity in their responses, during the rebuttal phase, and provide no additional information that would otherwise be author-revealing.

Authors having further questions on double blind reviewing are encouraged to contact the program chairs by email. Papers that do not comply to the double-blind review process will be desk-rejected.

To prevent double submissions, the chairs will compare the submissions with related conferences that have overlapping review periods. The double submission restriction applies only to refereed journals and conferences, not to unrefereed forums (e.g. arXiv.org). To check for plagiarism issues, the chairs will use external plagiarism detection software.

All publications are subject to the ACM Author Representations policy.

Important Dates

All dates are 23:59:59 AoE (UTC-12h).

  • Full paper submission: 5 March 2020
  • Rebuttal period (all papers): 27-30 April 2020
  • Additional short response period (selected papers): 9-10 May 2020
  • Notification: 21 May 2020
  • Camera ready: September 10, 2020

Open Science Policy

The research track of ESEC/FSE has introduced an open science policy. Openness in science is key to fostering scientific progress via transparency, reproducibility, and replicability. The steering principle is that all research results should be accessible to the public, if possible, and that empirical studies should be reproducible. In particular, we actively support the adoption of open data and open source principles and encourage all contributing authors to disclose (anonymized and curated) data to increase reproducibility and replicability.

Upon submission to the research track, authors are asked to make their data available to the program committee (via upload of supplemental material or a link to a private or public repository) or to comment on why this is not possible or desirable. While sharing such a repository is not mandatory for submission or acceptance, this information will be passed to the program committee to inform its decision. Furthermore, authors are asked to indicate whether they intend to make their data publicly available upon acceptance. For more details on ESEC/FSE open science policy, please refer to the official guidelines.

Topics of Interest

Topics of interest include, but are not limited to:

  1. Agile software development
  2. AI and software engineering
  3. Apps and app store analysis
  4. Automated reasoning techniques
  5. Autonomic and (self-)adaptive systems
  6. Big data
  7. Cloud computing
  8. Component-based software engineering
  9. Computer-supported cooperative work
  10. Configuration management and deployment
  11. Crowd sourced software engineering
  12. Cyber physical systems
  13. Data-driven software engineering
  14. Debugging
  15. Dependability, safety, and reliability
  16. Distributed and collaborative software engineering
  17. Domain modeling and meta-modeling
  18. Education
  19. Embedded software
  20. Emerging domains of software
  21. Empirical software engineering
  22. End-user software engineering
  23. Fault localization
  24. Formal methods
  25. Green and sustainable technologies
  26. Human and social aspects of software engineering
  27. Human-computer interaction
  28. Knowledge acquisition and management
  29. Machine learning for software engineering
  30. Middleware, frameworks, and APIs
  31. Mining software engineering repositories
  32. Mobile applications
  33. Model-driven engineering
  34. Parallel, distributed, and concurrent systems
  35. Performance
  36. Program analysis
  37. Program comprehension
  38. Program repair
  39. Program synthesis
  40. Programming languages
  41. Recommendation systems
  42. Refactoring
  43. Requirements engineering
  44. Reverse engineering
  45. Safety-critical systems
  46. Scientific computing
  47. Search-based software engineering
  48. Security, privacy and trust
  49. Software architecture
  50. Software economics and metrics
  51. Software engineering for machine learning
  52. Software evolution and maintenance
  53. Software modeling and design
  54. Software process
  55. Software product lines
  56. Software reuse
  57. Software services
  58. Software testing
  59. Software visualization
  60. Specification and modeling languages
  61. Tools and environments
  62. Traceability
  63. Ubiquitous and pervasive software systems
  64. Validation and verification