The 29th IEEE International Requirements Engineering Conference (RE’21) will continue the successful tutorial program of the RE conference series. RE’21 tutorials will focus on a variety of requirements-related topics of interest to industry, academia, and government.
We invite you to submit proposals for full-day ( approx. 7-hour) or half-day (approx. 3.5-hour) tutorials.

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

The presenters should be prepared to deliver the tutorial online, following the RE21 guidelines. On-site tutorial delivery may also be possible, depending on the situation of the pandemic in September 2021

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).

Speakers:
Birgit Penzenstadler (Chalmers Univ., Goteborg, Sweden)

The Sustainability Awareness Framework (SusAF) aims to anticipate the effects of IT products and services. It considers five dimensions of sustainability (social, individual, environmental, economic, and technical) and across three orders of effect (direct, indirect, and systemic). We teach you how to apply it to systems you bring with you or example systems we have as a backup. The take-aways from the tutorial are 1) a concrete method for projecting potential sustainability impacts of a system, 2) a graphical illustration to visualize these impacts, and 3) a structure to communicate sustainability impacts to diverse stakeholders.

Speakers:
Hermann Kaindl (TU Wien, Austria)
Mike Mannion (Glasgow Caledonian University, UK)

Several socio-economic trends, such as people’s demands for personalized software-intensive products, are generating unparalleled increases in the volume, variety, velocity and complexity of software-intensive products. This is placing considerable strain on software designers. Part of the solution is to make it easier to explore stakeholder needs by showcasing the range of similarity and variability between the products in a product line. A technical challenge is to create product development processes that include a systematic capability to manage the identification, selection and deployment of reusable requirements. Requirements reuse is not straightforward.
This tutorial presents and compares two different requirements reuse approaches, one in the context of product line engineering, the other in the context of case-based reasoning (invented in Artificial Intelligence). Both approaches have different key properties and trade-offs between the costs of making software artefacts reusable and the benefits of reusing them. To aid large-scale development we have proposed a FeatureSimilarity Model, which draws on both approaches to facilitate discovering requirements relationships using similarity metrics. Understanding the similarities and differences between products can aid suppliers assess whether there is value in new product development proposals, and customers assess whether there is value in one product over another concerning their needs.

Speakers:
Jon Whittle ( CSIRO’s Data61 and Monash University Melbourne, Australia)
Waqar Hussain (Monash University Melbourne, Australia)

Recent years have seen renewed interest in the social impact of technology, as major scandals such as Cambridge Analytica and bias in AI systems have made the international press. There is an increasing acceptance that software systems must properly embed human values – such as inclusion, diversity, social responsibility, and cultural context – in their design. The software engineering field, however, has been slow to adopt human-value based methods for software design, in contrast to other fields such as HCI. In this tutorial, we will give an overview of approaches for embedding human values in technology, summarizing work in other fields. We will then describe work in addressing human values in the software engineering field, with a specific focus on requirements engineering. Through a series of interactive exercises, we will help participants to explore what human values mean in a requirements engineering context, how they can be captured as part of requirements engineering, and practical steps that can be taken to address human values in software.

Speakers:
Theresia Ratih Dewi Saputri (Universitas Ciputra Surabaya, Indonesia)
Seok-Won Lee (Ajou University, South Korea)

Due to the critical role of software-intensive systems in society, software engineers have a responsibility to add sustainability as a goal while designing a software system. However, most of the engineers mostly focus on their specific areas. Moreover, sustainability is usually treated as an afterthought in current practice. This is not surprising because the concept of sustainability is still vague and at a high level of abstraction.
This tutorial proposes an integrated framework that allows software practitioners and academics to accommodate sustainability requirements that are aligned with the other software quality attributes to enhance sustainable development. Using the combination of goal-scenario based approach and feature modeling, the sustainability requirements are designed along with the system’s functional compositions. By using the provided reference model, we can show the practical way of addressing sustainability concerns in the software development process. It could help the requirements engineer to incorporate the sustainability concept in structuring requirements, decomposing functional implementation, and documenting the requirements artifacts. The process includes (1) investigating the stakeholders' needs related to sustainability (2) structuring software system requirements into a sustainability goal model and minimizes sustainability impacts based on gathered requirements, and (3) discovering and designing features to satisfy sustainability-related requirements that can be easily integrated with other requirements.

Speakers:
Mariana Peixoto ( Federal University of Pernambuco (UFPE), Brazil)
Carla Silva ( Federal University of Pernambuco (UFPE), Brazil)
Jéssyka Vilela ( Federal University of Pernambuco (UFPE), Brazil)
Tony Gorschek (Blekinge Institute of Technology (BTH), Sweden)

Privacy has become a concern in Agile Software Development (ASD), either to satisfy users' needs or to comply with privacy laws. However, recent studies have shown that ASD approaches still neglect non-functional requirements (NFRs), as is the privacy case. This concern and new data protection laws that came into force led companies to face the challenges to understand the laws and to comply with them. In addition, research has shown that many developers do not have sufficient knowledge about how to develop privacy-sensitive software.
Motivated by this scenario, this tutorial aims to draw attention to the need to understand privacy from the beginning of the software development lifecycle. Initially, we will present an overview of privacy, as well as several privacy principles. Later, we will show the main data protection laws (In-depth detailing of the General Data Protection Regulation - GDPR). Then, we will discuss how to read and evaluate privacy policies. Finally, we will present a technique for specifying privacy requirements in ASD called Privacy Criteria Method (PCM). At the end of the tutorial, participants will be able to have a critical and technical view of privacy when performing the requirements specification activity.

Speaker:
Jean-Michel Bruel (Toulouse University, France)
Sébastien Mosser (Université du Québec à Montréal, Canada)

We propose a tutorial on Requirements Engineering in an DevOps context that aims at exploring the boundaries between requirements, specifications, stories, scenarios and tests. We will capitalize on the well-known a concept of user stories and epics and their usage for expressing user requirements. The objective of the tutorial is to focus on the automation of the evaluation of such requirements based on definition of done acceptance criteria. We will demonstrate how such requirements can be tracked in a project management tool and linked to source code development. At the source code level, we will demonstrate how the stories and the associated acceptance scenarios can be modeled using the Gherkin language and linked to classical unit tests to automate their validation. Finally, a continuous integration environment will be deployed using Docker to link together the different tools and offer an automated pipeline for software developers, bridging the gap between requirements and code development.

Speakers:
Fabiano Dalpiaz (Utrecht University, Netherlands)
Sjaak Brinkkemper (Utrecht University, Netherlands)

90% of agile practitioners employ user stories for capturing requirements, also thanks to embedding of this practice within development tools. Among user story users, about 70% follow a simple template: As a role, I want to action, so that benefit. User stories’ popularity among practitioners and their simple yet strict structure make them ideal candidates for automatic reasoning based on natural language processing. In our research, we have found that about 50% of real-world user stories contain easily preventable linguistic defects. To alleviate this problem, we have created tool-supported methods that facilitate the creation of better user stories.
This tutorial combines previous work of the RE-Lab@UU into a pipeline for working with user stories: (1) The basics of creating user stories, and their use in requirements engineering; (2) How to improve user story quality with the Quality User Story Framework and AQUSA tool; (3) How to generate conceptual models from user stories using the Visual Narrator tool and analyze them for possible ambiguity and inconsistency; and (4) How to link requirements to architectures via the RE4SA model. Our approach is demonstrated with results obtained from 20+ software companies employing user stories. Index Terms—Agile requirements engineering, user stories, NLP, AQUSA, Visual Narrator, REVV-Light, RE4SA.

Speakers:
Giancarlo Guizzardi (Free University of Bolzano-Bozen, Italy, and University of Twente, Netherlands )
Renata Guizzardi (University of Twente, Netherlands)
John Mylopoulos (University of Ottawa, Canada)

The advent of socio-technical, cyber-physical and Artificial Intelligence (AI) systems has broadened the scope of requirements engineering which must now deal with new classes of requirements, concerning, e.g., ethics, privacy and trust. Unfortunately, requirements engineers cannot be expected to understand the qualities behind these new classes of systems so that they can conduct elicitation, analysis and operationalization. To address this issue, we present here a novel approach for conducting requirements engineering. The approach is grounded on foundational theories from the area of applied ontology, as well as on methodological and engineering tools derived from those theories. Moreover, it proposes a requirements engineering process that starts with the adoption of a domain model properly constructed using these techniques, which is then used to guide the activities of requirements analysis. We illustrate the approach by: conducting an ontological analysis of the very notions of functional and non-functional requirements; constructing examples of ontology-based domain modeling in the areas of Risk, Value and Trust; exemplifying the analysis and derivation of Ethicality requirements.

Tutorial proposals should not exceed two pages (not counting appendices) and must be submitted electronically as PDF. Tutorial proposals should contain the following information: