Ewan Tempero

Ewan Tempero

Auto-generated profile, based on publicly available information

Ewan Tempero

University of Auckland

Research Focus & Metrics

Academic Career Length

37Years (1990-Present)

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

Representative Publications

View All Publications
1 October 2009
Verified
Conference Paper
Closed access
MRMehwish Riaz
Mehwish Riaz
EMEmilia Mendes
Emilia Mendes
ETEwan Tempero
Ewan Tempero
This paper presents the results of a systematic review conducted to collect evidence on software maintainability prediction and metrics. The study was targeted at the software quality attribute of maintainability as opposed to the process of software maintenance. The evidence was gathered from the selected studies against a set of meaningful and focused questions. 710 studies were initially retrieved; however of these only 15 studies were selected; their quality was assessed; data extraction was performed; and data was synthesized against the research questions. Our results suggest that there is little evidence on the effectiveness of software maintainability prediction techniques and models.

12 January 2007 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
HMHayden Melton
Hayden Melton
ETEwan Tempero
Ewan Tempero

9 March 2011
Verified
Conference Paper
Open access
PDF file
PDPaul Denny
Paul Denny
ALAndrew Luxton-Reilly
Andrew Luxton-Reilly
ETEwan Tempero
Ewan Tempero
JHJacob Hendrickx
Jacob Hendrickx
Drill and practice exercises enable students to master skills needed for more sophisticated programming. A barrier to providing such activities is the effort required to set up the programming environment. Testing is an important component to writing good software, but it is difficult to motivate students to write tests. In this paper we describe and evaluate CodeWrite, a web-based tool that provides drill and practice support for Java programming, and for which testing plays a central role in its use. We describe how we have used CodeWrite in a CS1 course, and demonstrate its effectiveness in providing good coverage of the language features presented in the course.

1 June 1998 in ACM SIGCSE Bulletin
Verified
Journal Article
Open access
RBRobert Biddle
Robert Biddle
ETEwan Tempero
Ewan Tempero
In this paper we will examine the Java language, and consider how easy it is for beginning programmers to learn. We address primarily the issues that arise directly from the language itself, and discuss whether the promises are compromised by the pitfalls. This analysis is the result of our teaching of Java to people in industry, our consideration of whether Java is suitable as a first programming language for university students, and our earlier work involving similar issues with regard to C++.

1 September 2012
Verified
Conference Paper
Closed access
GDGiuseppe Destefanis
Giuseppe Destefanis
RTRoberto Tonelli
Roberto Tonelli
ETEwan Tempero
Ewan Tempero
GCGiulio Concas
Giulio Concas
Michele MarchesiMichele Marchesi
Michele Marchesi
One of the goals of Software Engineering is to reduce, or at least to try to control, the defectiveness of software systems during the development phase. The aim of our study is to analyze the relationship between micro patterns (introduced by Gil and Maman) and faults in a software system. Micro patterns are similar to design patterns, but their characteristic is that they can be identified automatically, and are at a lower level of abstraction with respect to design patterns. Our study aims to show, through empirical studies of open source software systems, which categories of micro patterns are more correlated to faults. Gil and Maman demonstrated, and subsequent studies confirmed, that 75% of the classes of a software system are covered by micro patterns. In our study we also analyze the relationship between faults and the remaining 25% of classes that do not match with any micro pattern. We found that these classes are more likely to be fault-prone than the others. We also studied the correlation among all the micro patterns of the catalog, in order to verify the existence of relationships between them.

29 January 2024
Verified
Conference Paper
Open access
DKDiana Kirk
Diana Kirk
ALAndrew Luxton-Reilly
Andrew Luxton-Reilly
ETEwan Tempero
Ewan Tempero
It is widely acknowledged that code style is an important aspect of text-based programming. This is because programs written with good style are considered easier to understand and change and so improve the maintainability of the delivered software product. However, it is difficult for educators to find appropriate guidance on teaching style concepts because the available advice is often conflicting or language-specific. In this paper, we describe an exploratory study to create a set of code style principles that can be used by educators to support their teaching. The abstract nature of the principles provides a means of reconciling the inconsistencies in style guidelines while forming a basis for presenting to students the key concepts for understanding and changing code. We extracted from four software product quality models the code attributes that relate to understanding and changing code and elicited feedback from colleagues to consolidate these into the principles. Principles relate to Language, Layout, Constructs, Design, Redundancy, Implementations, Repetition and Structure. To evaluate the principles, we mapped some common style guidelines to them. Our contribution is a set of high level principles that support the teaching of code style. In future work we will evaluate the principles within the wider community and in the classroom context.