The 31st EEE International Requirements Engineering Conference (RE’23) will continue the successful tutorial program of the RE conference series. RE’23 tutorials will focus on a variety of 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
  • Relating requirements to 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 Big Data / Machine-Learning / AI systems
  • Data/process mining for requirements engineering
  • Requirements engineering for sustainability
  • Distributed requirements engineering


The presenters should note that all RE’23 tutorials will be held in person.

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 in PDF. 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 shall be used, it has to be elaborated in some 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 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.