ICSE 2024
Fri 12 - Sun 21 April 2024 Lisbon, Portugal

Call for papers

The Software Engineering in Practice (SEIP) track is the premier venue for practitioners and researchers to discuss insights, innovations, and solutions to concrete software engineering problems. Practical software development relies on excellent software engineering research.

SEIP provides a unique forum for networking, exchanging ideas, fostering innovations, and forging long-term collaborations to address Software Engineering research that impacts directly on practice. It is one of the most prestigious forums in which to publish work in the Software Engineering literature. SEIP will include participants and speakers from both industrial and academic sectors, drawing together researchers and practitioners eager to communicate and share common interests in software engineering. The track will be composed of invited talks, paper presentations, and interactive sessions, all with a strong focus on software practice.

Please note that the ICSE SEIP track DOES NOT require double-anonymous review. Unlike other ICSE tracks, it is often important for SEIP paper authors and the organizations involved to be visible to the reviewers in order for the reviewers to fully understand the industrial relevance and context.

Submissions

Link to submission: https://icse2024-seip.hotcrp.com/

We seek the following two types of submissions, both of which must be written exclusively in English and for which paper limits include references.

Full papers (up to 10 pages, plus up to 2 pages for references)

Full papers address industrially-relevant problems through systematic investigations. Each paper should describe a problem of practical importance, explain how the problem was investigated and in what context, and present evidence for the paper’s conclusions. The submission should have technical and empirical soundness. Other aspects that should also be included where appropriate include: discussing why the resolution of the problem is innovative, (cost-) effective, or efficient; providing a concise explanation of the approach, techniques, and methodologies employed; and explaining the insights or best practices that emerged, tools developed, and/or software processes involved.

Full papers will appear in the ICSE SEIP Companion proceedings.

Industrial Challenge papers (up to 2 pages, plus up to 1 page for references)

Industrial challenge papers outline a new research challenge, arising from industrial software practice and experience. A challenge paper will clearly articulate the problem and motivate it in terms of its potential for industrial impact and/or its practical importance. The aim of the call for challenge papers is to provide a growing pool of well-defined industrially relevant problems for the research community to tackle. Submission Process

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) option. To that end, the following LaTeX code can be placed at the start of the LaTeX document:

\documentclass[sigconf,review]{acmart}

\acmConference[ICSE 2024]{46th International Conference on Software Engineering}{April 2024}{Lisbon, Portugal}

  • All submissions must not exceed 10 pages (for full papers) or 2 pages (for industrial challenge papers) for the main text, inclusive of all figures, tables, appendices, etc. Two more pages (for full papers) or one more page (for industrial challenge papers) containing only references are permitted. All submissions must be in PDF. Accepted papers will be allowed one extra page for the main text of the camera-ready version.

  • Submissions must strictly conform to the ACM conference proceedings formatting instructions specified above. Alterations of spacing, font size, and other changes that deviate from the instructions may result in desk rejection without further review.

  • By submitting to the ICSE Research Track, authors acknowledge that they are aware of and agree to be bound by the ACM Policy and Procedures on Plagiarism and the IEEE Plagiarism FAQ. Papers submitted to ICSE 2024 must not have been published elsewhere and must not be under review or submitted for review elsewhere whilst under consideration for ICSE 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. 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.

  • By submitting to the ICSE Research Track, authors acknowledge that they conform to the authorship policy of the ACM, and the authorship policy of the IEEE.

  • By submitting your article to an ACM Publication, you are hereby acknowledging that you and your co-authors are subject to all ACM Publications Policies, including ACM’s new Publications Policy on Research Involving Human Participants and Subjects. Alleged violations of this policy or any ACM Publications Policy will be investigated by ACM and may result in a full retraction of your paper, in addition to other potential penalties, as per ACM Publications Policy.

  • Please ensure that you and your co-authors obtain an ORCID ID, so you can complete the publishing process for your accepted paper. ACM has been involved in ORCID from the start and we have recently made a commitment to collect ORCID IDs from all of our published authors. The collection process has started and will roll out as a requirement throughout 2022. We are committed to improve author discoverability, ensure proper attribution and contribute to ongoing community efforts around name normalization; your ORCID ID will help in these efforts.

Evaluation

All SEIP submissions will be reviewed by members of the SEIP Program Committee. Submissions will be evaluated based on relevance to industrial practice, the significance of contribution, and the quality of presentation.

By submitting to this track, authors acknowledge that they are aware of and agree to be bound by the ACM Policy and Procedures on Plagiarism and the IEEE Plagiarism FAQ. In particular, papers submitted to ICSE 2024 SEIP must not have been published elsewhere and must not be under review or submitted for review elsewhere whilst under consideration for ICSE SEIP 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. 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.

By submitting to this track, authors acknowledge that they conform to the authorship policy of the ACM, and the authorship policy of the IEEE.

Important Dates

  • Submission Deadline: October 6th 2023 - Submissions close at 23:59 AoE (Anywhere on Earth, UTC-12)
  • Acceptance Notification: December 21st 2023.
  • Camera Ready Due: January 10th 2024.

Conference Attendance Expectation

If a submission is accepted, at least one author of the paper is required to register for and attend the conference to present the paper. The presentation is expected to be delivered in person, unless this is impossible due to travel restrictions (related to, e.g., health, visa, or COVID-19 constraints).

Contact

If there are queries regarding the CFP, please contact the ICSE SEIP 2024 chairs (Maurício Aniche and Nachi Nagappan): mauricio.aniche@adyen.com and nachiappan.nagappan@gmail.com.

Accepted Papers

Title
A Catalog of Unintended Software Dependencies in Multi-Lingual Systems at ASML
Software Engineering in Practice
An Ethnographic Study on the CI of A Large Scale Project
Software Engineering in Practice
A New Frontier of AI: On-Device AI Training and Personalization
Software Engineering in Practice
Pre-print
An Industry Case Study on Adoption of AI-based Programming Assistants
Software Engineering in Practice
API Governance at Scale
Software Engineering in Practice
Assessing LLMs for High Stakes Applications
Software Engineering in Practice
AutoConsis: Automatic GUI-driven Data Inconsistency Detection of Mobile Apps
Software Engineering in Practice
Automated Security Findings Management: A Case Study in Industrial DevOps
Software Engineering in Practice
Pre-print
Autonomous Monitors for Detecting Failures Early and Reporting Interpretable Alerts in Cloud Operations
Software Engineering in Practice
Broadly Enabling KLEE to Effortlessly Find Unrecoverable Errors in Rust
Software Engineering in Practice
CodeFuse-13B: A Pretrained Multi-lingual Code Large Language Model
Software Engineering in Practice
Code Impact Beyond Disciplinary Boundaries: Constructing A Multidisciplinary Dependency Graph and Analyzing Cross-Boundary Impact
Software Engineering in Practice
Constructive Code Review: Managing the Impact of Interpersonal Conflicts in Practice
Software Engineering in Practice
Data Lineage Analysis for Enterprise Applications by Manta: The Story of Java and C# Scanners
Software Engineering in Practice
Dynamic Alert Suppression Policy for Noise Reduction in AIOps
Software Engineering in Practice
Dynamic Inference of Likely Symbolic Tensor Shapes in Python Machine Learning Programs
Software Engineering in Practice
DOI Pre-print
Enhancing Testing at Meta with Rich-State Simulated Populations
Software Engineering in Practice
Enhancing Text-to-SQL Translation for Financial System Design
Software Engineering in Practice
FaultProfIT: Hierarchical Fault Profiling of Incident Tickets in Large-scale Cloud Systems
Software Engineering in Practice
GWP-ASan: Sampling-Based Detection of Memory-Safety Bugs in Production
Software Engineering in Practice
Hawkeye: Change-targeted Testing for Android Apps based on Deep Reinforcement Learning
Software Engineering in Practice
Industrial Challenges in Secure Continuous Development
Software Engineering in Practice
Pre-print
Inference for Ever-Changing Policy of Taint Analysis
Software Engineering in Practice
Intelligent Monitoring Framework for Cloud Services: A Data-Driven Approach
Software Engineering in Practice
Knowledge-aware Alert Aggregation in Large-scale Cloud Systems: a Hybrid Approach
Software Engineering in Practice
Lessons from Building CodeBuddy: A Contextualized AI Coding Assistant
Software Engineering in Practice
LLM4PLC: Harnessing Large Language Models for Verifiable Programming of PLCs in Industrial Control Systems
Software Engineering in Practice
MicroFuzz: An Efficient Fuzzing Framework for Microservices
Software Engineering in Practice
Mind the Gap: What Working With Developers on Fuzz Tests Taught Us About Coverage Gaps
Software Engineering in Practice
DOI Pre-print
Motivating Open Source Collaborations Through Social Network Evaluation: A Gamification Practice from Alibaba
Software Engineering in Practice
Objectives and Key Results in Software Teams: Challenges, Opportunities and Impact on Development
Software Engineering in Practice
On the Costs and Benefits of Adopting Lifelong Learning for Software Analytics - Empirical Study on Brown Build and Risk Prediction
Software Engineering in Practice
Pre-print
On the Difficulty of Identifying Incident-Inducing Changes
Software Engineering in Practice
PrivacyCAT: Privacy-Aware Code Analysis at Scale
Software Engineering in Practice
Productive Coverage: Improving the Actionability of Code Coverage
Software Engineering in Practice
Resolving Code Review Comments with Machine Learning
Software Engineering in Practice
Software in the Manufacturing Industry: Emerging Security Challenge Areas for IIoT Platforms
Software Engineering in Practice
Stop Pulling my Rug: Exposing Rug Pull Risks in Crypto Token to Investors
Software Engineering in Practice
Taming Timeout Flakiness: An Empirical Study of SAP HANA
Software Engineering in Practice
The Devil Is in the Command Line: Associating the Compiler Flags With the Binary and Build Metadata
Software Engineering in Practice
DOI Pre-print
The Impact Of Bug Localization Based on Crash Report Mining: A Developers' Perspective
Software Engineering in Practice
Towards Building AI-CPS with NVIDIA Isaac Sim: An Industrial Benchmark and Case Study for Robotics Manipulation
Software Engineering in Practice
Translating between SQL Dialects for Cloud Migration
Software Engineering in Practice
User-Centric Deployment of Automated Program Repair at Bloomberg
Software Engineering in Practice
What Do You Mean by Memory? When Engineers Are Lost in the Maze of Complexity
Software Engineering in Practice
DOI Pre-print