Requirements engineering (RE) is a critical sub-field of software engineering that deals with identifying, specifying, modeling, analyzing, and validating the needs and constraints of a system. Despite the wide spectrum of activities that the requirements engineering covers, practitioners and researchers alike have often the misconception that RE is limited to writing and analyzing requirements specifications. Consequently, many researchers in the software engineering community conduct research on RE problems but do not explicitly acknowledge it. Therefore, RE is generally under-represented and under-appreciated in the SE community.

The MO2RE workshop represents an opportunity to highlight the multiple facets of RE, clarify its role within the software development process, and bring together the broader SE community where RE is involved–e.g., testing, human aspects. The workshop is a shared place to gather the SE community around RE as a central topic while also hosting contributions from other under-represented areas, closely related to RE (e.g., modelling and system architecture).

We welcome submissions at the intersection of RE and other sub-fields of software engineering, including but not limited to:

• RE for Emerging Technologies (e.g., Quantum Computing)
• RE for Artificial Intelligence
• Applications of (Generative) Artificial Intelligence in RE
• Human Factors of RE
• RE for Society and Sustainability
• Twin-peaks of Requirements and Architecture
• Modeling Requirements and Systems
• Requirements Elicitation, Analysis and Specification
• Requirements Management
• Requirements Verification and Validation
• Requirements for Testing and Security
• RE Education and Training
• RE for Sustainability

The workshop also welcomes submissions that are more specific on RE given the current advances in artificial intelligence (AI) technologies. Specifically, topics including the following:

• How RE can affect the revolution of AI towards more responsible and ethical AI.
• How AI can impact the effectivity and efficiency of RE and software engineering activities.
• Generative-driven AI within the RE spectrum

Research Papers

Max 7 pages for long and 4 pages for short, including references. These papers should describe ongoing research that links RE with the entire spectrum of software engineering. Such papers can describe either a new technical solution or an empirical evaluation. Short papers present preliminary work or research previews, while long papers present more advanced, yet ongoing, studies.

Position Papers

Max 4 pages, including references. These papers serve to foster discussion on emerging, relevant topics that emphasize the multi-facets of RE.

Demo Papers

Max 4 pages, including references. These papers describe a tool that provides automated support in some RE activities. The demo paper should describe a plan for demonstrating the tool at the workshop.

Lightning Talks

Max 2 pages, including references. A lightning talk is a short presentation lasting up to five minutes on a related topic (we would be looking for controversial topics, industry experiences, etc.).

Instructions

• Workshop proceedings will be published in the IEEE Xplore digital library
• The official publication date is the date the proceedings are made available in the ACM or IEEE Digital Libraries. This date may be up to two weeks prior to the first day of ICSE 2025. The official publication date affects the deadline for any patent filings related to published work
• Submissions are single-blind. Authors' name, institution, and contact details should appear on the first page
• Submission should be written in English, formatted according to the ICSE'25 conference template, and submitted in PDF format
• The page limit is strict. Purchases of additional pages in the proceedings is not allowed
• Submissions must conform to the IEEE conference proceedings template, specified in the IEEE Conference Proceedings Formatting Guidelines (title in 24pt font and full text in 10pt type, LaTeX users must use \documentclass[10pt,conference]{IEEEtran} without including the compsoc or compsocconf options).