Thorsten Haendler
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Previous Organizations / Institutes
The organizations / institutes from the scholar's other articles in the past ten years
Research Subjects
Thorsten Haendler has a total of 7 co-authors. Here are the top co-authors by number of shared publications:
Gustaf Neumann
Vienna University of Economics and Business (WU Vienna)
5 shared publicationsStefan Sobernig
WU Vienna, Austria
3 shared publicationsFiodor Smirnov
Vienna University of Economics and Business (WU Vienna)
2 shared publicationsMark Strembeck
WU Vienna, Austria
2 shared publications- Mark Strembeck
Institute for Complex Networks, WU Vienna, Vienna, Austria
2 shared publications - Gustaf Neumann
Vienna University of Economics and Business Vienna University of Economics and Business Leipzig University
1 shared publication
Latest Publications
- 10 November 2020
- Published by Springer Nature
- p. 236-261
RefacTutor: An Interactive Tutoring System for Software Refactoring
- 10 November 2020
- Published by Springer Nature
- p. 236-261
RefacTutor: An Interactive Tutoring System for Software Refactoring
- 10 November 2020
- Published by Springer Nature
- p. 602-628
Ontology-Based Analysis and Design of Educational Games for Software Refactoring
- 10 November 2020
- Published by Springer Nature
- p. 602-628
Ontology-Based Analysis and Design of Educational Games for Software Refactoring
- Open Access
- 1 January 2019
- Published by INSTICC
- p. 307-316
A Framework for the Assessment and Training of Software Refactoring Competences
- 1 January 2019
- Published by INSTICC
- p. 307-316
Open AccessA Framework for the Assessment and Training of Software Refactoring Competences
- Open Access
- 1 January 2019
- Published by INSTICC
- p. 177-188
An Interactive Tutoring System for Training Software Refactoring
- 1 January 2019
- Published by INSTICC
- p. 177-188
Open AccessAn Interactive Tutoring System for Training Software Refactoring
- Open Access
- 1 January 2019
- Published by INSTICC
- p. 24-35
Ontology-based Analysis of Game Designs for Software Refactoring
- 1 January 2019
- Published by INSTICC
- p. 24-35
Open AccessOntology-based Analysis of Game Designs for Software Refactoring
- Open Access
- 1 January 2019
- Published by HICSS Conference Office
Serious Refactoring Games
Software design issues can severely impede software development and maintenance. Thus, it is important for the success of software projects that developers are aware of bad smells in code artifacts and improve their skills to reduce these issues via refactoring. However, software refactoring is a complex activity and involves multiple tasks and aspects. Therefore, imparting competences for identifying bad smells and refactoring code efficiently is challenging for software engineering education and training. The approaches proposed for teaching software refactoring in recent years mostly concentrate on small and artificial tasks and fall short in terms of higher level competences, such as analysis and evaluation. In this paper, we investigate the possibilities and challenges of designing serious games for software refactoring on real-world code artifacts. In particular, we propose a game design, where students can compete either against a predefined benchmark (technical debt) or against each other. In addition, we describe a lightweight architecture as the technical foundation for the game design that integrates pre-existing analysis tools such as test frameworks and software-quality analyzers. Finally, we provide an exemplary game scenario to illustrate the application of serious games in a learning setting.
- 1 January 2019
- Published by HICSS Conference Office
Open AccessSerious Refactoring Games
Software design issues can severely impede software development and maintenance. Thus, it is important for the success of software projects that developers are aware of bad smells in code artifacts and improve their skills to reduce these issues via refactoring. However, software refactoring is a complex activity and involves multiple tasks and aspects. Therefore, imparting competences for identifying bad smells and refactoring code efficiently is challenging for software engineering education and training. The approaches proposed for teaching software refactoring in recent years mostly concentrate on small and artificial tasks and fall short in terms of higher level competences, such as analysis and evaluation. In this paper, we investigate the possibilities and challenges of designing serious games for software refactoring on real-world code artifacts. In particular, we propose a game design, where students can compete either against a predefined benchmark (technical debt) or against each other. In addition, we describe a lightweight architecture as the technical foundation for the game design that integrates pre-existing analysis tools such as test frameworks and software-quality analyzers. Finally, we provide an exemplary game scenario to illustrate the application of serious games in a learning setting.
- Open Access
- 22 May 2017
- Published by Association for Computing Machinery (ACM)
- p. 1-9
Towards triaging code-smell candidates via runtime scenarios and method-call dependencies
Managing technical debt includes the detection and assessment of debt at the code and design levels (such as bad smells). Existing approaches and tools for smell detection primarily use static program data for decision support. While a static analysis allows for identifying smell candidates without executing and instrumenting the system, such approaches also come with the risk of missing candidates or of producing false positives. Moreover, smell candidates might result from a deliberate design decision (e.g., of applying a particular design pattern). Such risks and the general ambivalence of smell detection require a manual design and/or code inspection for reviewing all alleged smells. In this paper, we propose an approach to obtain tailorable design documentation for object-oriented systems based on runtime tests. In particular, the approach supports a tool-supported triaging of code-smell candidates. We use runtime scenario tests to extract execution traces. Based on these execution traces, different (automatically derived) model perspectives on method-call dependencies (e.g., dependency structure matrices, DSMs; UML2 sequence diagrams) are then used as decision support for assessing smell candidates. Our approach is implemented as part of the KaleidoScope tool which is publicly available for download.
- 22 May 2017
- Published by Association for Computing Machinery (ACM)
- p. 1-9
Open AccessTowards triaging code-smell candidates via runtime scenarios and method-call dependencies
Managing technical debt includes the detection and assessment of debt at the code and design levels (such as bad smells). Existing approaches and tools for smell detection primarily use static program data for decision support. While a static analysis allows for identifying smell candidates without executing and instrumenting the system, such approaches also come with the risk of missing candidates or of producing false positives. Moreover, smell candidates might result from a deliberate design decision (e.g., of applying a particular design pattern). Such risks and the general ambivalence of smell detection require a manual design and/or code inspection for reviewing all alleged smells. In this paper, we propose an approach to obtain tailorable design documentation for object-oriented systems based on runtime tests. In particular, the approach supports a tool-supported triaging of code-smell candidates. We use runtime scenario tests to extract execution traces. Based on these execution traces, different (automatically derived) model perspectives on method-call dependencies (e.g., dependency structure matrices, DSMs; UML2 sequence diagrams) are then used as decision support for assessing smell candidates. Our approach is implemented as part of the KaleidoScope tool which is publicly available for download.
- Open Access
- 4 April 2016
- Published by Association for Computing Machinery (ACM)
- p. 1573-1575
Deriving UML-based specifications of inter-component interactions from runtime tests
- 4 April 2016
- Published by Association for Computing Machinery (ACM)
- p. 1573-1575
Open AccessDeriving UML-based specifications of inter-component interactions from runtime tests
- 25 February 2016
- Published by Springer Nature
- p. 326-348
Deriving Tailored UML Interaction Models from Scenario-Based Runtime Tests
- 25 February 2016
- Published by Springer Nature
- p. 326-348
Deriving Tailored UML Interaction Models from Scenario-Based Runtime Tests
- Open Access
- 1 January 2015
- Published by INSTICC
- p. 229-240
An Approach for the Semi-automated Derivation of UML Interaction Models from Scenario-based Runtime Tests
- 1 January 2015
- Published by INSTICC
- p. 229-240
Open AccessAn Approach for the Semi-automated Derivation of UML Interaction Models from Scenario-based Runtime Tests