Ewan Tempero
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
Research Interests
Ewan Tempero has a total of 93 co-authors. Here are the top co-authors by number of shared publications:
- Andrew Luxton-Reilly
University of Auckland, Auckland, New Zealand
12 shared publications - Diana Kirk
The University of Auckland, Auckland, New Zealand
11 shared publications - Yu-Cheng Tu
The University of Auckland, Auckland, New Zealand
9 shared publications - Kelly Blincoe
University of Auckland, New Zealand
6 shared publications - James Noble
Creative Research & Programming, Wellington, New Zealand
5 shared publications Robert Biddle
School of Mathematical and Computing Sciences, Victoria University of Wellington, P.O. Box 600, Wellington, New Zealand
5 shared publications
Latest Publications
- Open Access
- 11 November 2026
- Published by Association for Computing Machinery (ACM)
- p. 246-252
The Case for a Theoretical Approach to Teaching Code Style
- 11 November 2026
- Published by Association for Computing Machinery (ACM)
- p. 246-252
Open AccessThe Case for a Theoretical Approach to Teaching Code Style
- Open Access
- 6 October 2026
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Computing Education
Evaluating Code Quality Principles by Mapping Student Defects
Background Instructors teaching text-based programming would like to teach students how to write good quality code, in particular code that is understandable and modifiable. Often this is described as writing code with “good style”, and presented as needing to follow “style” rules or guides. However, existing style guides differ in what is included and provide rules with little justification as to why the rules improve quality. This means that the guides cannot easily be used by instructors as a teaching resource for code quality. To address this problem, Kirk et al. created a set of Principles, each of which includes a rationale that explains why certain properties of code are important for understanding and changing code. Objectives The objective for this study was to evaluate the Principles by determining their sufficiency and necessity for explaining why the style defects often found in students’ code are detrimental to code quality. We also wanted to understand the benefits and limitations of a Principles-based approach to classifying defects. Method We sourced from the literature two comprehensive, classified sets of defects found in students’ code. We mapped each defect in the source data sets to a Principle. Sufficiency and necessity were established by examining gaps in the mappings. Findings We successfully mapped all one hundred and thirty defects in the source data sets, establishing sufficiency. Most defects mapped to a single Principle, with five requiring further information before mapping could take place. All Principles were required for the mapping, confirming necessity. A comparison of defect- and Principles-based classifications revealed that the Principles-based approach enabled the identification of root causes of defects to support effective refactoring. Conclusions The assessment of the Principles for classifying student defects was positive. All defects were successfully classified and explained. The theoretical basis of the Principles resulted in categories that are more conducive to supporting future work on helping students to identify and remove quality issues. In future work, we will augment the Principles with examples based on the source defect sets and with targeted questions to support refactoring.
- 6 October 2026
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Computing Education
Open AccessEvaluating Code Quality Principles by Mapping Student Defects
Background Instructors teaching text-based programming would like to teach students how to write good quality code, in particular code that is understandable and modifiable. Often this is described as writing code with “good style”, and presented as needing to follow “style” rules or guides. However, existing style guides differ in what is included and provide rules with little justification as to why the rules improve quality. This means that the guides cannot easily be used by instructors as a teaching resource for code quality. To address this problem, Kirk et al. created a set of Principles, each of which includes a rationale that explains why certain properties of code are important for understanding and changing code. Objectives The objective for this study was to evaluate the Principles by determining their sufficiency and necessity for explaining why the style defects often found in students’ code are detrimental to code quality. We also wanted to understand the benefits and limitations of a Principles-based approach to classifying defects. Method We sourced from the literature two comprehensive, classified sets of defects found in students’ code. We mapped each defect in the source data sets to a Principle. Sufficiency and necessity were established by examining gaps in the mappings. Findings We successfully mapped all one hundred and thirty defects in the source data sets, establishing sufficiency. Most defects mapped to a single Principle, with five requiring further information before mapping could take place. All Principles were required for the mapping, confirming necessity. A comparison of defect- and Principles-based classifications revealed that the Principles-based approach enabled the identification of root causes of defects to support effective refactoring. Conclusions The assessment of the Principles for classifying student defects was positive. All defects were successfully classified and explained. The theoretical basis of the Principles resulted in categories that are more conducive to supporting future work on helping students to identify and remove quality issues. In future work, we will augment the Principles with examples based on the source defect sets and with targeted questions to support refactoring.
- 1 September 2026
- Published by Institute of Electrical and Electronics Engineers (IEEE) in Computer
- Vol. 59 (9) , 96-98
Making Software Metrics Useful
- 1 September 2026
- Published by Institute of Electrical and Electronics Engineers (IEEE) in Computer
- Vol. 59 (9) , 96-98
Making Software Metrics Useful
- Open Access
- 13 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 373-385
Analyzing Dependency Distribution Changes Arising from Code Smell Interactions
- 13 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 373-385
Open AccessAnalyzing Dependency Distribution Changes Arising from Code Smell Interactions
- Open Access
The Influence of Code Smells in Efferent Neighbors on Class Stability
Understanding what drives code instability is essential for effective software maintenance, as unstable classes require larger or more frequent edits and increase the risk of unintended side effects. Although code smells are widely believed to harm maintainability, most prior stability studies examine only the smells within the class being modified. In practice, however, classes can change because their efferent neighbors (i.e., the classes they depend on) are modified due to ripple effects that propagate along static dependencies, even if the class itself is clean. Such ripple effects may be more severe when the efferent neighbor exhibits code smells. In addition, code smells rarely occur alone. They often appear together within a class or across classes connected by static dependencies, a phenomenon known as code smell interrelation. Such interrelation can lead to code smell interaction, where smells are directly connected through static dependencies and may further compound maintainability issues. However, the effect of code smell interrelation and interaction on code quality remains largely underexplored. Therefore, this study investigates whether the presence of code smells in a class's efferent neighbors affects its stability, considering the factor of code smell interrelation and interaction. To achieve this, we mine one year of commit history from 100 top-starred GitHub projects, detect code smells and static dependencies, determine code smell interrelation and interaction, and model these factors as predictors of class stability.
Open AccessThe Influence of Code Smells in Efferent Neighbors on Class Stability
Understanding what drives code instability is essential for effective software maintenance, as unstable classes require larger or more frequent edits and increase the risk of unintended side effects. Although code smells are widely believed to harm maintainability, most prior stability studies examine only the smells within the class being modified. In practice, however, classes can change because their efferent neighbors (i.e., the classes they depend on) are modified due to ripple effects that propagate along static dependencies, even if the class itself is clean. Such ripple effects may be more severe when the efferent neighbor exhibits code smells. In addition, code smells rarely occur alone. They often appear together within a class or across classes connected by static dependencies, a phenomenon known as code smell interrelation. Such interrelation can lead to code smell interaction, where smells are directly connected through static dependencies and may further compound maintainability issues. However, the effect of code smell interrelation and interaction on code quality remains largely underexplored. Therefore, this study investigates whether the presence of code smells in a class's efferent neighbors affects its stability, considering the factor of code smell interrelation and interaction. To achieve this, we mine one year of commit history from 100 top-starred GitHub projects, detect code smells and static dependencies, determine code smell interrelation and interaction, and model these factors as predictors of class stability.
- 1 April 2025
- Published by Springer Nature
- p. 13-28
Veracity Debt: Practitioners Voices on Managing Software Requirements Concerning Veracity
- 1 April 2025
- Published by Springer Nature
- p. 13-28
Veracity Debt: Practitioners Voices on Managing Software Requirements Concerning Veracity
- Open Access
- 31 March 2025
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Computing Education
- Vol. 25 (1) , 1-39
CSM: A Code Style Model for Computing Educators
Objectives Code style is an important aspect of text-based programming because programs written with good style are considered easier to understand and change and so improve the maintainability of the delivered software product. However teaching code style is complicated by the existence of many style guides and standards that contain inconsistent, low-level advice. The objective of the study is to support educators in helping students understand the nature of these inconsistencies by highlighting the rationale behind rules and their contextual nature. Participants Seventy members of local and national computing science education (CSE) groups contributed in the exploratory phase. Fifty-two members of the ACM SIGCSE members mailing list and the Australasian Chapter contributed in the evaluation and refinement phases. These mailing lists represent a large, global population of CSE educators. Study Methods We created, evaluated and refined an abstract code style model ( CSM ) comprising a Definition and eight Principles for code style. For CSM creation, we took an exploratory approach based on an examination of the existing literature on code quality and style. To evaluate the level of community endorsement for the model, we analysed quantitative and qualitative data from an international survey questionnaire. We refined the CSM based on an analysis of the qualitative survey data. Findings Analysis of the data from the survey indicated a strong level of support for the CSM . Quantitative data revealed a general agreement with the Principles , with responses for five Principles achieving a minimum of 84 percent agreement and all Principles achieving a minimum of 66 percent agreement. Qualitative data contained very few comments that voiced dissatisfaction with a basic aspect of the model. We found that barriers to developing a community-wide CSM were the strongly-held beliefs about style held by some and the abstract nature of the CSM . Conclusions The creation of an abstract set of Principles for code style is generally perceived by the community to be worthwhile and important and our approach has high levels of endorsement. A validated version of the CSM has been created.
- 31 March 2025
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Computing Education
- Vol. 25 (1) , 1-39
Open AccessCSM: A Code Style Model for Computing Educators
Objectives Code style is an important aspect of text-based programming because programs written with good style are considered easier to understand and change and so improve the maintainability of the delivered software product. However teaching code style is complicated by the existence of many style guides and standards that contain inconsistent, low-level advice. The objective of the study is to support educators in helping students understand the nature of these inconsistencies by highlighting the rationale behind rules and their contextual nature. Participants Seventy members of local and national computing science education (CSE) groups contributed in the exploratory phase. Fifty-two members of the ACM SIGCSE members mailing list and the Australasian Chapter contributed in the evaluation and refinement phases. These mailing lists represent a large, global population of CSE educators. Study Methods We created, evaluated and refined an abstract code style model ( CSM ) comprising a Definition and eight Principles for code style. For CSM creation, we took an exploratory approach based on an examination of the existing literature on code quality and style. To evaluate the level of community endorsement for the model, we analysed quantitative and qualitative data from an international survey questionnaire. We refined the CSM based on an analysis of the qualitative survey data. Findings Analysis of the data from the survey indicated a strong level of support for the CSM . Quantitative data revealed a general agreement with the Principles , with responses for five Principles achieving a minimum of 84 percent agreement and all Principles achieving a minimum of 66 percent agreement. Qualitative data contained very few comments that voiced dissatisfaction with a basic aspect of the model. We found that barriers to developing a community-wide CSM were the strongly-held beliefs about style held by some and the abstract nature of the CSM . Conclusions The creation of an abstract set of Principles for code style is generally perceived by the community to be worthwhile and important and our approach has high levels of endorsement. A validated version of the CSM has been created.
- Open Access
- 12 February 2025
- Published by Association for Computing Machinery (ACM)
- p. 26-35
Distilling PEP 8 for Teaching Introductory Programming
- 12 February 2025
- Published by Association for Computing Machinery (ACM)
- p. 26-35
Open AccessDistilling PEP 8 for Teaching Introductory Programming
- Open Access
- 12 February 2025
- Published by Association for Computing Machinery (ACM)
- p. 1204-1210
KernelVM: Teaching Linux Kernel Programming through a Browser-Based Virtual Machine
Providing students with hands-on experience in kernel programming within a real-world operating system is highly beneficial in an Operating Systems (OS) course for teaching core operating system concepts and developing practical skills. However, accessing suitable devices for such hands-on experimentation poses significant challenges. Traditional solutions involve hosting virtual machines on cloud platforms, which are expensive and do not scale well with increasing student numbers. Additionally, many students' personal devices, such as Macs or iPads, have limited support for running Linux, creating further barriers. In this paper, we introduce KernelVM, a novel cost-effective platform that offers students a Linux virtual machine with full superuser access and pre-configured kernel programming toolchains. KernelVM is accessible via any modern browser on any device. It performs all computations locally within the user's browser, thus eliminating cloud computing costs. KernelVM provides a robust learning environment by incorporating interactive virtual hardware components and an automatic evaluation system, supporting a wide range of tasks, including multi-threaded cryptographic kernel modules and Linux drivers for hardware interaction. We detail the design of KernelVM, and describe our experiences incorporating it for the first time into an OS course with 159 undergraduate students. We found that KernelVM was instrumental in improving the quality and efficiency of hands-on learning experiences, with students reporting increased satisfaction and engagement due to the immediate feedback and the ability to experiment in a risk-free environment. Our experience suggests that KernelVM not only addresses the logistical challenges of kernel programming education, but it helps foster a highly interactive and engaging learning experience.
- 12 February 2025
- Published by Association for Computing Machinery (ACM)
- p. 1204-1210
Open AccessKernelVM: Teaching Linux Kernel Programming through a Browser-Based Virtual Machine
Providing students with hands-on experience in kernel programming within a real-world operating system is highly beneficial in an Operating Systems (OS) course for teaching core operating system concepts and developing practical skills. However, accessing suitable devices for such hands-on experimentation poses significant challenges. Traditional solutions involve hosting virtual machines on cloud platforms, which are expensive and do not scale well with increasing student numbers. Additionally, many students' personal devices, such as Macs or iPads, have limited support for running Linux, creating further barriers. In this paper, we introduce KernelVM, a novel cost-effective platform that offers students a Linux virtual machine with full superuser access and pre-configured kernel programming toolchains. KernelVM is accessible via any modern browser on any device. It performs all computations locally within the user's browser, thus eliminating cloud computing costs. KernelVM provides a robust learning environment by incorporating interactive virtual hardware components and an automatic evaluation system, supporting a wide range of tasks, including multi-threaded cryptographic kernel modules and Linux drivers for hardware interaction. We detail the design of KernelVM, and describe our experiences incorporating it for the first time into an OS course with 159 undergraduate students. We found that KernelVM was instrumental in improving the quality and efficiency of hands-on learning experiences, with students reporting increased satisfaction and engagement due to the immediate feedback and the ability to experiment in a risk-free environment. Our experience suggests that KernelVM not only addresses the logistical challenges of kernel programming education, but it helps foster a highly interactive and engaging learning experience.
- 1 January 2025
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 51 (2) , 449-465
A Holistic Approach to Design Understanding Through Concept Explanation
Complex software systems consist of multiple overlapping design structures, such as abstractions, features, crosscutting concerns, or patterns. This is similar to how a human body has multiple interacting subsystems, such as respiratory, digestive, or circulatory. Unlike in the medical domain, software designers do not have an effective way to distinguish, visualize, comprehend, and analyze these interleaving design structures. As a result, developers often struggle through the maze of source code. In this paper, we present an Automated Concept Explanation (ACE) framework that automatically extracts and categorizes major concepts from source code based on the roles that files play in design structures and their topic frequencies. Based on these categorized concepts, ACE recovers four categories of high-level design models using different algorithms and generates a natural language explanation for each. To assess if and how ACE can help developers better understand design structures, we conducted an empirical study where two groups of graduate students were assigned three design comprehension tasks: identifying feature-related files, identifying dependencies among features, and identifying design patterns used, in an open-source project. The results reveal that the students who used ACE can accomplish these tasks much faster and more accurately, and they acknowledged the usefulness of the categorized concepts and structures, multi-type high-level model visualization, and natural language explanations.
- 1 January 2025
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 51 (2) , 449-465
A Holistic Approach to Design Understanding Through Concept Explanation
Complex software systems consist of multiple overlapping design structures, such as abstractions, features, crosscutting concerns, or patterns. This is similar to how a human body has multiple interacting subsystems, such as respiratory, digestive, or circulatory. Unlike in the medical domain, software designers do not have an effective way to distinguish, visualize, comprehend, and analyze these interleaving design structures. As a result, developers often struggle through the maze of source code. In this paper, we present an Automated Concept Explanation (ACE) framework that automatically extracts and categorizes major concepts from source code based on the roles that files play in design structures and their topic frequencies. Based on these categorized concepts, ACE recovers four categories of high-level design models using different algorithms and generates a natural language explanation for each. To assess if and how ACE can help developers better understand design structures, we conducted an empirical study where two groups of graduate students were assigned three design comprehension tasks: identifying feature-related files, identifying dependencies among features, and identifying design patterns used, in an open-source project. The results reveal that the students who used ACE can accomplish these tasks much faster and more accurately, and they acknowledged the usefulness of the categorized concepts and structures, multi-type high-level model visualization, and natural language explanations.