Write a Blog >>
ICSE 2020
Wed 24 June - Thu 16 July 2020

The Software Engineering in Practice (SEIP) track is the privileged ICSE track for researchers and practitioners to discuss insights, innovations and solutions to concrete software engineering problems. Following its tradition, SEIP will gather highly-qualified industrial and research participants who are eager to discuss common interests in software engineering. The track will comprise invited and reviewed sessions, including paper presentations, reviewed talks, interactive sessions with a strong focus on software practice.

Dates
Nothing to filter
Tracks
ICSE Demonstrations
ICSE Journal First
ICSE New Ideas and Emerging Results
ICSE Software Engineering in Practice
ICSE Technical Papers
ICSE
Software
Engineering
in
Practice
You're viewing the program in a time zone which is different from your device's time zone change time zone

Accepted Papers

Title
Assessing Practitioner BeliefsSEIP
Software Engineering in Practice
Pre-print Media Attached
Automated Bug Reproduction from User Reviews for Android ApplicationsSEIP
Software Engineering in Practice
Automated Identification of Libraries from Vulnerability DataSEIP
Software Engineering in Practice
Pre-print Media Attached
Automatic Abnormal Log Detection by Analyzing Log History for Providing Debugging InsightSEIP
Software Engineering in Practice
Building and Maintaining a Third-Party Library Supply Chain for Productive and Secure SGX Enclave DevelopmentSEIP
Software Engineering in Practice
Code Level Model-Checking in the Software Development WorkflowArtifact ReusableArtifact AvailableSEIP
Software Engineering in Practice
Pre-print Media Attached
Debugging Crashes using Continuous Contrast Set MiningSEIP
Software Engineering in Practice
DeCaf: Diagnosing & Triaging Performance Issues in Large-Scale Cloud ServicesSEIP
Software Engineering in Practice
Pre-print
Engineering for a Science-Centric Experimentation PlatformSEIP
Software Engineering in Practice
Escape from Escape Analysis of GolangSEIP
Software Engineering in Practice
Exploring Differences and Commonalities between Feature Flags and Configuration OptionsSEIP
Software Engineering in Practice
Pre-print
How do you Architect your Robots? State of the Practice and Guidelines for ROS-based SystemsArtifact ReusableArtifact AvailableSEIP
Software Engineering in Practice
How to reduce risk effectively in fixed price software developmentSEIP
Software Engineering in Practice
JSidentify: A Hybrid Framework for Detecting Plagiarism Among JavaScript Code in Online Mini GamesSEIP
Software Engineering in Practice
Lack of Adoption of Units of Measurement Libraries: Survey and AnecdotesSEIP
Software Engineering in Practice
Modeling and Ranking Flaky Tests at AppleSEIP
Software Engineering in Practice
Piranha: Reducing Feature Flag Debt at UberSEIP
Software Engineering in Practice
Pre-print
PRECFIX: Large-Scale Patch Recommendation by Mining Defect-Patch PairsSEIP
Software Engineering in Practice
Pre-print
Property-based Testing for LG Home Appliances using Accelerated Software-in-the-Loop SimulationIEEE Software Best Software Engineering in Practice AwardSEIP
Software Engineering in Practice
Pre-print
Rule-based Code Generation in Industrial Automation: Four Large-scale Case Studies applying the CAYENNE MethodSEIP
Software Engineering in Practice
Pre-print
Sharing at Scale: An Open-Source-Software-based License Compliance EcosystemSEIP
Software Engineering in Practice
Software Development Data for Architecture Analysis: Expectation, Reality, and Future DirectionsSEIP
Software Engineering in Practice
The Forgotten Case of the Dependency Bugs: On the Example of the Robot Operating SystemSEIP
Software Engineering in Practice
Pre-print
Towards Understanding and Fixing Upstream Merge Induced Conflicts in Divergent Forks: An industrial Case StudySEIP
Software Engineering in Practice
Understanding and Handling Alert Storm for Online Service SystemsSEIP
Software Engineering in Practice
Using a Context-Aware Approach to Recommend Code Reviewers: Findings from an Industrial Case StudySEIP
Software Engineering in Practice

Call for Papers

The Software Engineering in Practice (SEIP) Track is the premier venue for researchers and practitioners to discuss insights, innovations and solutions to concrete software engineering problems. After many decades of research, software engineering (SE) techniques and algorithms are gaining substantial momentum in industry: more companies produce SE-based tools and more software engineers use previously published ideas in their daily projects. SEIP provides a unique forum for networking, exchanging ideas, fostering innovations, and forging long-term collaborations to address SE research that impacts directly on practice. SEIP will gather highly-qualified industrial and research participants that are eager to communicate and share common interests in software engineering. The track will be composed of invited speeches, paper presentations, reviewed talks, interactive sessions with a strong focus on software practice.

Submissions

We are seeking the following types of submissions, all of which must be written exclusively in English. We do not use double-blind review (i.e., authors do not have to hide their identities in their papers).

Full papers: (8-10 pages, including figures, tables, appendices, and 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. Other aspects that should be included if appropriate are: 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. IEEE Software will recognize the best paper of the SEIP track with an award at the conference.

Talk proposals (2 pages): Talks present topics that are likely to be relevant and interesting to both practitioners and researchers. Talk proposals should include the title, the name and affiliation of each presenter, a short abstract (150 words), and up to 8 keywords. In addition, the proposal should describe what the talk will be about, highlighting its key points and the reason why it is interesting to ICSE-SEIP attendees (500 words). Submissions should include a speaker biography and history, and they can include supporting materials such as whitepapers or videos.

Please note that the target audience of the talk proposal is the SEIP program committee. Talk proposals will be reviewed in two phases. The outcome of the first phase is either rejected or conditionally accepted for the next phase. In the second phase, submitters will be required to prepare the complete presentation. The target audience of the second phase talk proposal is the attendees of the SEIP track and readers of the proceedings. The committee will then review the presentations and make the final accept/reject decisions. Each accepted talk will be of 30 minutes duration and will be allowed two pages for an “extended abstract” in the ICSE SEIP Companion proceedings.

Interactive proposals (2 pages): Interactive sessions are aimed at practitioners but should be attractive for all audiences. Interactive sessions will be 60 minutes’ duration and will explore an aspect of practice in-depth. They may take the form of, for example, a panel discussion or live coding session (but should not aim to promote a specific proprietary tool). We welcome new and thought-provoking ideas and formats, and encourage submitters to contact the chairs at any time with their suggestions before making a formal proposal.

Interactive proposals should include a title, the name and affiliation of each presenter, a short abstract that describes the focus of the session and the outcomes for attendees (150 words), and up to 8 keywords. In addition, the proposal should describe why the session focus is important, outlining the session structure and the reason why it is interesting to ICSE-SEIP attendees (500 words). Like talk proposals, interactive proposals will be reviewed in two phases. The outcome of the first phase is either rejected or conditionally accepted for the next phase. In the second phase, submitters will be required to prepare a detailed plan of the session and a complete set of materials to be used. Each interactive session will be allowed two pages for an “extended abstract” in the ICSE SEIP Companion proceedings.

Formatting and Submission Links: Formatting instructions are available at https://www.acm.org/publications/proceedings-template for both LaTeX and Word users. LaTeX users must use the provided acmart.cls and ACM-Reference-Format.bst without modification, enable the conference format in the preamble of the document (i.e., \documentclass[sigconf,review]{acmart}), and use the ACM reference format for the bibliography (i.e., \bibliographystyle{ACM-Reference-Format}). The review option adds line numbers, thereby allowing referees to refer to specific lines in their comments.

Evaluation

All submissions will be reviewed by members of the SEIP Program Committee. Submissions must not have been previously published or concurrently submitted elsewhere. Submissions will be evaluated on the basis of relevance to industry, significance of contribution, and quality of presentation.

Special Issue

Authors from this track will be encouraged to submit an extended version of their work to Journal of Software: Practice and Experience’s special issue on software engineering in practice. The submission deadline is April 15, 2020.

https://onlinelibrary.wiley.com/page/journal/1097024x/homepage/special_issues.htm

Conference Attendance Expectation

If a submission is accepted, at least one author of the paper is required to register for and attend the full 3-day technical conference and present the paper in person.

Important Dates for Paper submissions

  • Submissions Due: Fri 4th Oct 2019
  • Notification of Acceptance: Mon 16th Dec 2019
  • Camera Ready Copy: Fri 7th Feb 2020

Important Dates for Talk and Interactive submissions

  • Phase 1 Submissions Due: Fri 4th Oct 2019
  • Phase 1 Notifications: Fri 22nd Nov 2019
  • Phase 2 Submissions Due: Mon 6th Jan 2020
  • Notification of Acceptance: Mon 20th Jan 2020
  • Camera Ready Copy: Fri 7th Feb 2020

Contact

If there are queries regarding the CFP, please contact the SEIP chairs (Mark Grechanik and Moonzoo Kim): icse2020seip@gmail.com.

:
: