Write a Blog >>
ICSE 2023
Sun 14 - Sat 20 May 2023 Melbourne, Australia

Call for Papers

Being a software engineer goes far beyond just writing code. Software engineers need to possess a balanced set of soft and technical skills that allow them to solve real-world problems, work in teams to develop complex, high-quality software systems, efficiently evolve and maintain these systems, all while catering to users’ changing needs. Many paths could be taken and combined to acquire and develop this skill set, from formal education to on-the-job training, from coding clubs to boot camps, by using online or offline platforms and resources, etc. ICSE SEET 2023 is a venue interested in all these paths and aspects of teaching and training the future and current software engineers.

ICSE SEET is the premiere venue that brings together educators from both academia and industry worldwide to share and discuss cutting-edge results and experiences on how to best shape software engineers that are able to deal with real-word challenges. We invite you to join us to continue to grow our collective knowledge in the field of software engineering education and training.

Topics of Interest

ICSE SEET 2023 seeks original contributions covering all dimensions of learning and teaching software engineering topics. We welcome a variety of papers addressing challenges, innovations, and best practices in software engineering education and training. Contributions may address different levels and contexts, including, but not limited to, primary and secondary education, university education at undergraduate and graduate levels, coding clubs, hackathons, bootcamps, industrial training, and informal learning and training.

Topics of interest include, but are not limited to:

● Foundational research on software engineering skills

● Methods of teaching software engineering skills

● Methods of evaluating, assessing, and measuring software engineering skills

● Evaluation and assessment in software engineering education

● Evaluations of teaching and assessment methods in software engineering

● Empirical studies describing software engineering education contexts

● Pedagogical approaches supporting software engineering education and training in distributed and remote settings

● Learning technologies and tools that support software engineering education and training

● Automated evaluation of software engineering skills

● Role of soft skills (communication, collaboration, teamwork, organization, negotiation, conflict management) for software engineers

● Studies of equity, diversity, and inclusion in software engineering education and training

● Ethical and societal concerns (e.g., sustainability, human values) in software engineering education and training

● Onboarding and on-the-job training of software engineers

● Continuing education of software engineers

● Extra-curricular training of software engineering students (e.g., through hackathons, bootcamps)

● Certification and training for professional software engineers

● Use of online platforms and resources for software engineering education

● Role of culture and gender in software engineering education and training

● Introducing software engineering topics to children in primary and secondary education

● Encouraging synergy between academia and industry in software engineering education and training

Submission Categories

Research Paper (max 10 pages, plus up to 2 pages for references) A research paper must address a topic related to software engineering and education using appropriate research techniques and proper scholarly writing. Negative and mixed findings are acceptable.

Experience Report (max 10 pages, plus up to 2 pages for references) An experience report provides anecdotal evidence by describing an experience related to software engineering education and training (typically a course, a teaching or training technique or strategy, or an assessment method) and interprets the experience in terms of actionable advice and lessons learned, but does not need to evaluate it or use rigorous research methods to support its claims. Negative and mixed findings are acceptable provided they can support advice or lessons learned.

Idea Paper (max 5 pages, plus 1 page of references) An idea paper must present a new software engineering education and training idea with a proposed formal evaluation strategy, possibly with some preliminary or informal results.

Tool Paper (max 5 pages, plus 1 page of references) A tool paper describes a tool or technology that supports software engineering education and training. Papers in this category should discuss the impact of the tool on the learning process. A tool paper can optionally be accompanied by a short video (not exceeding five minutes) demonstrating the tool’s main functionality (if you use this option, please provide the link at the end of the abstract).

Replication Paper (max 5 pages, plus 1 page of references) A replication paper describes the repetition of an existing and already published pedagogical intervention (e.g. course, approach, study) in new contexts. The goal is to determine if the basic findings related to the original pedagogical intervention can be applied to other circumstances.

SEET submissions should not exceed their respective category page limit, including all text, figures, tables, and appendices. The page limits are strict and non-compliance will result in a desk-rejection.

Evaluation Criteria

Submissions will be evaluated based on their category:

Research Papers will be evaluated against these criteria: Relevance, Significance, Soundness, Verifiability, Presentation

Experience Reports will be evaluated against these criteria: Relevance, Significance, Actionability, Lessons, Presentation

Idea Papers will be evaluated against these criteria: Relevance, Significance, Soundness, Presentation

Tool Papers will be evaluated against these criteria: Relevance, Significance, Maturity, Availability, Presentation

Replication Papers will be evaluated against these criteria: Relevance, Significance, Soundness, Presentation

The evaluation criteria for SEET 2023 papers are defined as follows:

Relevance: The extent to which the paper is relevant to SEET.

Significance: The extent to which the paper is well-motivated and its contributions are original and important, with respect to the existing literature on software engineering education and training.

Soundness: The extent to which the paper’s contributions are supported by rigorous application of appropriate research methods and whether the paper discusses meaningfully the research methods’ limitations and threats to the validity of the findings.

Verifiability: The extent to which the paper includes sufficient information to support independent verification or replication of the paper’s claimed contributions. This includes public availability of research data or an explicit statement why such data cannot be made publicly available.

Actionability: The extent to which the paper provides actionable advice with clear take-away messages.

Lessons: The extent to which the paper meaningfully discusses lessons learned in terms of what went right, what went wrong, and what could be improved if the experience is repeated.

Maturity: The extent to which the tool or technology is mature enough to be presented.

Availability: Whether the tool or technology is available online, open-sourced, or on a trial basis and the extent to which it can be evaluated by potential users.

Presentation: The extent to which the paper’s organization and quality of writing is up to the standard: the paper is well-structured, employs clear and correct scholarly language, avoids ambiguity, includes clearly readable figures and tables, and is appropriately formatted.

How to Submit

All submissions must conform to the IEEE conference proceedings template, specified in the IEEE Conference Proceedings Formatting Guidelines (title in 24pt font and full text in 10pt type, LaTeX users must use \documentclass[10pt,conference]{IEEEtran} without including the compsoc or compsocconf options). Submissions must strictly conform to the IEEE 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 SEET 2023 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 SEET 2023 must not have been published elsewhere and must not be under review or submitted for review elsewhere whilst under consideration for ICSE SEET 2023 . 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.

● If the research involves human participants/subjects, the authors must adhere to the ACM Publications Policy on Research Involving Human Participants and Subjects . Upon submitting, authors will declare their compliance to such a policy.

● The ICSE SEET 2023 will employ a double-anonymous review process. Thus, no submission may reveal its authors’ identities in the paper nor in the artifacts, code, videos, tools, documentation, or repositories associated with the submission. The authors must make every effort to honor the double-anonymous review process. In particular:

Authors’ names must be omitted from the submission.

○ All references to the author’s prior work should be in the third person.

○ While authors have the right to upload preprints on ArXiV or similar sites, they should avoid specifying that the manuscript was submitted to ICSE SEET 2023.

○ During review, authors should not publicly use the submission title.

● Further advice, guidance, and explanation about the double-anonymous review process can be found in the Q&A page .

● By submitting to the ICSE SEET 2023 Track, authors acknowledge that they conform to the authorship policy of the ACM , and the authorship policy of the IEEE .

Submissions to the ICSE SEET 2023 Track that meet the above requirements can be made via the submission site ( https://icse2023-seet.hotcrp.com ) by the submission deadline. Any submission that does not comply with these requirements may be desk rejected without further review.

We encourage the authors to upload their paper info early (and can submit the PDF later) to properly enter conflicts for double-anonymous reviewing. Authors are encouraged to try out the experimental SIGSOFT Submission Checker to detect violations to the formatting and double anonymous guidelines. (Mind that the tool is based on heuristics. Therefore it may miss violations, and it can raise false alarms. The requirements listed in this call for papers take precedence over the results of the tool when deciding whether a paper meets the submission guidelines.)

Open Science Policy

The SEET track of ICSE 2023 aims to follow the ICSE 2023 Open Science policies. In summary, the steering principle is that research results should be made accessible to the public and empirical studies should be reproducible whenever possible. 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 whenever allowable and applicable. We are aware that some datasets and tools may not be made open and public (e.g., when prohibited by a Non-Disclosure Agreement, when the Ethics Review Board forbids sharing data for participant privacy, when tool source code is commercial-in-confidence, etc.). We also recognize that reproducibility or replicability is not a goal in qualitative research and that, similar to industrial studies, qualitative studies often face challenges in sharing research data. For guidelines on how to report qualitative research to ensure the assessment of the reliability and credibility of research results, see the ICSE 2023 Open Science page . Note that sharing research data is not mandatory for submission or acceptance. However, non-sharing needs to be justified.

We therefore ask all authors to provide a supporting statement on the data availability (or lack thereof) in their submitted papers in a section named Data Availability after the Conclusion section. Authors can also provide anonymized links to anonymized data and repositories in that section or can upload anonymized data using the supplementary material upload option during submission process via the HotCRP submission site ( https://icse2023-seet.hotcrp.com ). Authors who cannot disclose data should provide a short statement explaining the reasons why they cannot share the data in the Data Availability section of their paper, after the Conclusion section.

Upon acceptance, authors have the possibility to separately submit their supplementary material to the ICSE 2023 Artifact Evaluation track , for recognition of artifacts that are reusable, available, replicated or reproduced.

Authors are asked to carefully review any supplementary material to ensure it conforms to the double-anonymous policy employed for ICSE SEET 2023. For example, code and data repositories may be exported to remove version control history, scrubbed of names in comments and metadata, and anonymously uploaded to a sharing site to support review. Below are some resources that can be helpful:

● A step-by-step approach to disclosing artifacts for (doubly-anonymous) peer review and make it open data upon acceptance is available online

● A step-by-step approach to automatically archive a GitHub repository to Zenodo.org is available at https://guides.github.com/activities/citable-code/

● A step-by-step approach to automatically archive a GitHub repository to figshare.com is available at https://knowledge.figshare.com/articles/item/how-to-connect-figshare-with-your-github-account

● A proposal for artifact evaluation by SIGSOFT is available at https://github.com/acmsigsoft/artifact-evaluation

● A proposal for open science in software engineering, including explanations for structuring an open artifact, is available at https://arxiv.org/abs/1904.06499

Important Dates

● SEET Submissions Deadline: 13 October 2022 - Submissions close at 23:59 AoE (Anywhere on Earth, UTC-12)

● SEET Acceptance Notification: 21 December 2022

● SEET Camera Ready: 19 January 2023

Conference Attendance Expectation

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

Contacts

For more information, please contact the ICSE SEET 2023 Co-Chairs:

● Sonia Haiduc, Florida State University, shaiduc@fsu.edu

● Jean-Guy Schneider, Monash University, jean-guy.schneider@monash.edu

.