The 33rd IEEE International Requirements Engineering Conference (RE’25) will continue the successful tutorial program of the RE conference series. RE’25 tutorials will focus on various requirements-related topics of interest to industry, academia, and government. Tutorial attendees can expect to leave a tutorial with new ideas and skills applicable to their profession or research area.

We invite you to submit proposals for full-day (approx. 7-hour) or half-day (approx. 3.5-hour) tutorials.

Call for Tutorial Proposals

We welcome tutorial proposals related to requirements engineering and business requirements analysis, including but not limited to the topics below:

• Requirements elicitation, analysis, documentation, verification, and validation
• Requirements management, traceability, viewpoints, prioritization, and negotiation
• Evolution of requirements over time and across product families
• Requirements specification languages, methods, processes, and tools
• Prototyping, simulation, visualization, and animation of requirements
• Requirements alignment with business goals, architecture, design, implementation, and testing
• Social, cultural, global, personal, and cognitive factors
• Domain-specific problems, experiences, and solutions
• Managing requirements-related complexity (e.g., problem complexity, solution complexity, organizational complexity, etc.)
• Requirements engineering as part of agile or DevOps development processes
• Requirements engineering for service-oriented and cloud/fog computing systems
• Requirements related to safety, reliability, security, privacy, ethics, and digital forensics
• Requirements engineering for Digital Twins, IoT, or Blockchain
• Requirements engineering for Big Data, Artificial Intelligence, Machine Learning
• Requirements engineering for data sharing/data lakes/data mesh
• Data/process mining for requirements engineering
• Requirements engineering for sustainability
• Distributed requirements engineering
• OpenScience initiatives in Requirements engineering
• Improving requirements engineering practices with large language models (LLMs)

Tutorial Proposal Evaluation Criteria

Evaluation criteria include the quality of the proposal, the tutorial’s anticipated benefit for prospective participants, its fit within the program as a whole, and the qualification and experience of the presenter(s).

Tutorial proposals should not exceed two pages (not counting appendices) and must be submitted via EasyChair submission page in PDF. Make sure you select “Tutorials”.

Tutorial proposals should contain the following information:

Title and Abstract:

The abstract should be between 140 and 250 words. If the proposal is accepted, the title and abstract will appear in advertisements and on the conference website.

Motivation and Objectives:

2-3 sentences describing the motivation for why this topic is relevant to the main conference. If your tutorial has particular applicability to practitioners from industry, describe this relevance in another 2-3 sentences. If your tutorial is accepted, then this description will be used as early publicity for the tutorial.

Duration:

Full-day (7-hour) or half-day (3.5-hour), including breaks. If another format is used, it must be elaborated in detail here.

Outline of Topics:

Envision topics (e.g., in the form of a table of contents of the tutorial) Please indicate the number and type of interactive activities (such as exercises) for tutorial attendees and the motivation of why such activities have been chosen.

Target Audience:

What type of background should the tutorial attendees have? What is the envisioned number of attendees desired for the tutorial (minimum and maximum)?

Tutorial History:

Have you offered this tutorial before? If so, please provide a history of the venues, dates, and approximate attendance numbers.

Presenters’ Bios:

Provide the name and a brief (2-3 sentence) biography for each of the tutorial presenters that highlights their qualifications with respect to the tutorial.

Publicity:

Plans for promoting the tutorial and attracting participants.

Appendix:

Provide five to ten sample slides from the tutorial.

Please note that all tutorial presenters should be present in person at RE’25.

Tutorial 1: Promotion of Open Science in Requirements Engineering: Leveraging the ORKG and ORKG Ask for FAIR Scientific Information

Organisers: Oliver Karras, Lena John and Davide Fucci

Abstract: Despite improved digital access to publications as digitized artifacts, they remain document-based and often behind paywalls, impeding open science. Researchers must push beyond the established boundary of publications as digitized documents. Open science infrastructures support them in organizing and (re-)using publications and their information so that they are Findable, Accessible, Interoperable, and Reusable (FAIR) for humans and machines in the long term. The Open Research Knowledge Graph (ORKG) and ORKG Ask are two sustainably governed open science infrastructure for FAIR scientific information, with successful use cases in requirements engineering (RE). This tutorial aims to familiarize the participants with open science and empower them to leverage ORKG and ORKG Ask for FAIR scientific information. The half-day tutorial consists of three sessions: 1) A theoretical session on open science, ORKG, and ORKG Ask regarding their importance, benefits, and incentives, 2) Two practical sessions with two hands-on exercises for learning skills and practical experiences to leverage ORKG and ORKG Ask, and 3) A feedback session for reflection. The tutorial raises awareness for open science in RE, introduces ORKG and ORKG Ask, fosters networking and future collaborations. The participants become familiar with open science, ORKG, and ORKG Ask by learning skills and gaining practical experience to leverage the infrastructures themselves. The transition away from digitized documents and towards FAIR scientific information is a long-term endeavor. We must gradually sensitize researchers to this transition, while guiding and empowering them to leverage existing solutions as an integral part of their work. The tutorial pursues this endeavor to promote open science in RE.

Tutorial 2: Product Comparison using Feature Similarity Matching

Organisers: Mike Mannion and Hermann Kaindl

Abstract: The volume, variety and velocity of products in software-intensive systems product lines is increasing. One challenge is to understand the range of similarity between products. Reasons for product comparison include (i) to decide whether to build a new product or not (ii) to evaluate how similar products differ for strategic positioning or branding reasons (iii) to gauge if a product line needs to be reorganized (iv) to assess if a product falls within national legislative and regulatory boundaries. In product line engineering, feature models are developed as one of several reusable assets and new systems are configured from the feature model of a product line. A feature model can be represented as an acyclic graph showing the product line as a set of structural feature relationships. In this tutorial, we will show how systems configured from a feature model can be represented as a weighted binary string where a 1 represents a selected feature, a 0 represents an unselected feature, where each weight represents the feature’s relative importance and can be calculated using a centrality metric. Systems can then be compared using similarity matching with a weighted binary string metric. We will discuss the benefits and limitations of this method using a mobile phone example.

Tutorial 3: Applied Statistical Causal Inference in Requirements Engineering

Organisers: Julian Frattini, Hans-Martin Heyn, Robert Feldt and Richard Torkar

Abstract: Software engineering (SE) research currently witnesses a shift in data analysis practices. The flaws of simple, frequentist tools like t-tests threaten the validity of conclusions drawn from quantitative data, especially in observational studies. To address these flaws, SE researchers adopt methods for statistical causal inference (SCI) which are successfully applied in scientific disciplines like medical research, sociology, and econometrics. However, these methods exhibit a steep learning curve which hinders their adoption both in SE and requirements engineering (RE) research. This tutorial aims to gently introduce SCI to RE researchers in order to keep up with methodological advances of the SE field. The tutorial introduces the fundamentals of SCI with applications and examples particular to RE. Participating in the tutorial will equip RE researchers to keep up with the advanced data analysis practices observed in SE research.

Tutorial 4: Social, Legal, Ethical, Empathetic and Cultural Requirements: from Elicitation to Verification

Organisers: Lina Marsso, Sinem Getir Yaman, Isobel Standen, Nick Feng, Pedro Ribeiro, Beverley Townsend, Ana Cavalcanti, Radu Calinescu and Marsha Chechik

Abstract: A new class of requirements is of growing importance for many AI and autonomous systems. In applications ranging from assistive care to emergency management, software for autonomous systems (often using AI components) need to make decisions that are expected to comply with requirements that reflect the social, legal, ethical, empathetic and cultural (SLEEC) norms of its users. For example, the control software of an assistive-care robot should consider its users’ well-being and autonomy needs. In this tutorial, we will present a tool-supported methodology for the elicitation, formalisation, well-formedness validation, and compliance verification of SLEEC requirements, and show its application to an assistive-care robot.