Authors are invited to submit original, unpublished research papers as well as industrial practice papers. Simultaneous submissions to other publication venues are not permitted.
All papers must conform to the CSEE&T conference proceedings format (PDF | Word DOCX | Latex) and Submission Guidelines set in advance by CSEE&T 2026. They must be in English and in PDF format. Submissions that do not comply with the above instructions will be rejected without review.
Each submission will be reviewed by at least three members of the Program Committee and evaluated on originality, contribution, soundness, presentation, and relatedness. The program committee as a whole will make final decisions about which submissions to be accepted for presentation at the conference.
Accepted papers will be published by the IEEE Conference Publishing Services (CPS). They will also be submitted for inclusion into the IEEE Xplore. In addition, these papers will also appear in Google Scholar and the DBLP database.
Authors are invited to submit papers describing original research in relevant areas of software engineering education and training. Papers presenting actual research results, or in-depth analysis of experience with delivering courses and training units in different settings (schools, universities, industry, governmental entities, etc.), or describing theoretical or empirical research, new techniques and tools, novel interpretation and in-depth case studies, are all welcome. Research papers will be evaluated based on originality, technical quality, and relevance to the field of software engineering education. They should clearly relate the work described to the relevant literature and provide an adequate evaluation.
Each submission can have a maximum of ten pages. It should include a title, the name and affiliation of each author, a 300-word abstract, and up to 6 keywords.
Short paper submissions that address software engineering education and training topics are also invited. They are intended particularly for reports of less substantial work, or of work that is still in progress (such as experience with a particular educational tool or support environment), or they may discuss a promising idea at an early stage, or an idea that may lack complete evaluation. Even so, it is important that short papers relate the work described to the relevant literature and attempt to evaluate it as far as possible. Conclusions should focus on aspects interesting for others working in related areas.
Each submission can have a maximum of five pages. It should include a title, the name and affiliation of each author, a 300-word abstract, and up to 6 keywords.
Journal first submissions present research on software engineering education and training, which has recently been published in high-quality journals. Submissions must clearly give reference to the original publication and state how the topic is related to software engineering education and training, and what the main contribution to be presented is. The original work must be included in the submission as a supplement for reviewing purposes. Only the one-page summary will be published in the conference proceedings.
Each submission can only have one page. It should include a title, the name and affiliation of each author, a 300-word abstract, and up to 6 keywords.
Industrial Experience Reports constitute novel ideas and application of existing approaches in the industry or with very strong industry collaboration. These should cover topics associated with the industry-readiness of graduates and/or training of industry practitioners. Contributions need not be scientifically rigorous, but must systematically outline the benefit of the approach along with preconditions for application to foster repeatability.
Each submission can have a maximum of six pages. It should include a title, the name and affiliation of each author, a 300-word abstract, and up to 6 keywords.
Poster papers constitute a two-page abstract of research results, or analysis of experience with delivering courses and training units in different settings (schools, universities, industry, governmental entities, etc.), or describing theoretical or empirical research, industrial application of new or old techniques and tools, novel interpretation, or case studies. Poster papers will be evaluated based on originality, technical quality, and relevance to the field of software engineering education.
Tool Demo papers constitute a two-page abstract of a tool to support a teaching approach, tools to support delivering courses and training units in different settings, industry tools and their availability to students.
Poster papers will be evaluated based on originality, technical quality, and relevance to the field of software engineering education. Tool papers will be evaluated based on their ability to support instruction, training, education, and learning in the field of software engineering.
