The IEEE International Requirements Engineering Conference (RE) is the premier requirements engineering conference where researchers, practitioners, students, and educators meet, present and discuss the most recent innovations, trends, experiences and issues in the field of requirements engineering. The 29th edition of RE (RE’21) will be hosted at the University of Notre Dame (USA), from September 20-24, 2021.
Call for Papers
The RE’21 welcomes original papers focusing on the traditional RE topics, but this year’s edition is particularly thrilled with the idea of receiving submissions addressing the following five research themes:
1 - Discover stakeholders’ needs:
As software systems get more complex and intertwined with society, discovering the needs of various stakeholders remains one of the fundamental missions of requirements engineering. Techniques, tools, and insights are a contribution that cuts across all applications and domains.
2 - Societal Challenges:
Software is no longer a purely technical device or product. Its enormous power and potential continue to shape society, affecting human values and our ways to live our lives. Working from home and online teaching was imposed on us by the COVID-19 crises. How are requirements related to this and to ethical issues, such as sustainability and gender? Where are we going?
3 - Smart and connected: Our world has developed into a huge socio-technical system of systems. Software with intelligent capabilities is linked to human activities and organizational systems. In smart cities, a smooth collaboration between human goals and technical sophistication is on the horizon.
4 - Agile, DevOps, and Hybrid:
Requirements engineering activities and customer satisfaction are at the core of agile development. However, the interplay between RE and development has shifted. Requirements are not as explicit and as visible in iterative approaches driven by direct communication. Most companies mix and match agile and DevOps with proven techniques. Where is the sweet spot?
5 - AI + RE:
AI seems to be everywhere and ready to solve problems even humans could not solve before. However, what are the problems to be solved? Who decides, controls, and explains whether requirements set by stakeholders are effectively transformed into AI solutions? Can AI itself help to do that?
The RE’21 Research Track invites original submissions of research papers in three categories: Technical Solution, Scientific Evaluation, Perspective.
Technical solution papers present solutions for requirements-related problems that are novel or significantly improve on existing solutions. This includes new algorithms or theory, novel tools, modeling languages, infrastructures, or other technologies. All requirements-related activities, such as elicitation, prioritization or analysis are in scope. These papers are mainly evaluated with regard to problem relevance, novelty in comparison with existing work, clarity of presentation, technical soundness, and evidence for its benefits.
Scientific evaluation papers evaluate existing problem situations or real-world artifacts, or they validate or refute proposed solutions by scientific means. This includes experiments, case studies, and surveys reporting qualitative and quantitative data and findings. The papers are mainly evaluated with regard to the soundness of research questions and appropriateness and correctness of study design, data analysis, and threats to validity. Replications are welcome. Lessons learned can be particularly important to complement other empirical results.
Perspective papers explore the history, successes, and challenges of requirements related practices and research agendas, and outline research roadmaps for the future. Literature reviews are also included in this category and must distil novel knowledge, present new insights and not a mere compilation. These papers are evaluated based on the insights they offer to the reader and the corresponding arguments, and on their potential to shape future research.
Each paper will be reviewed by at least three members of the Program Committee, based on the criteria for the respective category. In general, originality, importance of contribution, soundness, evaluation, quality of presentation, and appropriate comparison to related work are important.
The authors of accepted papers will have the opportunity to increase the visibility of their artifacts (software and data) and to obtain an artifact badge. Upon acceptance, the authors can submit their artifacts, which will be evaluated by a committee that determines their sustained availability and reusability.
Papers should be submitted electronically to the EasyChair system. In order to guide the reviewing process, all authors who intend to submit a paper must first submit the title and abstract. Abstracts should describe explicit coverage of context, objectives, methods, and results and conclusions, and should not exceed 200 words.
Papers must describe original work that has not been previously published or submitted elsewhere. Papers must not exceed 10 pages for the main body and up to 2 additional pages for the references. Submissions must be written in English and formatted according to the IEEE formatting instructions. Submissions must be double-blinded in conformance with the instructions below.
Papers exceeding the length specification, are not formatted correctly, or are not properly double-blinded (see instructions below) will be desk-rejected without review.
Only full paper submissions will be peer-reviewed. Abstract-only submissions will be discarded without further notice after the submission deadline.
Accepted papers may require editing for clarity prior to publication and presentation. They will appear in the IEEE Digital Library.
Please submit your Research paper in PDF format via EasyChair. Select the RE’21 Research Track for your submission.
The RE’20 Research track will use a double-blind reviewing process. The goal of double-blind reviewing is to ensure that the reviewers can read and review your paper without having to know who any of the authors are, and hence avoid related bias. Of course, authors are allowed and encouraged to submit papers that build on their previously published work.
In order to prepare your submission for double-blind reviewing, please follow the instructions given below.
Omit all names and affiliations of authors from the title page, but keep sufficient space to re-introduce them in the final version should the paper be accepted.
Do not include any acknowledgements that might disclose your identity. Leave space in your submission to add such acknowledgements when the paper has been accepted.
Refer to your own work in the third person, as you would normally do with the work of others.
When providing supplementary material (e.g., data repositories, source code, study protocols), do this via a website that does not disclose your identity.
Anonymize the names of your own tools, approaches or systems, in a way that can be reversed should the paper be accepted.
When anonymizing your paper, make sure not to compromise the technical integrity of your work. In particular, never blind references.
Adhere to instruction 3 when citing previously published own work.
Remove identification metadata from the PDF file before submission (in Adobe Acrobat Reader, you can check their presence with File Properties, or Ctrl-D). Microsoft Word users should follow the Document Properties and Personal Information section of these instructions.
Papers submitted to RE 2021 must be original, and will be reviewed under the assumption that they do not contain plagiarized material, have not been published nor submitted for review elsewhere while under consideration for RE 2021.
RE 2021 follows the IEEE policies for cases of double submission and plagiarism
The format of your paper must strictly adhere to the IEEEtran Proceedings Format.
LaTeX users: please use the LaTeX class file IEEEtran v1.8 and the following configuration (without option ‘compsoc’ or ‘compsocconf’):
Please make sure that your submission
does not exceed the respective page limit specified in the track call
is in PDF format,
is in letter page size,
does not have page numbers,
has all fonts embedded in the PDF file,
uses only scalable font types (like Type 1, TrueType) --- bit-mapped font types (like Type 3) are not acceptable,
has all figures embedded in vector graphics (if not possible, use a high-resolution bitmap format of at least 300 dpi; do not use JPG, but a lossless format like PNG or GIF),
has all text in figures and tables large enough and readable when printed,
has a caption for every figure or table,
has the title and all headings properly capitalized