Refactoring a Java code base to AspectJ: an illustrative example

Monteiro, Miguel P.; Fernandes, João M.

doi:10.1109/icsm.2005.75

Cited by 19 publications

(30 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This strategy leads to the following grouping: (1) extraction of CCCs, (2) improvement of the internal structure of an aspect and (3) generalisation of aspects. The sequence of code transformations described in [29] also fits naturally with this grouping.…”

Section: Grouping the Refactoringsmentioning

confidence: 73%

“…The code examples presented at the end of each description found in this paper originate from those test sessions, as well as the refactoring process described in detail in [29]. 1 The latter also serves as a first validation effort.…”

Section: The Approachmentioning

confidence: 99%

“…For instance, they do not account for uses of reflection. Likewise, they do not deal with the fragile pointcut problem [24], which is caused by the fact that almost all refactorings can potentially break existing aspects, particularly pointcuts (in [28,29] we call it the fragile base code problem). We believe human programmers will be able to thoroughly deal with this problem only when provided with a new generation of tools, specifically designed to account for the presence of aspects.…”

Section: Overview Of the Refactoringsmentioning

confidence: 99%

See 2 more Smart Citations

Towards a Catalogue of Refactorings and Code Smells for AspectJ

Monteiro

Fernandes

2006

Transactions on Aspect-Oriented Software Development I

View full text Add to dashboard Cite

Abstract. In this paper, we contribute to the characterisation of a programming style specific to aspect-oriented programming. For this purpose, we present a collection of refactorings for aspect-oriented source code, comprising refactorings to enable extraction to aspects of crosscutting concerns from objectoriented legacy code, the subsequent tidying up of the extracted aspects and factoring out of common code from similar aspects to superaspects. The second group of refactorings is documented in detail. In addition, we propose some new aspect-oriented code smells, including one smell that is specific to aspect modules. We also propose a reinterpretation of some of the traditional objectoriented code smells in the light of aspect-orientation, to detect the presence of crosscutting concerns.

show abstract

Section: Grouping the Refactoringsmentioning

confidence: 73%

Section: The Approachmentioning

confidence: 99%

Section: Overview Of the Refactoringsmentioning

confidence: 99%

See 1 more Smart Citation

Towards a Catalogue of Refactorings and Code Smells for AspectJ

Monteiro

Fernandes

2006

Transactions on Aspect-Oriented Software Development I

View full text Add to dashboard Cite

show abstract

“…Monteiro et al [16] and Hannemann et al [9] separately conducted studies that applied AO refactorings incrementally on small code examples that use design patterns such as the Observer Pattern. Marin also illustrated the AO refactoring approach on JHotDraw project and completely extracted the Undo concern into an aspect [12].…”

Section: Related Workmentioning

confidence: 99%

Bridging the gap between aspect mining and refactoring

Yuen

Robillard

2007

Proceedings of the 3rd Workshop on Linking Aspect Technology and Evolution

View full text Add to dashboard Cite

Aspect-mining techniques help to identify crosscutting structure that could potentially be modularized through objectoriented (OO) or aspect-oriented refactoring (AO). This paper describes a case study in which we used aspect-mining techniques to identify and refactor crosscutting concerns using aspect-oriented programming. We observed that, in our case, there were many subtle variations in the implementation of the concerns that made them non-trivial to modularize with AO refactoring. In the end, we solved our modularization problem using traditional OO refactoring. We conclude that there exists an important gap between the identification of crosscutting concerns and the technologies available to mitigate the problem.

show abstract

“…Accessing wrapped code through an Adapter, accepting a Visitor into a data structure, notifying a model change to Observers, or invoking a software system piece of functionality through a Command, are just some examples of scattered code related to design pattern usage [22,17].…”

Section: Introductionmentioning

confidence: 99%