ESEM Industry, Government, and CommunityESEIW 2023
Submission: Tuesday, May 23, 2023
Notification: Friday, June 23, 2023
Camera ready: Friday, July 7, 2023
Andrew Begel Carnegie Mellon University
Dan Port University of Hawaii, Manoa
The ESEM IGC track is one of the major forums for practitioners and researchers to share their experiences and disseminate results concerning the experience of applying or evaluating software engineering technologies (process, methods, techniques and tools) in real settings. It provides an opportunity for practitioners and researchers to exchange new ideas and develop new collaborations. Submissions to this track must include at least one non-academic author who has made a material contribution to the work. Submissions to this track will be peer-reviewed mainly for relevance, substance, and interest to the conference rather than for “academic” rigor. We encourage submissions written by practitioners for practitioners.
Some areas of interest include, but are limited to:
- Case studies of development practice
- Use of advanced tools or methods (e.g., AI)
- Product development interactions with non-Engineers
- Issues with Maintenance, DevOps, CI
- Management of large-scale services and frameworks
- War stories
- Assessment and/or self-improvement of processes, tools, or practices
- Metrics and Measures Used in Practice
- Progress towards internal goals or metrics
- Reports on Best Practices
- Empirical Assessment of Technical Management
- Translation of research into practice and vice versa
- Adaptation and use of research tools (no matter how old) in practice
- Lessons learned applying academic research to practice (what worked, what didn’t work)
- Explaining current problems that need to be addressed by research
- Compliance and Regulations
- GDPR, CCPA, and other Privacy Regulations
- Community Participation
- Community Service Projects and Outreach
- Participation in open source communities
- Participation in standards bodies and RFCs
- Workforce assessment and advancement
- Education to workforce pipeline (needs, outcomes, preparation)
- Onboarding, Training, and Technical workforce development
- Diversity, Equity, Inclusion, and Belonging
- Opportunities for collaborations
We seek the following types of submissions:
This type of submission is only open to industry, government, or community practitioners. Submissions should describe experiences that may help understanding situations in which practices or technologies are applied and their impact. Experience reports on implementing practices or technologies suggested or driven from research are especially encouraged. Experience reports should include information on the setting, provide motivation, explain the events leading to the outcomes including the challenges faced, summarize the outcomes, and conclude with lessons learned, take-away messages, and advice based on the described experience. An extensive description of related work or background material is not required. However, references to relevant research is appreciated. Accepted submissions will be invited to present their report at the conference and a summary will be included in the conference proceedings.
Experience Reports submissions should provide a 2-4 page summary of the experience.
Submissions should describe empirical studies conducted in industry, government, or community settings (e.g., action research, case studies). We encourage the submission of novel studies, replication studies, and studies with negative results (i.e., studies that did not deliver the expected results). Submissions should describe related work, provide details on the approach and methodology employed, and discuss implications of the results.
For Empirical Studies, we accept both full papers (6-10 pages) and short papers (4-6 pages).
IGC Challenge Workshop Session
This type of submission is only open to practitioners. IGC challenge submissions outline a new research challenge, arising from software practice and experience. The submission should clearly articulate the problem and motivate it in terms of its potential for industrial impact and/or its practical importance. The aim is to provide a well-defined industrially relevant problem for the research community to tackle. Submissions should include a brief background and describe a problem or area that is in need of empirical study, and a list of questions/challenges to be discussed. Accepted submissions will be given an opportunity to conduct a workshop session at the conference to discuss the problem and solicit potential collaborations. Submissions are limited to 2-pages and must use the following outline:
BackgroundBrief background of the organization and context
Problem(s)Description of problem or areas in need of empirical study
Discussion PointsBullet point list of questions, challenges, and requests. Put these in order of priority as there will be limited time in the workshop and not all discussion points will be addressed. The objective here is to stimulate interest and possible collaborations.
Page limits include figures, tables, appendices. One additional page may be used for references.
Submissions must include an additional section, a Lay Abstract: a 250-word summary of the paper written in plain English, intended to be read not by researchers, but by practicing software engineers or community members, who may have very little understanding of software engineering research or academic jargon. This will help make our work more accessible to the public, an important constituency and focus of our research. The Lay Abstract should come after the Abstract but before the paper’s Introduction section.
It is not required to publicly reveal data or data sources. However, submissions should provide a statement indicating the provenance of the data and its appropriate use in the study/report.
Submissions must be submitted via EasyChair by selecting the “IGC Track”. Details on how to submit and format your paper can be found at submission link.