Evaluating the performance of model transformation styles with Maude

Roberto Bruni, Alberto Lluch Lafuente

Research output: Chapter in Book/Report/Conference proceedingArticle in proceedingsResearchpeer-review


Rule-based programming has been shown to be very successful in many application areas. Two prominent examples are the specification of model transformations in model driven development approaches and the definition of structured operational semantics of formal languages. General rewriting frameworks such as Maude are flexible enough to allow the programmer to adopt and mix various rule styles. The choice between styles can be biased by the programmer’s background. For instance, experts in visual formalisms might prefer graph-rewriting styles, while experts in semantics might prefer structurally inductive rules. This paper evaluates the performance of different rule styles on a significant benchmark taken from the literature on model transformation. Depending on the actual transformation being carried out, our results show that different rule styles can offer drastically different performances. We point out the situations from which each rule style benefits to offer a valuable set of hints for choosing one style over the other.
Original languageEnglish
Title of host publicationFormal Aspects of Component Software : 8th International Symposium, FACS 2011, Oslo, Norway, September 14-16, 2011, Revised Selected Papers
PublisherSpringer Berlin Heidelberg
Publication date2012
ISBN (Print)978-3-642-35742-8
ISBN (Electronic)978-3-642-35743-5
Publication statusPublished - 2012
Externally publishedYes
Event8th International Symposium on Formal Aspects of Component Software (FACS 2011) - Oslo, Norway
Duration: 14 Sep 201116 Sep 2011
Conference number: 8


Conference8th International Symposium on Formal Aspects of Component Software (FACS 2011)
Internet address
SeriesLecture Notes in Computer Science


Dive into the research topics of 'Evaluating the performance of model transformation styles with Maude'. Together they form a unique fingerprint.

Cite this