Refactoring OCL annotated UML class diagrams

Marković, Slaviša; Baar, Thomas

doi:10.1007/s10270-007-0056-x

Cited by 39 publications

(7 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Refactoring Pull Up Attribute [10,17] can be used to move this attribute to an existing parent class and to remove all equal attributes from the sibling classes. If the attribute should not be moved to an existing parent class, refactoring Extract Superclass [13,17] can be used to create a new parent class and to pull up the attribute to it. The right-hand side of Figure 3 shows an example for the selection of potentially new smells after applying a specific refactoring.…”

Section: Manual Integrationmentioning

confidence: 99%

See 1 more Smart Citation

Integration of smells and refactorings within the Eclipse modeling framework

Arendt

Taentzer

2012

Proceedings of the Fifth Workshop on Refactoring Tools

View full text Add to dashboard Cite

Models are primary artifacts in model-based, and especially, in model-driven software development processes. Therefore, software quality and quality assurance frequently leads back to the quality and quality assurance of the involved models. In our approach, we propose a model quality assurance process that is based on static model analysis and uses techniques like model metrics and model smells. Based on the outcome of the model analysis, appropriate model refactoring steps are performed. Appropriate tools support the included techniques, i.e. metrics, smells, and refactorings, for models that are based on the Eclipse Modeling Framework (EMF). In this paper, we present the integration of the two model quality tools EMF Smell and EMF Refactor. This integration provides modelers with a quick and easy way to erase model smells by automatically suggesting appropriate model refactorings, and to get warnings in cases where new model smells come in by applying a certain refactoring.

show abstract

Section: Manual Integrationmentioning

confidence: 99%

“…However, some research prototypes for model refactoring are discussed in the literature, e.g. in [11,17,18]. Most of them are no longer maintained.…”

Section: Related Workmentioning

confidence: 99%

Integration of smells and refactorings within the Eclipse modeling framework

Arendt

Taentzer

2012

Proceedings of the Fifth Workshop on Refactoring Tools

View full text Add to dashboard Cite

show abstract

“…In PIM-to-PIM transformations, the context change is required, for instance, in the application of refactoring operations at the model level [7].…”

Section: -Example Conceptual Schemamentioning

confidence: 99%

“…On the other hand [1] tries to improve the understandability of OCL constraints but without considering the possibility of redefining them using a different context. [7] mentions context changes but restricts them to associations with multiplicity 1 on both association ends. Hence, as far as we know, ours is the first method able to deal completely with this kind of ICs' automatic transformations.…”

Section: -Example Conceptual Schemamentioning

confidence: 99%

Transforming OCL constraints

Cabot

Teniente

2006

Proceedings of the 2006 ACM Symposium on Applied Computing

View full text Add to dashboard Cite

Integrity constraints (ICs) play a key role in the definition of conceptual schemas. In the UML, ICs are usually specified as invariants written in the OCL. However, due to the high expressiveness of the OCL, the designer has different syntactic alternatives to express each IC, mainly depending on the type used as a context of the constraint. The method presented in this paper assists the designer during the definition of ICs by means of automatically transforming the initially defined constraints into equivalent alternatives. The method is also useful in the context of the MDA, where the choice of a particular alternative has a direct effect on the efficiency of the automatically generated implementation.

show abstract

“…While existing model transformation techniques always take into account structural constraints, they often ignore the attached OCL constraints [14,18]. This is because model transformation rules are defined over metamodel elements while attached OCL constraints are defined in a different technical space.…”

Section: Introductionmentioning

confidence: 99%

A Formalisation of Constraint-Aware Model Transformations

Rutle¹,

Rossini

Lamo³

et al. 2010

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. This paper introduces a formal approach to the definition of constraint-aware model transformations. The proposed approach is based on the Diagram Predicate Framework and extends graph transformations with the ability to handle constraints in the definition and execution of model transformations. In particular, it uses non-deleting rules that are typed over the metamodel of a joined modelling language which is constructed from the source and target languages. Furthermore, the application of transformation rules is formalised as a pushout construction that creates a model which is typed over the metamodel of the joined modelling language. Finally, the target model is obtained from the created model by a pullback construction.

show abstract

Refactoring OCL annotated UML class diagrams

Cited by 39 publications

References 19 publications

Integration of smells and refactorings within the Eclipse modeling framework

Integration of smells and refactorings within the Eclipse modeling framework

Transforming OCL constraints

A Formalisation of Constraint-Aware Model Transformations

Contact Info

Product

Resources

About