Goetz Botterweck

Goetz Botterweck

Auto-generated profile, based on publicly available information

Goetz Botterweck

Trinity College Dublin Dublin Ireland

Research Focus & Metrics

Academic Career Length

20Years (2007-Present)

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

Representative Publications

View All Publications
28 July 2012 in International Journal on Software Tools for Technology Transfer
Verified
Journal Article
Open access
PDF file
ISIna Schaefer
Ina Schaefer
RRRick Rabiser
Rick Rabiser
DCDave Clarke
Dave Clarke
LBLorenzo Bettini
Lorenzo Bettini
DBDavid Benavides
David Benavides
KVKarina Villela
Karina Villela
Diversity is prevalent in modern software systems to facilitate adapting the software to customer requirements or the execution environment. Diversity has an impact on all phases of the software development process. Appropriate means and organizational structures are required to deal with the additional complexity introduced by software variability. This introductory article to the special section “Software Diversity—Modeling, Analysis and Evolution” provides an overview of the current state of the art in diverse systems development and discusses challenges and potential solutions. The article covers requirements analysis, design, implementation, verification and validation, maintenance and evolution as well as organizational aspects. It also provides an overview of the articles which are part of this special section and addresses particular issues of diverse systems development.

1 October 2012 in Journal of Systems and Software
Verified
Journal Article
Closed access
APAndreas Pleuss
Andreas Pleuss
GBGoetz Botterweck
Goetz Botterweck
DDDeepak Dhungana
Deepak Dhungana
APAndreas Polzer
Andreas Polzer
SKStefan Kowalewski
Stefan Kowalewski

1 January 2010
Verified
Book Chapter
Closed access
PDF file
DKDimitrios S. Kolovos
Dimitrios S. Kolovos
LRLouis M. Rose
Louis M. Rose
SASaad Bin Abid
Saad Bin Abid
RPRichard F. Paige
Richard F. Paige
FPFiona A. C. Polack
Fiona A. C. Polack
GBGoetz Botterweck
Goetz Botterweck

7 October 2024 in ACM Computing Surveys
Verified
Journal Article
Open access
ARAbdul Razzaq
Abdul Razzaq
JBJim Buckley
Jim Buckley
QLQin Lai
Qin Lai
TYTingting Yu
Tingting Yu
GBGoetz Botterweck
Goetz Botterweck
Context and Motivation – Developer eXperience (Dev-X) is a recent research area that focuses on developers perceptions, feelings, and values with respect to software development and software quality. Research suggests that factors and practices related to Dev-X can have a substantial impact on developer productivity (Dev-P). However, despite a large and diverse body of literature on factors that can impact Dev-P in general, there is no coherent and comprehensive characterization of how Dev-X-specific insights can influence developer productivity. Aims – In the presented research, we aim to provide a coherent, comprehensive characterization of factors and practices related to Dev-X, with a particular focus on those factors and practices that potentially affect Dev-P. Method – To this end, we performed a systematic literature review and identified 218 relevant papers in this area. We characterize the papers based on the related frameworks and concepts common to Dev-X and Dev-P as presented in the existing literature. Dev-X factors such as “work fragmentation” and practices such as “collaboration with owner-developer” are identified using a grounded-in-the-literature, content-analysis method, guided by the theory. For each Dev-X factor, we identify attributes that might be used to assess/ measure the current status (of an organization or project) regarding that factor and how that factor and its effects on productivity have been evidenced in the literature (mentioned vs. considered in questionnaires vs. substantiated with a more positivist evaluation). Results – We identify 33 Dev-X-related factors and 41 Dev-X-related practices, which are organized into 10 themes to summarize their influence. The results suggest that the availability of required resources, relevant expertise re the allocated tasks, and fewer interruptions are among the top positively impacting factors. Conversely, factors such as code complexity, heterogeneous contexts of tasks, and non-adherence to standardization harm Dev-X and Dev-P. Top industrial practices employed to mitigate the negative influence of factors include characterization-based task assignments, mental model support, and the timely evolution of technologies. Conclusions – Overall, this research suggests that organizations can influence Dev-P through improved Dev-X, incorporating suitable practices to mediate relevant factors in their context. Important in this regard are practices such as fragmenting large tasks, highlighting the utility of proposed tasks/changes to the developers, and promoting (developer) ownership of artefacts. Finally, our results point to areas where further research seems appropriate, i.e., where Dev-X factors/practices have been proposed as being impactful on Dev-P but not yet fully substantiated or explored as such (factors like “Nature of Activity” and practices like choosing practices/protocols appropriately).

1 June 2015 in Information and Software Technology
Verified
Journal Article
Open access
JDJosé Ángel Galindo Duarte
José Ángel Galindo Duarte
DDDeepak Dhungana
Deepak Dhungana
RRRick Rabiser
Rick Rabiser
DBDavid Benavides
David Benavides
GBGoetz Botterweck
Goetz Botterweck
PGPaul Grünbacher
Paul Grünbacher

2 September 2012
Verified
Conference Paper
Open access
PDF file
JRJulia Rubin
Julia Rubin
AKAndrei Kirshin
Andrei Kirshin
GBGoetz Botterweck
Goetz Botterweck
MCMarsha Chechik
Marsha Chechik
We consider the problem of supporting effective code reuse as part of Software Product Line Engineering. Our approach is based on code forking -- a practice commonly used in industry where new products are created by cloning the existing ones. We propose to maintain meta-information allowing organization to reason about the developed product line in terms of features rather than incremental code changes made in different forks and to detect inconsistencies in implementations of these features. In addition, we propose to detect and maintain semantic, implementation-level require relationships between features, supporting the developers when they copy features from different branches or delete features in their own branch, thus facilitating reuse of features between products. Our approach aims at mitigating the disadvantages of the forking mechanism while leveraging its advantages. We illustrate the approach on an example, and discuss its possible implementation and integration with Software Configuration Management systems.