Exploiting the hierarchical structure of rule-based specifications for decision planning

Artur Boronat, Roberto Bruni, Alberto Lluch Lafuente, Ugo Montanari, Generoso Paolillo

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

Abstract

Rule-based specifications have been very successful as a declarative approach in many domains, due to the handy yet solid foundations offered by rule-based machineries like term and graph rewriting. Realistic problems, however, call for suitable techniques to guarantee scalability. For instance, many domains exhibit a hierarchical structure that can be exploited conveniently. This is particularly evident for composition associations of models. We propose an explicit representation of such structured models and a methodology that exploits it for the description and analysis of model- and rule-based systems. The approach is presented in the framework of rewriting logic and its efficient implementation in the rewrite engine Maude and is illustrated with a case study.
Original languageEnglish
Title of host publicationFormal Techniques for Distributed Systems : Joint 12th IFIP WG 6.1 International Conference, FMOODS 2010 and 30th IFIP WG 6.1 International Conference, FORTE 2010, Amsterdam, The Netherlands, June 7-9, 2010. Proceedings
PublisherSpringer Berlin Heidelberg
Publication date2010
Pages2-16
ISBN (Print)978-3-642-13463-0
ISBN (Electronic)978-3-642-13464-7
DOIs
Publication statusPublished - 2010
Externally publishedYes
EventInternational Conference on Formal Techniques for Distributed Systems - Amsterdam, Netherlands
Duration: 7 Jun 20109 Jun 2010

Conference

ConferenceInternational Conference on Formal Techniques for Distributed Systems
CountryNetherlands
CityAmsterdam
Period07/06/201009/06/2010
SeriesLecture Notes in Computer Science
Volume6117
ISSN0302-9743

Fingerprint Dive into the research topics of 'Exploiting the hierarchical structure of rule-based specifications for decision planning'. Together they form a unique fingerprint.

Cite this