Change-oriented software engineering

Ebraert, Peter; Vallejos, Jorge; Costanza, Pascal; Paesschen, Ellen Van; D'Hondt, Theo

doi:10.1145/1352678.1352680

Cited by 37 publications

(26 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…First-class change entities, modeled as objects in Robbes and Lanza's approach, represent the behaviour of the different kinds of changes required for a program (for example, to add, remove, or modify classes) (Ebraert et al, 2007).…”

Section: Change Reificationmentioning

confidence: 99%

Change-based test selection: an empirical evaluation

et al. 2015

View full text Add to dashboard Cite

Regression test selection (i.e., selecting a subset of a given regression test suite) is a problem that has been studied intensely over the last decade. However, with the increasing popularity of developer tests as the driver of the test process, more fine-grained solutions that work well within the context of the Integrated Development Environment (IDE) are in order. Consequently, we created two variants of a test selection heuristic which exploit fine-grained changes recorded during actual development inside the IDE. One variant only considers static binding of method invocations while the other variant takes dynamic binding into account. This paper investigates the tradeoffs between these two variants in terms of the reduction (i.e., How many tests could we omit from the test suite, and how much did we gain in runtime execution?) as well as the fault detection ability of the reduced test suite (i.e., Were tests omitted erroneously?). We used our approach on three distinct cases, two open source cases -Cruisecontrol and PMD-and one industrial case -Historia. Our results show that only considering static binding reduces the test suite significantly but occasionally omits a relevant test; considering dynamic binding rarely misses a test yet often boils down to running the complete test suite. Nevertheless, our analysis provides indications on when a given variant is more appropriate.

show abstract

Section: Change Reificationmentioning

confidence: 99%

Change-based test selection: an empirical evaluation

et al. 2015

View full text Add to dashboard Cite

show abstract

“…These sets validated our findings, as reported in the previous sections, but also confirmed the known limitation of this and any SLR: the limitation due to circumscribing the review and thus missing interesting papers. For example, our discussions with the colleagues working on FAMIX pointed us to works in which FAMIX was used to model program metadata and related data, including, but not limited to: Evolizer to analyze source code and software project data (Gall et al 2009), ChEOPS to represent changes as first-class entities for change-oriented software engineering (Ebraert et al 2007), and Orion to model simultaneous versions in a software version repository ). We did not include these works in our review because they were beyond the borders of our review.…”

Section: Limitationsmentioning

confidence: 99%

ProMeTA: a taxonomy for program metamodels in program reverse engineering

2018

View full text Add to dashboard Cite

To support program comprehension, maintenance, and evolution, metamodels are frequently used during program reverse engineering activities to describe and analyze constituents of a program and their relations. Reverse engineering tools often define their own metamodels according to the intended purposes and features. Although each metamodel has its own advantages, its limitations may be addressed by other metamodels. Existing works have evaluated and compared metamodels and tools, but none have considered all the possible characteristics and limitations to provide a comprehensive guideline for classifying, comparing, reusing, and extending program metamodels. To aid practitioners and researchers in classifying, comparing, reusing, and extending program metamodels and their corresponding reverse engineering tools according to the intended goals, we establish a conceptual framework with definitions of program metamodels and related concepts. We confirmed that any reverse engineering activity can be clearly described as a pattern based on the framework from the viewpoint of program metamodels. Then the framework is used (2018) 23:2323-2358 to provide a comprehensive taxonomy, named Program Metamodel TAxonomy (ProMeTA), which incorporates newly identified characteristics into those stated in previous works, which were identified via a systematic literature review (SLR) on program metamodels, while keeping the orthogonality of the entire taxonomy. Additionally, we validate the taxonomy in terms of its orthogonality and usefulness through the classification of popular metamodels.Empir Software Eng

show abstract

“…While the approaches described above -similar to our approach -provide an off-line analysis of the development history, there are approaches such as SpyWare [22,23] and CheOPS [7] that do an on-line analysis of the source code's history. These approaches are tightly integrated with a developer's environment and use this environment to monitor and record the changes that the developer makes to the source code.…”

Section: Mining Software Repositoriesmentioning

confidence: 99%

Time warp, an approach for reasoning over system histories

Gómez

Kellens

Brichau

et al. 2009

Proceedings of the Joint International and Annual ERCIM Workshops on Principles of Software Evolution (IWPSE) and Software Evol

Self Cite

View full text Add to dashboard Cite

The version history of a software system contains a wealth of information that can assist developers in their daily implementation and maintenance tasks. By reasoning over the role of certain code entities in previous versions of the system, developers can better understand their current state, assess the required maintenance and avoid making the same mistakes over and over again. Unfortunately, current approaches do not offer a means to easily extract specific information about the source code from such a version history. In this paper we present Time Warp, a library of logic predicates that builds on the SOUL language and the FAMIX and Hismo meta-models and that allows writing queries about the history of a system. By means of a number of concrete examples, we demonstrate how our approach can be used to express interesting queries over the version history of a system.

show abstract

Change-oriented software engineering

Cited by 37 publications

References 12 publications

Change-based test selection: an empirical evaluation

Change-based test selection: an empirical evaluation

ProMeTA: a taxonomy for program metamodels in program reverse engineering

Time warp, an approach for reasoning over system histories

Contact Info

Product

Resources

About