Serge Demeyer

Serge Demeyer

Auto-generated profile, based on publicly available information

Serge Demeyer

University of Antwerp, Antwerpen, Belgium

Research Focus & Metrics

Academic Career Length

32Years (1995-Present)

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

Representative Publications

View All Publications
1 January 1999
Verified
Conference Paper
Closed access
SDS. Ducasse
S. Ducasse
MRM. Rieger
M. Rieger
SDS. Demeyer
S. Demeyer
Code duplication is one of the factors that severely complicates the maintenance and evolution of large software systems. Techniques for detecting duplicated code exist but rely mostly on parsers, technology that has proven to be brittle in the face of different languages and dialects. In this paper we show that is possible to circumvent this hindrance by applying a language independent and visual approach, i.e. a tool that requires no parsing, yet is able to detect a significant amount of code duplication. We validate our approach on a number of case studies, involving four different implementation languages and ranging from 256 K up to 13 Mb of source code size.

15 September 2010 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
AZAndy Zaidman
Andy Zaidman
BRBart Van Rompaey
Bart Van Rompaey
ADArie van Deursen
Arie van Deursen
SDSerge Demeyer
Serge Demeyer
Many software production processes advocate rigorous development testing alongside functional code writing, which implies that both test code and production code should co-evolve. To gain insight in the nature of this co-evolution, this paper proposes three views (realized by a tool called TeMo) that combine information from a software project’s versioning system, the size of the various artifacts and the test coverage reports. We validate these views against two open source and one industrial software project and evaluate our results both with the help of log messages, code inspections and the original developers of the software system. With these views we could recognize different co-evolution scenarios (i.e., synchronous and phased) and make relevant observations for both developers as well as test engineers.

1 January 2005
Verified
Conference Paper
Open access
TMT. Mens
T. Mens
MWM. Wermelinger
M. Wermelinger
SDS. Ducasse
S. Ducasse
SDS. Demeyer
S. Demeyer
RHR. Hirschfeld
R. Hirschfeld
MJM. Jazayeri
M. Jazayeri
Humans will have to live with software for a long time. As demonstrated by the Y2K problem, computer professionals used a wrong time scale when thinking about software. Large software products live much longer than expected. It took a few decades to ...

1 April 2008
Verified
Conference Paper
Closed access
AZAndy Zaidman
Andy Zaidman
BRBart Van Rompaey
Bart Van Rompaey
SDSerge Demeyer
Serge Demeyer
ADArie van Deursen
Arie van Deursen
Engineering software systems is a multidisciplinary activity, whereby a number of artifacts must be created - and maintained - synchronously. In this paper we investigate whether production code and the accompanying tests co- evolve by exploring a project's versioning system, code coverage reports and size-metrics. Our main aim for studying this co-evolution is to create awareness with developers and managers alike about the testing process that is followed. We explore the possibilities of our technique through two open source case studies and observe a number of different co-evolution scenarios. We evaluate our results both with the help of log-messages and the original developers of the software system.

5 November 2007 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
BRBart Van Rompaey
Bart Van Rompaey
BBBart Du Bois
Bart Du Bois
SDSerge Demeyer
Serge Demeyer
MRMatthias Rieger
Matthias Rieger
As a fine-grained defect detection technique, unit testing introduces a strong dependency on the structure of the code. Accordingly, test coevolution forms an additional burden on the software developer which can be tempered by writing tests in a manner that makes them easier to change. Fortunately, we are able to concretely express what a good test is by exploiting the specific principles underlying unit testing. Analogous to the concept of code smells, violations of these principles are termed test smells. In this paper, we clarify the structural deficiencies encapsulated in test smells by formalizing core test concepts and their characteristics. To support the detection of two such test smells, General Fixture and Eager Test, we propose a set of metrics defined in terms of unit test concepts. We compare their detection effectiveness using manual inspection and through a comparison with human reviewing. Although the latter is the traditional means for test quality assurance, our results indicate it is not a reliable means for test smell detection. This work thus stresses the need for a more reliable detection mechanism and provides an initial contribution through the validation of test smell metrics.

1 January 2008
Verified
Book
Closed access
TMTom Mens
Tom Mens
SDSerge Demeyer
Serge Demeyer