Rebekka Wohlrab

Rebekka Wohlrab

Auto-generated profile, based on publicly available information

Rebekka Wohlrab

Department of Computer Science and Engineering Chalmers University of Technology and University of Gothenburg Gothenburg Sweden

Research Focus & Metrics

Academic Career Length

13Years (2014-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
22 April 2019 in Journal of Software: Evolution and Process
Verified
Journal Article
Open access
PDF file
RWRebekka Wohlrab
Rebekka Wohlrab
PPPatrizio Pelliccione
Patrizio Pelliccione
EKEric Knauss
Eric Knauss
MLMats Larsson
Mats Larsson
Summary: Agile methods are increasingly introduced in automotive companies in the attempt to become more efficient and flexible in the system development. The adoption of agile practices influences communication between stakeholders and makes companies rethink the management of artifacts and documentation like requirements, safety compliance documents, and architecture models. Practitioners aim to reduce irrelevant documentation but face a lack of guidance to determine what artifacts are needed and how they should be managed. This paper presents artifacts, challenges, guidelines, and practices for the continuous management of systems engineering artifacts in automotive based on a theoretical and empirical understanding of the topic. In collaboration with 53 practitioners from six automotive companies, we conducted a design‐science study involving interviews, a questionnaire, focus groups, and practical data analysis of a systems engineering tool. The guidelines suggest the distinction between artifacts that are shared among different actors in a company (boundary objects) and those that are used within a team (locally relevant artifacts). We propose an analysis approach to identify boundary objects and three practices to manage systems engineering artifacts in industry.

18 November 2019
Verified
Book Chapter
Closed access
PDF file
JSJan-Philipp Steghöfer
Jan-Philipp Steghöfer
EKEric Knauss
Eric Knauss
JHJennifer Horkoff
Jennifer Horkoff
RWRebekka Wohlrab
Rebekka Wohlrab

21 November 2018 in Requirements Engineering
Verified
Journal Article
Open access
PDF file
RWRebekka Wohlrab
Rebekka Wohlrab
EKEric Knauss
Eric Knauss
JSJan-Philipp Steghöfer
Jan-Philipp Steghöfer
SMSalome Maro
Salome Maro
AAAnthony Anjorin
Anthony Anjorin
PPPatrizio Pelliccione
Patrizio Pelliccione
Traceability is crucial for many activities in software and systems engineering including monitoring the development progress, and proving compliance with standards. In practice, the use and maintenance of trace links are challenging as artifacts undergo constant change, and development takes place in distributed scenarios with multiple collaborating stakeholders. Although traceability management in general has been addressed in previous studies, there is a need for empirical insights into the collaborative aspects of traceability management and how it is situated in existing development contexts. The study reported in this paper aims to close this gap by investigating the relation of collaboration and traceability management, based on an understanding of characteristics of the development effort. In our multiple exploratory case study, we conducted semi-structured interviews with 24 individuals from 15 industrial projects. We explored which challenges arise, how traceability management can support collaboration, how collaboration relates to traceability management approaches, and what characteristics of the development effort influence traceability management and collaboration. We found that practitioners struggle with the following challenges: (1) collaboration across team and tool boundaries, (2) conveying the benefits of traceability, and (3) traceability maintenance. If these challenges are addressed, we found that traceability can facilitate communication and knowledge management in distributed contexts. Moreover, there exist multiple approaches to traceability management with diverse collaboration approaches, i.e., requirements-centered, developer-driven, and mixed approaches. While traceability can be leveraged in software development with both agile and plan-driven paradigms, a certain level of rigor is needed to realize its benefits and overcome challenges. To support practitioners, we provide principles of collaborative traceability management. The main contribution of this paper is empirical evidence of how culture, processes, and organization impact traceability management and collaboration, and principles to support practitioners with collaborative traceability management. We show that collaboration and traceability management have the potential to be mutually beneficial—when investing in one, also the other one is positively affected.

25 August 2016
Verified
Conference Paper
Open access
SMSalome Maro
Salome Maro
AAAnthony Anjorin
Anthony Anjorin
RWRebekka Wohlrab
Rebekka Wohlrab
JSJan-Philipp Steghöfer
Jan-Philipp Steghöfer
Traceability is an important concern for numerous software engineering activities. Establishing traceability links is a challenging and cost-intensive task, which is uneconomical without suitable strategies for maintaining high link quality. Current approaches to Traceability Management (TM), however, often make important assumptions and choices without ensuring that the consequences and implications for traceability maintenance are feasible and desirable in practice. In this paper, therefore, we identify a set of core factors that influence how the quality of traceability links can be maintained. For each factor, we discuss relevant challenges and provide guidelines on how best to ensure viable traceability maintenance in a practical TM approach. Our guidelines are meant to be used by tool developers and users to select the most appropriate TM approach for their needs. Our results are based on and supported by data collected from interviews conducted with: (i) 9 of our industrial and academic project partners to elicit requirements for a TM tool, and (ii) 24 software development stakeholders from 15 industrial cases to provide a broader overview of the current state of the practice on TM. To evaluate the feasibility of our guidelines, we investigate a set of existing TM approaches used in industry with respect to our guidelines.

1 April 2018
Verified
Conference Paper
Closed access
SGSergio Garcia
Sergio Garcia
CMClaudio Menghi
Claudio Menghi
PPPatrizio Pelliccione
Patrizio Pelliccione
TBThorsten Berger
Thorsten Berger
RWRebekka Wohlrab
Rebekka Wohlrab
Robotic applications are typically realized using ad hoc and domain-specific solutions, which challenges the engineering and cross-project reuse of such applications. Especially in complex scenarios, where self-adaptive robots collaborate among themselves or with humans, the effective and systematic engineering of such applications is becoming increasingly important. Such scenarios require decentralized software architectures that foster fault-tolerant ways of managing large teams of (possibly) heterogeneous robots. To the best of our knowledge, no existing architecture for robot applications supports decentralized and self-adaptive collaboration. To address this gap, we conducted a design science study with 21 practitioners and experts in the field of robotics to develop an architecture fulfilling these requirements through several iterations. We present SERA, an architecture for robot applications that supports human-robot collaboration, as well as adaptation and coordination of single- and multi-robot systems in a decentralized fashion. SERA is based on layers that contain components that manage the adaptation at different levels of abstraction and communicate through well-defined interfaces. We successfully validated SERA by considering a set of real scenarios, by both using simulators and real robots, by involving robotic experts, and by benchmarking it with state-of-the-art solutions.

1 April 2020 in Journal of Systems and Software
Verified
Journal Article
Closed access
RWRebekka Wohlrab
Rebekka Wohlrab
EKEric Knauss
Eric Knauss
PPPatrizio Pelliccione
Patrizio Pelliccione