Call for contributions
Software Engineering Education and Training
Education in Research and Research in Education
Aims and Scope
Synergy between research and education is the key premise of a research university. Many of us play dual roles as software engineering researchers and software engineering educators. Sometimes we happily achieve that synergy, but as often we encounter tension between the roles. Can we bring the same rigor and creativity to software engineering education and educational research that we bring to software engineering research? Can our educational efforts profit our research, and vice versa?
And given the increasing synergy between research and practice, how can we effectively transfer to future generations of software engineers the competencies that are right for a society that increasingly needs them? Can research collaboration with industry help education, too?
Topics of Interest
We are looking for contributions that address challenges, innovations, and best practices in software engineering education and training. We welcome submissions on all topics related to software engineering education and training. We are particularly interested in submissions that combine software engineering research with research in software engineering education. We are open to a wide range of topics, including (but not limited to):
- new best practices for software engineering education and training;
- innovative curriculum or course formats;
- innovative and unconventional education platforms;
- software engineering as applied to other domain disciplines, such as liberal and fine arts, natural and behavioural sciences, and various forms of engineering;
- individual and (multidisciplinary) team development;
- individual, social and cultural issues;
- software engineering education and ethics;
- software engineering in non-traditional settings such as hackathons and living labs;
- emerging educational settings for software engineering such as online learning;
- global and distributed software engineering;
- methodological aspects of software engineering education;
- educational research methods in software engineering education and training;
- research and practice synergies for software engineering education
Format and Submissions
- Full papers, up to 10 pages, documenting results and findings, where the research presented has followed appropriate research methods;
- Short papers, up to 4 pages, reporting novel approaches that have not been fully evaluated, which will be presented as posters;
- Case study papers, up to 10 pages, reporting on innovative approaches, courses, tools, or delivery formats;
- Panel session proposals, up to 4 pages, which describe the topic to be discussed, explain why this topic will be of interest and give details of the proposed panel membership.
Please note that ICSE 2018 SEET has introduced a double-blind review process, which also imply some requirements on your writing style. For more details see please author tips and ICSE 2018 double blind review process description.
Each submission will be reviewed by at least three members of the program committee. Submissions must not have been previously published or concurrently submitted elsewhere. Selections will be made on the basis of originality, significance of contribution, soundness and appropriateness of research methods (as applicable), relation to the goals listed above, relevance for the ICSE audience, discussion of related work, and quality of presentation.
Accepted papers and panel summaries will be published in the ICSE 2018 Companion Proceedings and in the ACM and IEEE digital libraries. The official publication date of the proceedings is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work.
- Submissions deadline: 23 October 2017
- Notification of reviewing decisions: 22 January 2018
- Camera ready due: 23 February 2018
As a track of ICSE, the premier research conference in software engineering, we seek papers of high quality that improve the state of knowledge and practice in software engineering education and training. Your submission to the SEET track will be reviewed by at least three experts in the field, who will do their best to provide you useful feedback and a clear explanation of why they did or did not support it for publication. You can help them in their reviewing task, and improve the chance of your paper being accepted, by following these guidelines:
Omit author and institution identification
ICSE 2018 is using a double-blind reviewing process. Do not include author names and affiliations on your paper, and avoid any unnecessary identification by other means (e.g., a self-citation beginning “in our previous work”). ICSE SEET author identity will not be revealed to reviewers until after paper acceptance decisions have been made. However, our process is “lightweight” in the sense that you do not have to scrub every potential clue that a reviewer familiar with work coming from a particular institution or group of authors might use to make an educated guess regarding authorship.
Clearly identify your contribution and claims
A reviewer will be more likely to appreciate and properly evaluate your contribution if you state it explicitly. Sometimes it is also useful to clarify what you are not claiming.
Provide appropriate evidence or argument
Different contributions require different kinds of evidence or argument, and one of the things a reviewer will consider is whether the evidence or argument you have provided is appropriate to your claims.
Anticipate and assess potential perceived weaknesses
No study is perfect, no argument is air-tight, and no experiment is entirely without threats to validity. Anticipate the doubts a critical reader of your paper might have, and address them frankly and openly.
Relate your work to the field
A good related work section does not just list related work; it guides the reader to a better understanding of how the current paper contributes to the overall development of the field, and how it builds on what went before. A clear related work section gives a reviewer more confidence in your contribution by showing that you have the bigger picture.