Towards Automating Source-Consistent UML Refactorings

Gorp, Pieter Van; Stenten, Hans; Mens, Tom; Demeyer, Serge

doi:10.1007/978-3-540-45221-8_15

Cited by 55 publications

(37 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Refactorings for artifacts of individual types exist, e.g. for artifacts of object-oriented (Fowler, 1999), functional (Li, 2006), and logical programming languages (Schrijvers et al, 2004), and others (Van Gorp et al, 2003;Sunyé et al, 2001;Ambler, 2003).…”

Section: Multi-language Refactoringmentioning

confidence: 99%

“…The meta models FAMIX (Tichelaar, 2001), MOOSE (Ducasse et al, 2000), and UML (Van Gorp et al, 2003) are used for describing refactorings of OOP languages independently from the OOP language at hand. Therefore, FAMIX, MOOSE, as well as UML cannot be used to abstract artifacts of MLSAs in general.…”

Section: Related Workmentioning

confidence: 99%

“…Refactorings exist for several artifact types, e.g. source code of object-oriented programming languages, UML diagrams, and database schemas (Fowler, 1999;Li, 2006;Schrijvers et al, 2004;Van Gorp et al, 2003;Sunyé et al, 2001;Ambler, 2003). However, a refactoring for an artifact of one type does commonly not describe changes that must be done in artifacts of other types.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Hurdles in Multi-Language Refactoring of Hibernate Applications

Schink¹,

Kuhlemann²,

Saake³

et al. 2011

Proceedings of the 6th International Conference on Software and Database Technologies

View full text Add to dashboard Cite

Abstract:Different programming languages can be involved in the implementation of a single software application. In these software applications, source code of one programming language interacts with code of a different language. By refactoring an artifact of one programming language, the interaction of this artifact with an artifact written in another programming language may break. We present a study on refactoring an software application that contains artifacts of different languages.

show abstract

Section: Multi-language Refactoringmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Hurdles in Multi-Language Refactoring of Hibernate Applications

Schink¹,

Kuhlemann²,

Saake³

et al. 2011

Proceedings of the 6th International Conference on Software and Database Technologies

View full text Add to dashboard Cite

show abstract

“…The formal techniques in related work [7][8][9][10] address behavior preservation in model refactoring, but are in general tailored to a specific metamodel and limited to checking the behavior of certain models. Therefore, the transfer to different metamodels is, in general, quite difficult.…”

Section: Discussionmentioning

confidence: 99%

“…In practice, proving of behavior-preservation is not an easy task and therefore one normally relies on test suite executions and informal arguments in order to improve confidence that the behavior is preserved. On the other hand, formal approaches [7][8][9][10] have been also employed. A common issue is that behavior preservation is checked only for a certain number of models and their refactored versions.…”

Section: Introductionmentioning

confidence: 99%

Behavior Preservation in Model Refactoring Using DPO Transformations with Borrowed Contexts

Rangel

Lambers

König

et al.

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Behavior preservation, namely the fact that the behavior of a model is not altered by the transformations, is a crucial property in refactoring. The most common approaches to behavior preservation rely basically on checking given models and their refactored versions. In this paper we introduce a more general technique for checking behavior preservation of refactorings defined by graph transformation rules. We use double pushout (DPO) rewriting with borrowed contexts, and, exploiting the fact that observational equivalence is a congruence, we show how to check refactoring rules for behavior preservation without the need of considering specific models. When rules are behavior-preserving, their application will never change behavior, i.e., every model and its refactored version will have the same behavior. However, often there are refactoring rules describing intermediate steps of the transformation, which are not behavior-preserving, although the full refactoring does preserve the behavior. For these cases we present a procedure to combine refactoring rules to behavior-preserving concurrent productions in order to ensure behavior preservation. An example of refactoring for finite automata is given to illustrate the theory.

show abstract

A survey on UML model smells detection techniques for software refactoring

Mumtaz

Alshayeb

Mahmood

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

Bad smells tend to have a negative impact on software by degrading its quality. It is beneficial to detect model smells to avoid their propagation to later stages of software development. The objective of this paper is to present the state‐of‐the‐art research on techniques for detecting UML model bad smells. The detection techniques are compared and evaluated using a proposed evaluation framework. The framework consists of two parts. The first part of the framework compares the techniques in terms of the implemented approach, the investigated model, and the explored model smells, while the experimental design is explored in the second part of the framework. We found that the detection of bad smells in class and sequence diagrams is accomplished via design patterns, software metrics, and predefined rules, while model smells in use cases are detected using metrics and predefined rules. We also found that the class diagram is the most investigated UML model in the context of model smell detection, whereas there is a lack of work on other UML models. In addition, there is a scarcity of independent studies on sequence diagrams. Furthermore, the studies investigating class diagrams are mostly validated, whereas use case diagrams and sequence diagrams are rarely validated.

show abstract

Towards Automating Source-Consistent UML Refactorings

Cited by 55 publications

References 13 publications

Hurdles in Multi-Language Refactoring of Hibernate Applications

Hurdles in Multi-Language Refactoring of Hibernate Applications

Behavior Preservation in Model Refactoring Using DPO Transformations with Borrowed Contexts

A survey on UML model smells detection techniques for software refactoring

Contact Info

Product

Resources

About