Redesign of UML class diagrams: a formal approach

Kosiuczenko, Piotr

doi:10.1007/s10270-007-0068-6

Cited by 10 publications

(9 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Similarly in [19], author proposed a method, called interpretation function, for transforming constraints which allows for the extension of a mapping defined on a few model elements. This function is used first to redesign UML class diagram models.…”

Section: A Constraint Transformationmentioning

confidence: 99%

Assistance System for OCL Constraints Adaptation during Metamodel Evolution

Hassam¹,

Sadou²,

Gloahec³

et al. 2011

2011 15th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

Abstract-Metamodels evolve over time, as well as other artifacts. In most cases, this evolution is performed manually by stepwise adaptation. In MDE, metamodels are described using the MOF language. Often OCL constraints are added to metamodels in order to ensure consistency of their instances (models). However, during metamodel evolution these constraints are omitted or manually rewritten, which is time consuming and error prone.We propose a tool to help the designer to make a decision on the constraints attached to a metamodel during its evolution. Thus, the tool highlights the constraints that should disappear after evolution and makes suggestions for those which need adaptation to remain consistent. For the latter case, we formally describe how the OCL constraints have to be transformed to preserve their syntactical correctness. Our adaptation rules are defined using QVT which is the OMG standard language for specifying model-to-model transformations. I. INTRODUCTION Model Driven Engineering (MDE)[1] raises the abstraction's level of software development from code to models, with a great emphasis on focusing the developer concerns on the problem domain rather than on the underlying technologies. Metamodels are the definition of abstract syntax of languages. However, structural constructions of metamodeling languages do not allow to express completely the syntax of a language (e.g. context-sensitive properties). In consequence, to get coherent models, it is necessary to add constraints expressed using the Object Constraint Language (OCL) [2]. Moreover, metamodels evolve over time like other software artifacts [3], [4], due to several reasons: to be consistent with the evolution of the application domain scope, to improve or correct the abstract syntax of the language, etc. As a consequence, these changes may break consistency of related terminal models. The risks stem from the fact that constraints attached to metamodels are either omitted or manually rewritten, which is time consuming and error prone [4], [5].To address this problem, we propose an approach in order to assist designers in constraint adaptation during a stepwise evolution [6] of a metamodel. This approach consists in identifying the impact of a change, made at the metamodel, on its associated constraints. After each modification of the

show abstract

Section: A Constraint Transformationmentioning

confidence: 99%

Assistance System for OCL Constraints Adaptation during Metamodel Evolution

Hassam¹,

Sadou²,

Gloahec³

et al. 2011

2011 15th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

show abstract

“…These functions have several useful properties. They preserve equational proofs, proofs using propositional tautologies, resolution rule and proofs by induction [Kos04]. From our perspective, the following property is the most important: Let the redesign diagram like the one in Def.…”

Section: Interpretation Functionsmentioning

confidence: 99%

“…According to the convention introduced in [Kos04], classes with the same names in both diagrams are implicitly related by a trace relationship. We only need to draw the dashed arrows between attribute and link names.…”

Section: A Redesign Example -Inline Class Refactoring Patternmentioning

confidence: 99%

“…Interpretation functions [Kos04] (see also [Kos01]) can be very useful as a vehicle for an automatic transformation of OCL constraints when changes to class diagrams are performed. An interpretation function is a partial function generated by term mappings with ortogonal domain [Kos04]. These functions have several useful properties.…”

Section: Interpretation Functionsmentioning

confidence: 99%

“…Translation of these OCL constraints to Casl logic is straightforward using the method described in [BHTW99]. As in [Kos04] we call the function that takes an OCL annotated UML class diagram and produces a specification in Casl institution a translation function Trans. Formally, since the whole class diagram can be described as an OCL sentence, Trans is a mapping of OCL terms to Casl formulas.…”

Section: Formalising Uml Class Diagramsmentioning

confidence: 99%

See 2 more Smart Citations

Property Preserving Redesign of Specifications

Zawłocki

Marczyński

Kosiuczenko

2005

Algebra and Coalgebra in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. In the traditional formal approach to system specification and implementation, the software development process consists of a number of refinement steps which transform the initial specification into its correct realisation. This idealised view can hardly capture common situations when a specification changes in a non-incremental way, e.g. when client requirements change or new software technologies emerge. An extra flexibility can be added to the development process by allowing for a redesign of specifications, in addition to refinement steps. In this paper, the notion of specification redesign is formalised for an arbitrary institution. Basic properties of redesign are investigated and the formalism is applied to provide a formal semantics for UML class diagram transformations. As examples, two refactoring patterns are described in terms of class diagrams and interpreted as redesigns of corresponding algebraic specifications.

show abstract

Refinement-Preserving Co-evolution

Ruhroth

Wehrheim

2009

Formal Methods and Software Engineering

View full text Add to dashboard Cite

Redesign of UML class diagrams: a formal approach

Cited by 10 publications

References 20 publications

Assistance System for OCL Constraints Adaptation during Metamodel Evolution

Assistance System for OCL Constraints Adaptation during Metamodel Evolution

Property Preserving Redesign of Specifications

Refinement-Preserving Co-evolution

Contact Info

Product

Resources

About