The 6th International Workshop on Crowd-Based Requirements Engineering (CrowdRE'22)

15 August 2022
Virtual Conference
In conjunction with RE 2022


Submission site: EasyChair

Submission deadline: 26 May 2022 AoE time, strict!

We welcome original submissions from research and practice in the following categories:

  • Technical solution papers providing research results with an early validation, which may include tool showcases (4–6 pages + 1 page for references).
  • Experience reports providing insights on existing RE practice and potential for application in settings that involve a crowd (4–6 pages + 1 page for references).
  • Problem statements explaining industry problems in settings with a large group of stakeholders (2–3 pages).
  • Vision statements explaining exploratory ideas, especially towards technology transfer into practice (2–3 pages).
  • Conference-first extended abstracts of recent conference contributions that fit CrowdRE's themes (1 page). Only CrowdRE-related papers published in conferences other than the RE conference and its collocated events are eligible.

Submissions must describe original works that have not been previously published (except for conference-first extended abstracts), are not currently submitted elsewhere, and address at least one of the workshop topics listed below.

Submissions must be written in English and formatted according to the IEEE formatting instructions. All accepted papers will be published in the joint RE 2022 workshop proceedings.

At least one author of every accepted manuscript is expected to attend the entire workshop and present their research.

Important Dates
  • Abstract Submission: 12 May 2022
  • Paper Submission: 26 May 2022 (Extended!)
  • Notification: 17 June 2022
  • Camera Ready: 7 July 2022
  • Workshop: 15 August 2022

All deadlines at 23:59:59 AoE.

Workshop Topics

The following themes of interest for paper submission include, but are not limited to, the following topics. However, each paper should address at least one of these topics:

  • Crowd-based Requirements Engineering (CrowdRE)
  • Analysis of user feedback for RE using Big Data and mining
  • Natural language processing, Information Retrieval, (supervised and unsupervised) Machine Learning, ontologies
  • Crowd-based monitoring and usage mining approaches
  • Case studies and Use Cases involving CrowdRE
  • Process descriptions of implementing or performing CrowdRE
  • Method descriptions that can be applied in CrowdRE
  • The role of the requirements engineer in CrowdRE
  • Contributions of CrowdRE to RE and to software engineering
  • The intersection of RE and domains such as sociology, psychology, human factors, and anthropology
  • Approaches to motivate, steer, and boost creativity in the crowd and understand, diversify and engage a crowd for RE
  • Automated RE and data (safeguarding rollback, privacy, traceability and data integrity; measuring validity, reliability, source quality; processing of rejected data)
  • Platforms and tools supporting CrowdRE

Key Questions and Themes of Interests

Submitted papers should ideally provide contributions relevant to answering one or more of the following key questions that CrowdRE will mainly focus on:

Motivation of Users in CrowdRE:
  • What are suitable CrowdRE approaches to motivate users to actively participate and provide feedback?
  • How can strategies in CrowdRE look like and be applied to motivate users of a (software) product to actively participate and provide feedback?
  • How can CrowdRE learn from other disciplines such as marketing, public relations, or advertising to increase users’ interest and motivation to actively participate?
CrowdRE and Human Values:
  • What are the effects of human values in CrowdRE on individual stakeholders, their contribution to RE, and on the crowd as a whole?
  • How does CrowdRE contribute to understand and handle the diversity of a crowd and the human values of all crowd members?
  • What are suitable CrowdRE approaches and technologies used to ensure human values in (1) a (software) product or (2) one or more of the four key activities of CrowdRE for all its crowd members?