Dietmar Winkler

Dr. Dietmar Winkler

TU Wien, Vienna, Wien, Austria

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
26 July 2021 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
MKMarco Kuhrmann
Marco Kuhrmann
PTPaolo Tell
Paolo Tell
RHRegina Hebig
Regina Hebig
JKJil Klunder
Jil Klunder
JMJurgen Munch
Jurgen Munch
IRIta Richardson
Ita Richardson
Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders’ collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile? In this article, we investigate the question: what makes a software development method agile? We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15 percent). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.

1 September 2010
Verified
Conference Paper
Closed access
WSWikan Danar Sunindyo
Wikan Danar Sunindyo
TMThomas Moser
Thomas Moser
DWDietmar Winkler
Dietmar Winkler
SBStefan Biffl
Stefan Biffl
For monitoring, controlling, and improving software development projects, project and quality managers need tool support to analyze engineering processes within development environments. Unfortunately, technical and semantic gaps between the engineering tools and related data models make it hard to observe and analyze the implemented tool-based engineering processes. In this paper we build on a service-oriented platform for technically and semantically integrating heterogeneous engineering tools and propose an approach to monitor, analyze, and improve tool-based engineering processes. We empirically evaluate the approach using the “continuous integration and test” process and discuss strengths and limitations. Major result was that the approach enabled comparing expected and real-life engineering processes with respect to process structure, performance of individual process steps, and risk of bottlenecks.

26 February 2024 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
DWDietmar Winkler
Dietmar Winkler
PUPirmin Urbanke
Pirmin Urbanke
RRRudolf Ramler
Rudolf Ramler
Context: The readability of source code is key for understanding and maintaining software systems and tests. Although several studies investigate the readability of source code, there is limited research specifically on the readability of test code and related influence factors. Objective: In this paper, we aim at investigating the factors that influence the readability of test code from an academic perspective based on scientific literature sources and complemented by practical views, as discussed in grey literature. Methods: First, we perform a Systematic Mapping Study (SMS) with a focus on scientific literature. Second, we extend this study by reviewing grey literature sources for practical aspects on test code readability and understandability. Finally, we conduct a controlled experiment on the readability of a selected set of test cases to collect additional knowledge on influence factors discussed in practice. Results: The result set of the SMS includes 19 primary studies from the scientific literature for further analysis. The grey literature search reveals 62 sources for information on test code readability. Based on an analysis of these sources, we identified a combined set of 14 factors that influence the readability of test code. 7 of these factors were found in scientific and grey literature, while some factors were mainly discussed in academia (2) or industry (5) with only limited overlap. The controlled experiment on practically relevant influence factors showed that the investigated factors have a significant impact on readability for half of the selected test cases. Conclusion: Our review of scientific and grey literature showed that test code readability is of interest for academia and industry with a consensus on key influence factors. However, we also found factors only discussed by practitioners. For some of these factors we were able to confirm an impact on readability in a first experiment. Therefore, we see the need to bring together academic and industry viewpoints to achieve a common view on the readability of software test code.

17 October 2018 in at - Automatisierungstechnik
Verified
Journal Article
Closed access
PDF file
AMAlexandra Mazak
Alexandra Mazak
ALArndt Lüder
Arndt Lüder
SWSabine Wolny
Sabine Wolny
MWManuel Wimmer
Manuel Wimmer
DWDietmar Winkler
Dietmar Winkler
SBStefan Biffl
Stefan Biffl
Production system operators need support for collecting and pre-processing data on production systems consisting of several system components, as foundation for optimization and defect detection. Traditional approaches based on hard-coded programming of such run-time data collection systems take time and effort, and require both domain and technology knowledge. In this article, we introduce the AML-RTDC approach, which combines the strengths of AutomationML (AML) data modeling and model-driven engineering, to reduce the manual effort for realizing the run-time data collection (RTDC) system. We evaluate the feasibility of the AML-RTDC approach with a demonstration case about a lab-sized production system and a use case based on real-world requirements.

1 September 2014
Verified
Conference Paper
Closed access
SBStefan Biffl
Stefan Biffl
DWDietmar Winkler
Dietmar Winkler
RMRichard Mordinyi
Richard Mordinyi
SSStefan Scheiber
Stefan Scheiber
GHGerald Holl
Gerald Holl
In a multi-disciplinary engineering project, such as the parallel engineering of industrial production plants, domain experts want to efficiently monitor project-level constraints that depend on technical parameter values in local engineering models. However, the heterogeneous representations of constraint parameters in these engineering models make the automation of constraint monitoring difficult. In this paper, we introduce the Multi-Model Dashboard (MMD) process providing semantically integrated values of parameters and of constraints to domain experts, as parameter values in various local models change during the project. The tool-supported MMD process guides the definition and monitoring of MMD parameters and constraints. We evaluate the effectiveness and efficiency of the MMD process in a feasibility study with requirements and data from real-world use cases at industry partners. Major results are that the MMD process was effective and efficient in eliciting relevant project constraints and model dependencies and in providing data for change impact analysis.

1 September 2008 in 2008 34th Euromicro Conference Software Engineering and Advanced Applications
Verified
Conference Paper
Open access
DWDindin Wahyudin
Dindin Wahyudin
ASAlexander Schatten
Alexander Schatten
DWDietmar Winkler
Dietmar Winkler
A Min TjoaA Min Tjoa
A Min Tjoa
SBStefan Biffl
Stefan Biffl
The quality evaluation of open source software (OSS) products, e.g., defect estimation and prediction approaches of individual releases, gains importance with increasing OSS adoption in industry applications. Most empirical studies on the accuracy of defect prediction and software maintenance focus on product metrics as predictors that are available only when the product is finished. Only few prediction models consider information on the development process (project metrics) that seems relevant to quality improvement of the software product. In this paper, we investigate defect prediction with data from a family of widely used OSS projects based both on product and project metrics as well as on combinations of these metrics. Main results of data analysis are (a) a set of project metrics prior to product release that had strong correlation to potential defect growth between releases and (b) a combination of product and project metrics enables a more accurate defect prediction than the application of one single type of measurement. Thus, the combined application of project and product metrics can (a) improve the accuracy of defect prediction, (b) enable a better guidance of the release process from project management point of view, and (c) help identifying areas for product and process improvement.