The 30th IEEE International Requirements Engineering Conference (RE ’22) is the premier international forum for industrial practitioners, researchers, educators, and students for discussing the most recent innovations, experiences, and concerns in the discipline of Requirements Engineering. The RE ’22 industry track will feature full industry papers, presentation-only contributions, invited presentations, and interactive formats.
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
Pre-print
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 Mucha 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 CESAR, CESAR School, 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 (Zane) 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, Xiao-Yi 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

Call for Papers

Topics of Interest

The industry track accepts the following types of industrial contributions: Problem statement papers describe a significant challenge that has been encountered in industry and has not been satisfactorily solved. Vision papers propose a solution and a research or innovation roadmap for addressing a significant challenge experienced in the industry. Experience report papers report on the innovative application of a concept, method, or framework in one or several interesting industrial contexts, including the lessons learned. As mentioned above, the track welcomes full industry papers and presentation-only submissions.

Topics may include, but are not limited to, the following:
 

Innovation with Requirements Engineering

  • Use of requirements engineering to address societal, economic, or corporate challenges
  • Use of requirements engineering to leverage emerging technologies such as Big Data, Artificial Intelligence, IoT, 5G, or Blockchain
  • Requirements engineering for ensuring the trustworthiness and fairness of AI-enabled systems
  • Innovation through networking, community-building, and creativity
  • Enablement of value chains or software ecosystems

Stakeholder Management

  • Requirements elicitation and negotiation
  • Work in multi-party consortia or geographically dispersed teams
  • Involvement of the crowd for requirements elicitation, analysis, and validation

Pragmatic Requirements Engineering

  • Good-enough requirements engineering
  • Agile and lean approaches
  • Domain-specifics and special contexts for requirements engineering such as Open-source or API development

Requirements Specification

  • Natural language
  • Formal and model-driven approaches
  • Work on complex systems or product lines
  • Traceability

Addressing Quality with Requirements Engineering

  • Ethics, compliance, and risk management
  • User experience, privacy, safety, and security
  • Sustainability
  • Approaches for requirements testing, validation, and impact management

Product Lifecycle Management

  • Value creation techniques
  • Product planning and evolution
  • Dissemination and cooperation with media, marketing, sales, and support

Industry Experiences of Requirements Engineering

  • Deploying new or improved processes
  • Transferring technology from academia to industry or within industry
  • Tooling for requirements engineering or management
  • Training and certification for practitioners
  • Learning from practice and improving productivity
  • Identifying industry best practices and benchmarks

We invite both practitioners and researchers with significant industry experience to submit original contributions reporting on requirements engineering challenges, innovations, and experience within industrial, government, and open-source settings.
 
Full industry papers may be up to 10 pages long, plus 1 additional page for references, and will be peer-reviewed. The accepted papers will be included in the IEEE proceedings for the conference and presented at RE’22.
 
Presentation-only submissions recognize that practitioners often perform innovative work that would be valuable to share but do not publish it in paper form. We, therefore, accept presentations of strong work performed in the industry at RE’22 based on the submission of a set of annotated draft slides (full paper not necessary). These presentations will be peer-reviewed and will not be eligible for publication in the conference proceedings.
 

RE’22 will provide you with an opportunity to share interests and discuss ideas with fellow practitioners and researchers. You will join the global network of requirements engineering experts across industry and academia and have a chance to influence the development of the field.

For further information and Word/Latex templates please check here (the same formatting instructions apply as for the Research Track).


Submission Instructions in a Nutshell
  • Submit your full industry paper with a maximum of 10 pages (main body) + 1 page (references) - Will be reviewed and published (if accepted)
  • Submit your presentation-only submission annotated draft slides - No paper necessary, will not be published
  • Submissions are SINGLE-blind (that is, authors are not required to make their submissions anonymous)
  • Submissions must be English, in IEEE format (for full papers)
  • Submit via EasyChair ( “RE’22 Industrial Innovation" option)

Guidelines for Full Industry Papers

Industry papers must be based on a strong connection to the industrial context. They should adhere to the following guidelines.

 

Clearly describe the context of the problem and why a practical solution is important to the industry. Indicate who has been impacted, for how long time, how new the problem is, and what the trigger of the problem is.

 

Identify prior work. You are not expected to have performed a systematic literature review as you would for the research track. However, identify if you are applying your own or someone else’s previously published ideas. Cite this related work.
 
Explain what you did and the results you have obtained. What were the environment and the problem that you have investigated? How did you develop and apply any solutions? What were the results, impact, and lessons learned? Provide concise descriptions and rationales for your choices.
 
Describe your findings with supporting data, and do not base your arguments on just your personal opinion or conjecture. Industry track papers may be based on topics for which there was originally no expectation of writing a paper and consequently no controlled data gathering. Use the data you have and collect inputs and opinions from those who were involved.
 
Discuss what makes your contribution innovative. significant, and useful for industry. To explain what is new, compare your results with relevant alternatives. If the findings were negative, provide a thorough discussion of the potential causes of failure, and ideally a perspective on how to solve them.

Guidelines for Presentation-only Submissions

While “presentation-only” authors will not be required to submit full papers, they will still need to work with the industry track program committee to demonstrate that their presentation will meet the criteria of full papers. For example, authors must be able to substantiate any claims made in their presentation. They will be required to submit draft slides with annotations in the notes section of the slides. Especially for slides that use graphics or photos, the authors should elaborate on the key messages they will provide in the notes section of this slide. Further, the authors shall provide a brief biography, their company information, and the category of the presentation (problem statement, experience report, innovative method, or vision) in the notes section of the first slide or in attached slides at the end of the presentation. The slideset should correspond to a presentation slot of approximately 20 minutes. Similar to full papers, at least one author will be required to register for and participate in the conference. Presentations must describe original work that has not been previously published or submitted elsewhere. Submissions must be written in English. You may reference additional content (i.e., data repositories, source code for open source tools, etc.) by providing a corresponding URL hosted on an institutional, archive-grade site in the notes section.

 

What is the Difference between Research and Industry Track Papers?

Authors sometimes ask for guidance as to the track to which they should submit their paper.

Both Research and Industry Track papers are expected to meet the same high standards required by IEEE for published papers, but they are evaluated using different criteria. To ensure its best chance for acceptance, a paper must be submitted to the appropriate track. The following examples are by no means exhaustive, but shall provide

Example papers that should be submitted to the Research Track

  • A review of previous research or literature on a given topic
  • A proposed new technique that industry could employ in the future, based on interviews with a company’s employees and analysis of data
  • A proposed new technique that industry could employ in the future, based on a trial in an industrial setting with simulated data
  • An exploration of the history, successes, and challenges of requirements related practices and/or vision of future directions based on the author’s work with practitioners

Example papers that could be submitted to the Research or Industry Track

  • An analysis of the state of the art across multiple companies
  • A description of the practices of a particular company by an employee or non-employee (e.g. a consultant or independent researcher)

Example papers that should be submitted to the Industry Track

  • A proposed new technique that industry could employ in the future, based on a practitioner’s work experience
  • A proposed new technique that industry could employ in the future, based on a trial in an industrial setting performed by practitioners doing their daily work
  • The deployment of an existing or new technique to practitioners doing their daily work, regardless of failure or success
  • An exploration of the history, successes, and challenges of requirements related practices and/or vision of future directions based on the author’s work as a practitioner