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 30th edition of RE (RE’22) will be hosted (virtually) at Deakin University, Melbourne, Australia, from August 15-19, 2022.
Dates
Tracks
You're viewing the program in a time zone which is different from your device's time zone - change time zone

Wed 17 Aug

Displayed time zone: Hobart change

19:20 - 20:10
Natural Language Processing for RERE@Next! Papers / Journal-First at Dibbler
Chair(s): Tong Li Beijing University of Technology
19:20
20m
Talk
Back to the Roots: Linking User Stories to Requirements Elicitation Conversations
RE@Next! Papers
Tjerk Spijkman Utrecht University, Fabiano Dalpiaz Utrecht University, Sjaak Brinkkemper Utrecht University
19:40
30m
Talk
Empirical evaluation of tools for hairy requirements engineering tasks
Journal-First
Dan Berry University of Waterloo
20:20 - 21:20
Eye Tracking in Requirements EngineeringResearch Papers / RE@Next! Papers at Dunnart
Chair(s): Maria Lencastre Universidade de Pernambuco
20:20
30m
Talk
Enriching Vision Videos with Text: An Eye Tracking Study
Research Papers
Melanie Schmedes Leibniz University Hannover, Maike Ahrens Leibniz Universität Hannover, Lukas Nagel Leibniz University Hannover, Kurt Schneider Leibniz Universität Hannover, Software Engineering Group
20:50
20m
Talk
Telling us your needs with your eyes
RE@Next! Papers
Li Rongchen Beijing University of Technology, Tong Li Beijing University of Technology
20:20 - 21:20
Traceability 1Research Papers / Industrial Innovation Papers at Koala
Chair(s): Chetan Arora Deakin University
20:20
30m
Talk
DizSpec: Digitalization of Requirements Specification Documents to Automate Traceability and Impact Analysis
Industrial Innovation Papers
Asha Rajbhoj TCS Research, Padmalata Nistala TCS Research, Vinay Kulkarni Tata Consultancy Services Research, Shivani Soni TCS Research, Ajim Pathan TCS Research
20:50
30m
Talk
Automated Detection of Typed Links in Issue TrackersAvailable
Research Papers
Clara Marie Lüders University of Hamburg, Tim Pietz Universität Hamburg, Walid Maalej University of Hamburg
21:40 - 22:40
Non-Functional Requirements 1Research Papers at Quokka
Chair(s): Zachary Oster University of Wisconsin-Whitewater
21:40
30m
Talk
A Divide & Concur Approach to Collaborative Goal Modeling with Merge in Early-REReusableAvailable
Research Papers
Kathleen R. Hablutzel Smith College, Anisha Jain Smith College, Alicia M. Grubb Smith College
22:10
30m
Talk
The Implications of "Soft Requirements"
Research Papers
Alistair Sutcliffe University of Aston, Peter Sawyer Aston University, Nelly Bencomo Durham University
21:40 - 22:40
Assurance and AccountabilityJournal-First / Research Papers at Wallaby
Chair(s): Jaelson Castro Universidade Federal de Pernambuco
21:40
30m
Talk
Legal Accountability as Software Quality: A U.S. Data Processing Perspective
Research Papers
Travis Breaux Carnegie Mellon University, Thomas Norton Fordham University
22:10
30m
Talk
How assurance case development and requirements engineering interplay: a study with practitioners
Journal-First
Camilo Almendra Universidade Federal do Ceará, Carla Silva Universidade Federal de Pernambuco, Luiz Eduardo G. Martins Universidade Federal de São Paulo, Johnny Marques Instituto Tecnológico de Aeronáutica

Thu 18 Aug

Displayed time zone: Hobart change

20:20 - 21:20
Mining User FeedbackResearch Papers at Dunnart
Chair(s): Eduard C. Groen Fraunhofer IESE
20:20
30m
Talk
Mining User Feedback For Software Engineering: Use Cases and Reference ArchitectureReusableAvailable
Research Papers
Jacek Dąbrowski University College London & Fondazione Bruno Kessler, Emmanuel Letier University College London, Anna Perini Fondazione Bruno Kessler, Angelo Susi Fondazione Bruno Kessler
20:50
30m
Talk
What's Inside a Cluster of Software User Feedback: A Study of Characterisation MethodsReusableAvailable
Research Papers
Peter Devine The University of Auckland, James Tizard University of Auckland, Hechen Wang The University of Auckland, Yun Sing Koh The University of Auckland, Kelly Blincoe University of Auckland
20:20 - 21:20
ExplainabilityRE@Next! Papers / Research Papers at Koala
Chair(s): Zhi Jin Peking University
20:20
30m
Talk
Requirements on Explanations: A Quality Framework for Explainability
Research Papers
Larissa Chazette Leibniz University Hannover, Verena Klös Technische Universität Berlin, Florian Herzog Graphmasters GmbH, Kurt Schneider Leibniz Universität Hannover, Software Engineering Group
20:50
20m
Talk
Explainability in a Time of Socially Responsible Software
RE@Next! Papers
Roxana L. Q. Portugal UNSAAC, Cusco, Luiz Marcio Cysneiros York University, Julio Cesar Leite PUC-Rio
21:40 - 22:40
RegulationsJournal-First / Research Papers at Quokka
Chair(s): Travis Breaux Carnegie Mellon University
21:40
30m
Talk
Automated Question Answering for Improved Understanding of Compliance Requirements: A Multi-Document StudyBest Paper
Research Papers
Sallam Abualhaija University of Luxembourg, Chetan Arora Deakin University, Amin Sleimi SnT, University of Luxembourg, Lionel Briand University of Luxembourg; University of Ottawa
22:10
30m
Talk
GoRIM: A Model-Driven Method for Enhancing Regulatory Intelligence
Journal-First
Okhaide Akhigbe University of Ottawa, Daniel Amyot University of Ottawa, Gregory Richards University of Ottawa, Lysanne Lessard University of Ottawa
21:40 - 22:40
Requirements Engineering for AIResearch Papers at Wallaby
Chair(s): Seok-Won Lee Ajou University
21:40
30m
Talk
CADE: The Missing Benchmark in Evaluating Dataset Requirements of AI-enabled Software
Research Papers
Mona Rahimi Northern Illinois University, Hamed Barzamini
22:10
30m
Talk
RESAM: Requirements Elicitation and Specification for Deep-Learning Anomaly Models with Applications to UAV Flight Controllers
Research Papers
Md Nafee Al Islam University of Notre Dame, Yihong Ma University of Notre Dame, Pedro Alarcon Granadeno University of Notre Dame, Nitesh Chawla University of Notre Dame, Jane Cleland-Huang University of Notre Dame

Fri 19 Aug

Displayed time zone: Hobart change

19:00 - 20:10
Quality and AssessmentJournal-First / RE@Next! Papers at Bilby
Chair(s): Sallam Abualhaija University of Luxembourg
19:00
30m
Talk
Empirical research on requirements quality: a systematic mapping study
Journal-First
Lloyd Montgomery Universität Hamburg, Davide Fucci Blekinge Institute of Technology, Abir Bouraffa University of Hamburg, Lisa Scholz University of Hamburg, Walid Maalej University of Hamburg
Link to publication DOI Media Attached
19:30
20m
Talk
A Live Extensible Ontology of Quality Factors for Textual RequirementsReusableAvailable
RE@Next! Papers
Julian Frattini Blekinge Institute of Technology, Lloyd Montgomery Universität Hamburg, Jannik Fischbach Netlight GmbH / fortiss GmbH, Michael Unterkalmsteiner Blekinge Institute of Technology, Daniel Mendez Blekinge Institute of Technology, Davide Fucci Blekinge Institute of Technology
Pre-print File Attached
19:50
20m
Talk
Teaching and learning Requirements Engineering concepts: Peer-review skills vs. problem solving skills
RE@Next! Papers
Maria Spichkova RMIT University, Australia
Pre-print
19:00 - 20:10
Artificial Intelligence for RERE@Next! Papers / Research Papers at Dibbler
Chair(s): Rifat Ara Shams CSIRO's Data61
19:00
30m
Talk
Automatic Terminology Extraction and Ranking for Feature Modeling
Research Papers
Jianzhang Zhang Alibaba Business School, Hangzhou Normal University, Sisi Chen Alibaba Business School, Hangzhou Normal University, Hangzhou, China, Jinping Hua Alibaba Business School, Hangzhou Normal University, Hangzhou, China, Nan Niu University of Cincinnati, Chuang Liu Alibaba Business School, Hangzhou Normal University, Hangzhou, China
19:30
20m
Talk
Done is better than perfect: Iterative Adaptation via Multi-grained Requirement Relaxation
RE@Next! Papers
Jialong Li Waseda University, Japan, Kenji Tei Waseda University
19:50
20m
Talk
Retraining a BERT Model for Transfer Learning in Requirements Engineering: A Preliminary Study
RE@Next! Papers
Muideen Ajagbe The University of Manchester, Liping Zhao University of Manchester
20:20 - 21:20
Traceability 2Research Papers / Journal-First at Dunnart
Chair(s): Michael C. Panis Teradyne Inc.
20:20
30m
Talk
Requirements document relations: A reuse perspective on traceability through standards
Journal-First
Katharina Großer University of Koblenz-Landau, Volker Riediger University of Koblenz-Landau, Jan Jürjens University of Koblenz-Landau
20:50
30m
Talk
The Benefits of Pre-Requirements Specification Traceability
Research Papers
Julia Krause Friedrich-Alexander University Erlangen-Nürnberg, Andreas Kaufmann Friedrich-Alexander University Erlangen-Nuremberg, Dirk Riehle University of Bavaria, Erlangen, Martin Jung Friedrich-Alexander University Erlangen-Nürnberg
20:20 - 21:20
Big Data and Business ProcessesIndustrial Innovation Papers / Journal-First at Koala
Chair(s): Fabiano Dalpiaz Utrecht University
20:20
30m
Talk
A Box Analogy Technique (BoAT) for Agile-based Modelling of Business Processes
Industrial Innovation Papers
Carlos Eduardo Da Silva Sheffield Hallam University, Leisia Medeiros Vigil , Yan Justino XP Inc., Eduardo Gomes Wipro Limited
20:50
30m
Talk
ModelOps for enhanced decision‑making and governance in emergency control rooms
Journal-First
Kay Lefevre Deakin University, Chetan Arora Deakin University, Kevin Lee Deakin University, Arkady Zaslavsky Deakin University, Mohamed Reda Bouadjenek Deakin University, Ali Hassani Deakin University, Imran Razzak Deakin University
21:40 - 22:40
Non-Functional Requirements 2Research Papers at Quokka
Chair(s): Daniel Amyot University of Ottawa
21:40
30m
Talk
Narratives: the Unforeseen Influencer of Privacy Concerns
Research Papers
Ze Shi Li University of Victoria, Canada, Manish Sihag University of Victoria, Nowshin Nawar Arony University of Victoria, Joao Bezerra Junior University of Victoria, Thanh Phan University of Victoria, Neil Ernst University of Victoria, Daniela Damian University of Victoria
22:10
30m
Talk
A Case Study of Building Shared Understanding of Non-Functional Requirements in a Remote Software OrganizationAvailable
Research Papers
Laura Okpara University of Victoria, Colin Werner University of Victoria, Adam R Murray University of Victoria, Daniela Damian University of Victoria
21:40 - 22:40
Safety Requirements EngineeringRE@Next! Papers / Research Papers at Wallaby
Chair(s): Xiao Liu School of Information Technology, Deakin University
21:40
30m
Talk
Hierarchical Assessment of Safety Requirements for Configurations of Autonomous Driving SystemsAvailable
Research Papers
Yixing Luo Peking University, Xiaoyi Zhang National Institute of Informatics, Japan, Paolo Arcaini National Institute of Informatics , Zhi Jin Peking University, Haiyan Zhao Peking University, Linjuan Zhang Peking University, Fuyuki Ishikawa National Institute of Informatics
22:10
20m
Talk
Requirements Engineering for Safety-Critical Molecular Programs
RE@Next! Papers
Robyn Lutz Iowa State University

Accepted Papers

Title
A Case Study of Building Shared Understanding of Non-Functional Requirements in a Remote Software OrganizationAvailable
Research Papers
A Divide & Concur Approach to Collaborative Goal Modeling with Merge in Early-REReusableAvailable
Research Papers
Automated Detection of Typed Links in Issue TrackersAvailable
Research Papers
Automated Question Answering for Improved Understanding of Compliance Requirements: A Multi-Document StudyBest Paper
Research Papers
Automatic Terminology Extraction and Ranking for Feature Modeling
Research Papers
CADE: The Missing Benchmark in Evaluating Dataset Requirements of AI-enabled Software
Research Papers
Enriching Vision Videos with Text: An Eye Tracking Study
Research Papers
Hierarchical Assessment of Safety Requirements for Configurations of Autonomous Driving SystemsAvailable
Research Papers
Legal Accountability as Software Quality: A U.S. Data Processing Perspective
Research Papers
Mining User Feedback For Software Engineering: Use Cases and Reference ArchitectureReusableAvailable
Research Papers
Narratives: the Unforeseen Influencer of Privacy Concerns
Research Papers
Requirements on Explanations: A Quality Framework for Explainability
Research Papers
RESAM: Requirements Elicitation and Specification for Deep-Learning Anomaly Models with Applications to UAV Flight Controllers
Research Papers
The Benefits of Pre-Requirements Specification Traceability
Research Papers
The Implications of "Soft Requirements"
Research Papers
What's Inside a Cluster of Software User Feedback: A Study of Characterisation MethodsReusableAvailable
Research Papers

Call for Papers

At the 30th anniversary of the International Requirements Engineering (RE) Conference, RE 2022 welcomes original papers focusing on the traditional RE topics, but this year’s edition is particularly thrilled with the idea of receiving submissions addressing our theme "Building Bridges Between Disciplines: Requirements for Transdisciplinarity". This theme evokes a call to
  
explore the complementary strengths of disciplines from social sciences and engineering fields: We examine the pivotal role RE plays in building bridges between disciplines. RE is a multidisciplinary effort, involving a large set of stakeholders with differing characteristics, strengths, and skill sets. The successful development of large and complex systems requires to routinely cross boundaries of disciplines - from psychology to economics, from physics to mechanical engineering, from life sciences to software engineering.

envision and elaborate novel, innovative ideas, techniques, and processes that integrate and move beyond discipline-specific approaches to address grand societal challenges such as sustainability, equality, and fairness: 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. How can we integrate approaches from other disciplines and apply them to this and to ethical issues, such as sustainability and gender?

Categories for Research Papers:

The RE 2022 Research Track invites original submissions of research papers in three categories: Technical Solution, Scientific Evaluation, and 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 significance, 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 distill novel knowledge, present new insights, and not be 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.

Review Criteria

Papers submitted to the RE 2022 Research Track will be evaluated based on the following criteria:

Soundness: The extent to which the paper’s contributions and/or innovations address its research questions and are supported by rigorous application of appropriate research methods

Significance: The extent to which the paper’s contributions can impact the field of requirements engineering, and under which assumptions (if any)

Novelty: The extent to which the paper's contributions are sufficiently original with respect to the state-of-the-art

Related Work: The extent to which the paper's contributions are appropriately compared to related work

Verifiability and Transparency: The extent to which the paper includes sufficient information to understand how an innovation works; to understand how data was obtained, analyzed, and interpreted; and how the paper supports independent verification or replication of the paper’s claimed contributions

Presentation: The extent to which the paper’s quality of writing meets the high standards of the RE conference series, including clear descriptions, as well as adequate use of the English language, absence of major ambiguity, clearly readable figures and tables, and adherence to the provided formatting instructions.

The RE 2022 Research Track follows a double-blind review process.

Reviewers will carefully consider all of these criteria during the review process, and authors should take great care in clearly addressing them. The authors should clearly explain the claimed contributions, and how they are sound, significant, novel, and verifiable, as described above.

Open Science Policy

The RE 2022 Research Track has an open science policy with the steering principle that all research results should be accessible to the public and, if possible, empirical studies should be reproducible. In particular, we actively support the adoption of open data and open source principles and encourage all contributing authors to disclose (anonymized and curated) data to increase reproducibility and replicability. Note that sharing research data is not mandatory for submission or acceptance. However, sharing is expected to be the default, and non-sharing needs to be justified. We recognize that reproducibility or replicability is not a goal in qualitative research and that, similar to industrial studies, qualitative studies often face challenges in sharing research data. For guidelines on how to report qualitative research to ensure the assessment of the reliability and credibility of research results, see the Q&A page.

Upon submission to the research track, authors are asked

to make their data available to the program committee (via upload of supplemental material or a link to an anonymous repository) – and provide instructions on how to access this data in the paper; or

to include in the paper an explanation as to why this is not possible or desirable; and

to indicate if they intend to make their data publicly available upon acceptance.

Supplementary material can be uploaded via the EasyChair site or anonymously linked from the paper submission. Although PC members are not required to look at this material, we strongly encourage authors to use supplementary material to provide access to anonymized data, whenever possible. Authors are asked to carefully review any supplementary material to ensure it conforms to the double-anonymous policy (described above). For example, code and data repositories may be exported to remove version control history, scrubbed of names in comments and metadata, and anonymously uploaded to a sharing site to support review. One resource that may be helpful in accomplishing this task is this blog post.

Artifacts

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 must be submitted electronically in PDF format via the RE'22 EasyChair system. Select the RE’22 Research Track for your submission.

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.

Please note: Papers that exceed the length specification, are not formatted correctly, or are not properly double-blinded 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.

Instructions for the Double-Blind Review Process

The RE 2022 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.

1. 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.

2. 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.

3. Refer to your own work in the third person, as you would normally do with the work of others. You should not change the names of your own tools, approaches, or systems, since this would clearly compromise the review process; it would also violate the constraint that “no change is made to any technical details of the work”. Instead, refer to the authorship or provenance of tools, approaches, or systems in the third person, so that it is credible that another author could have written your paper. In particular, never blind references.

4. When providing supplementary material (e.g., tools, data repositories, source code, study protocols), do this via a website that does not disclose your identity. Please refer to the Open Science Policy in the Call for Papers with guidelines on how to anonymize such content.

5. Adhere to instruction 3 when citing previously published own work.

6. Remove identification metadata from the PDF file before submission (in Adobe Acrobat Reader, you can check their presence with File Properties, or Ctrl-D).

Important Policy Announcements

Papers submitted to RE 2022 must be original. They will be reviewed under the assumption that they do not contain plagiarized material and have not been published nor submitted for review elsewhere while under consideration for RE 2022.

RE 2022 follows the IEEE policies for cases of double submission and plagiarism



  Submission Instructions in a Nutshell  

Submit your paper with a maximum of 10 pages (main body) + 2 pages (references)

Abstract up to 200 words

Submissions MUST be DOUBLE-blind,

Submissions must be English, in IEEE format

Submit via RE'22 EasyChair (RE’22 Research Track)

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’):

\documentclass[conference]{IEEEtran}


Word users: please use this Word template (official IEEE Templates page for more information).

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
has no orphans and widows (cf. Section Help), and
does not use footnote references in the abstract.

Empirical Studies and Sharing of Data

I am doing research with industry. What if I cannot share data from my research? We absolutely welcome research with industry, as it often conveys important lessons about requirements engineering in practice – and we perfectly understand that industry data may be subject to confidentiality issues or legal requirements. If you cannot share data, please state the reason in the submission form and the paper; a typical wording would be "The raw data obtained in this study cannot be shared because of confidentiality agreements". Having said that, even sharing a subset of your data (for instance, the data used for figures and tables in the paper, an anonymized subset, or one that aggregates over the entire dataset), analysis procedures, or scripts, would be useful.

I am doing user studies. What if I cannot share data from my empirical study? We absolutely welcome user studies! However, we also perfectly understand that sharing raw data can be subject to constraints such as privacy issues. If you cannot share data, please state the reason in the submission form and the paper; a typical wording would be "The raw data obtained in this study cannot be shared because of privacy issues". Having said that, even sharing a subset of your data (for instance, the data used for figures and tables in the paper, an anonymized subset, or one that aggregates over the entire dataset), analysis procedures, or scripts, would be useful.

I am doing qualitative research. What information should I include to help reviewers assess my research results and the readers use my results? Best practices for addressing the reliability and credibility of qualitative research suggest providing detailed arguments and rationale for qualitative approaches, procedures, and analyses. Therefore, authors are advised to provide as much transparency as possible into these details of their study. For example, clearly explain details and decisions such as 1) context of study, 2) the participant-selection process and the theoretical basis for selecting those participants, 3) collection of data or evidence from participants, and 4) data analysis methods, e.g., justify their choice theoretically and how they relate to the original research questions, and make explicit how the themes and concepts were identified from the data. Further, provide sufficient detail to bridge the gap between the interpretation of findings presented and the collected evidence by, for example, numbering quotations and labeling sources. Similar to replicability in quantitative research, transparency aims to ensure a study’s methods are available for inspection and interpretation. However, replicability or repeatability is not the goal, as qualitative methods are inherently interpretive and emphasize context. As a consequence, reporting qualitative research might require more space in the paper; authors should consider providing enough evidence for their claims while being mindful with the use of space.

Finally, when qualitative data is counted and used for quantitative methods, authors should report the technique and results in assessing rigour in data analysis procedures, such as inter-reliability tests or triangulation over different data sources or methods, and justify how they achieved rigour if no such methods were used.

I can make my data set / my tool available, but it may reveal my identity. What should I do? See this question under "double-anonymous submissions", below.

Double-Blind Submissions

I previously published an earlier version of this work in a venue that doesn’t have double-anonymous. What should I do about acknowledging that previous work? If the work you are submitting for review has previously been published in a peer-reviewed venue or in a non-peer-reviewed venue (e.g., arXiv.org, or a departmental technical report), then it should be cited but in the third person so that it is not revealed that the cited work and the submitted paper share one or more authors.

Our submission makes use of work from a PhD or master’s thesis, dissertation, or report which has been published. Citing the dissertation might compromise anonymity. What should we do? It is perfectly OK to publish work arising from a PhD or master’s degree, and there is no need to cite it in a submission to the RE Research Track because prior dissertation publication does not compromise novelty. In the final post-review, camera-ready version of the paper, please do cite the dissertation to acknowledge its contribution, but in any submission to the RE Research Track, please refrain from citing the dissertation to increase anonymity. You need not worry whether or not the dissertation has appeared. Your job is to ensure that your submission is readable and reviewable, without the reviewers needing to know the identities of the submission’s authors. You do not need to make it impossible for the reviewers to discover the authors’ identities. The referees will be trying hard not to discover the authors’ identity, so they will likely not be searching the web to check whether there is a dissertation related to this work.

What if we want to cite some unpublished work of our own (as motivation for example)? If the unpublished paper is an earlier version of the paper you want to submit to the RE Research Track and is currently under review, then you have to wait until your earlier version is through its review process before you can build on it with further submissions (this would be considered double-submission and violates plagiarism policies and procedures). Otherwise, if the unpublished work is not an earlier version of the proposed submission, then you should simply make it available on a website, for example, and cite it in the third person to preserve anonymity, as you are doing with other work.

Can I disseminate a non-anonymized version of my submitted work by discussing it with colleagues, giving talks, publishing it at ArXiV, etc.? You can discuss and present your work that is under submission at small meetings (e.g., job talks, visits to research labs, a Dagstuhl or Shonan meeting), but you should avoid broadly advertising it in a way that reaches the reviewers even if they are not searching for it. Therefore, the title of your submission must be different from preprints on ArXiV or similar sites. During review, you must not publicly use the submission title. Under these conditions, you are allowed to put your submission on your home page and present your work at small professional meetings.

What if we want to make available a tool, a data set, or some other resource, but it may reveal my identity? Please refer to the Open Science Policy in the Call for Papers with guidelines on how to anonymize such content. If that is impossible, place a warning next to the link that this may reveal your identity.

Thank you Daniela Damian and Andreas Zeller for sharing ICSE 2022 FAQs.