Write a Blog >>
ICSE 2022
Dates and location to be announced

Call for Papers

Many people can code, but only some are software engineers. Becoming a software engineer requires the acquisition of a balanced set of soft and technical skills. This special skill set enables software engineers to solve real-world problems. While working in teams, they are capable of developing complex software systems and evolving them gracefully. Their focus is on quality and catering to users’ needs. There are many paths that could be taken and combined to acquire the required skill set: from formal education to on-the-job training, online and offline, from coding clubs to boot camps, by watching online videos and participating in online programming contests. How do we best support our students in their journey to become software engineers?

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

Topics of Interest

ICSE SEET 2022 seeks original contributions covering all dimensions of learning and teaching software engineering. 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 and industrial training. Topics of interest include, but are not limited to:

  • Foundational research on software engineering skills

  • Methods of teaching 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 of software engineers

  • Use of online platform for software engineering education

  • Introducing software engineering in coding clubs targeting children, 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 page 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 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, Learnability, 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 are defined as follows:

  • Relevance: To what extent the submission 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: How well 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.

  • Learnability: 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 at ICSE.

  • 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 ICSE 2022 formatting and submission instructions 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.

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 ((https://www.acm.org/publications/policies/plagiarism and the IEEE Plagiarism FAQ (https://www.ieee.org/publications/rights/plagiarism/plagiarism-faq.html). In particular, papers submitted to ICSE 2022 must not have been published elsewhere and must not be under review or submitted for review elsewhere whilst under consideration for ICSE 2022. 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 (https://www.acm.org/publications/policy-on-authorship), and the authorship policy of the IEEE (https://journals.ieeeauthorcenter.ieee.org/become-an-ieee-journal-author/publishing-ethics/definition-of-authorship/).

SEET will use a doubly anonymous review. Be sure to remove the list of authors from the submitted paper. If citing your own prior work, please do so in the third person to obscure the relationship you have with it.

All papers must be written in English. All papers should be made accessible to people with disabilities. See some guidelines from the folks at SIGACCESS here: https://assets21.sigaccess.org/creating_accessible_pdfs.html.

All contributions must be submitted to HotCRP at: https://icse2022-seet.hotcrp.com/

Important Dates

  • SEET Submissions Deadline: 22 October 2021
  • SEET Acceptance Notification: 14 January 2022
  • SEET Camera Ready: 11 February 2022

Conference Attendance Expectation

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

Contacts

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