The 34th IEEE International Requirements Engineering Conference (RE’26) is proud to continue its tradition of offering a dynamic and impactful tutorial program. Designed for professionals, researchers, and practitioners from industry, academia, and government, the RE’26 tutorials will dive into a wide range of requirements-related topics at the forefront of practice and research.

Participants can look forward to interactive, skill-building sessions that deliver fresh insights, practical techniques, and new perspectives they can immediately apply in their work or research.

We invite you to contribute to this exciting program by submitting proposals for full-day tutorials (approx. 7 hours) or half-day tutorials (approx. 3.5 hours).

Tutorials

Call for Tutorial Proposals

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

• Improving requirements engineering practices with large language models (LLMs)
• 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

Tutorial Proposal Evaluation Criteria

Proposals will be evaluated based on their overall quality and clarity, the anticipated value and benefits for participants, the relevance and alignment with the conference program, and the qualifications 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 Knowledge

Organizers: Oliver Karras, Lena John and Tobias Hey

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 knowledge 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 knowledge, 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 knowledge. 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 knowledge 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: Applied Bayesian Data Analysis in Requirements Engineering

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

Abstract: Requirements engineering (RE) researchers often resort to frequentist methods to obtain results from quantitative data, e.g., Student’s t-test or ANOVA. These frequentist methods are convenient but subject to several flaws: They reduce complex data to binary results, rely on the incorrect application of the modus tollens, and distinguish only between normally and non-normally distributed data, dismissing all other types of distributions. These flaws threaten the conclusion validity of the obtained results. To mitigate these threats, several empirical disciplines have started adopting Bayesian data analysis (BDA) methods, which are more sophisticated, valid, and preserve natural uncertainty in data. However, their sophistication comes at the cost of additional complexity, which inhibits their adoption. Consequently, this tutorial aims at providing RE researchers with a gentle introduction to BDA methods.

Tutorial 3: Validating Requirements of Machine Learning Pipelines with Justification Models

Organizers: Sebastien Mosser and Kalvin Thuan-Phong Khuu

Abstract: In the rapid evolution of Machine Learning (ML) systems, engineers and data scientists often focus solely on building the pipelines to train and validate their models. This focus often leads to “decision drift”, a critical maintenance challenge in which the rationale behind specific ML pipeline configurations is lost over time, leaving teams knowing exactly how a pipeline is implemented but not why. To address this and ensure strict conformance with requirements, we demonstrate justification models as a lightweight approach to systematically capture and defend the rationale behind ML pipeline design. Using jPipe, a textual domain-specific language, developers can model justifications to ensure that specific project requirements and overarching goals are continuously met and automatically validated in their continuous integration/continuous deployment environments. By integrating jPipe into the ML lifecycle, teams operationalize their rationale, directly mitigating decision drift and fostering reproducible, transparent pipelines that provably conform to actionable, domain-specific software requirements.

Tutorial 4: From Specs to Success: Expanding your Impact as Requirements Engineer

Organizers: Christof Ebert

Abstract: Today, success is defined not by what exactly is built, but by the perceived value. Value exists in the eyes of the beholder, namely through customer adoption, business impact, and measurable outcomes. This focus on perceived value is not always understood in R&D and IT organization. Even in organizations with mature requirements engineering, the contribution to market value often remains implicit. Requirements are developed or simply collected, analyzed, modeled and eventually delivered. Sometimes they are not even delivered because other requirements would need more effort than planned. Value itself is shaped elsewhere, and often on a parallel track, which many engineers would call “political”. Key decisions on value propositions, innovation, prioritization, differentiation, and success criteria are frequently distributed across marketing, product management, and engineering. During projects, additional pressure emerges through ad-hoc change requests from sales, often disconnected from feasibility, product strategy, and return on investment. This separation creates friction and weakens market perception. There is a disconnect between what is specified and what ultimately succeeds in the market. This tutorial connects requirements engineering (RE) with value generation. It shows how RE will become a direct (!) driver of market success by linking specifications with value, outcomes, and business goals. Participants will explore where and how they can grow their own impact through prioritization, trade-offs, and how their expertise will be recognized by decision-makers. Building on real-world examples, the tutorial introduces practical techniques to connect requirements with customer value, strengthen alignment with product strategy, and make contributions to success visible. In an environment where AI increasingly supports traditional RE tasks, the tutorial elaborates the future role of requirements engineering. RE must focus on judgment, context, and value creation. By bridging product management, product marketing and engineering expands its impact on both product success and professional relevance. Christof Ebert as presenter brings over two decades of international experience in software engineering, product management, and executive leadership. He is a co-founder of IREB and ISPMA, introduced product management to companies such as Nokia, Siemens, Hitachi and serves as a business angel for start-ups. His work across industries combines hands-on delivery with strategic responsibility, providing participants with proven, actionable approaches grounded in their respective environments.