Translating Alloy Specifications to UML Class Diagrams Annotated with OCL

Garis, Ana Gabriela; Cunha, Alcino; Riesco, Daniel Eduardo

doi:10.1007/978-3-642-24690-6_16

Cited by 8 publications

(9 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Therefore, approaches using Alloy as a basis for constraint solving engine are also restricted by this functionality. [4,[37][38][39][40]. Further, Alloy's engine is limited to unranked constraints so users are not able to rank individual constraints, whereas our approach focuses on maximising all ranked features.…”

Section: Related Workmentioning

confidence: 99%

Finding Achievable Features and Constraint Conflicts for Inconsistent Metamodels

2017

Modelling Foundations and Applications

View full text Add to dashboard Cite

Determining the consistency of a metamodel is a task of generating a metamodel instance that not only meets structural constraints but also constraints written in Object Constraint Language (OCL). Those constraints can be conflicting, resulting in inconsistencies. When this happens, the existing techniques and tools have no knowledge about which constraints are achievable and which ones cause the conflicts. In this paper, we present an approach to finding achievable metamodel features and constraint conflicts for inconsistent metamodels. This approach allows users to rank individual metamodel features and works by reducing it to a weighted maximum satisfiability modulo theories (MaxSMT). This reduction allows us to utilise SMT solvers to tackle multiple ranked constraints and at the same time locate conflicts among them. We have prototyped this approach, incorporated it into an existing modelling tool, and evaluated it against a benchmark. The preliminary results show that our approach is promising and scalable.

show abstract

Section: Related Workmentioning

confidence: 99%

Finding Achievable Features and Constraint Conflicts for Inconsistent Metamodels

2017

Modelling Foundations and Applications

View full text Add to dashboard Cite

show abstract

“…We first proposed the translation from Alloy local state idiom to UML+OCL in [14]. The present work improves that translation by allowing both mutable and inmutable fields in signature definitions, enum signatures, arbitrary closures of relational expressions, integer expressions # for relations of arbitrary arity, among other minor improvements.…”

Section: Related Workmentioning

confidence: 99%

Translating between Alloy specifications and UML class diagrams annotated with OCL

2013

Self Cite

View full text Add to dashboard Cite

Model-Driven Engineering (MDE) is a Software Engineering approach based on model transformations at di↵erent abstraction levels. It prescribes the development of software by successively transforming models from abstract (specifications) to more concrete ones (code). Alloy is an increasingly popular lightweight formal specification language that supports automatic verification. Unfortunately, its widespread industrial adoption is hampered by the lack of an ecosystem of MDE tools, namely code generators. This paper presents a model transformation from Alloy to UML Class Diagrams annotated with OCL (UML+OCL), and shows how an existing transformation from UML+OCL to Alloy can be improved to handle dynamic issues. The proposed bidirectional transformation enables a smooth integration of Alloy in current MDE contexts, by allowing UML+OCL specifications to be transformed to Alloy for validation and verification, to correct and possibly refine them inside Alloy, and to translate them back to UML+OCL for sharing with stakeholders or to reuse current Model-Driven Architecture (MDA) tools to refine them towards code.

show abstract

“…The work discussed in [19] aims to check the consistency between class and object diagrams by explicitly modeling object diagram concepts in Alloy. A backward transformation from original Alloy specifications into UML and OCL models is presented in [8]. The authors in [4] translate conceptual models described in OntoUML for validation purposes into Alloy.…”

Section: Related Workmentioning

confidence: 99%

From UML and OCL to Relational Logic and Back

Kuhlmann

Gogolla

2012

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Languages like UML and OCL are used to precisely model systems. Complex UML and OCL models therefore represent a crucial part of model-driven development, as they formally specify the main system properties. Consequently, creating complete and correct models is a critical concern. For this purpose, we provide a lightweight model validation method based on efficient SAT solving techniques. In this paper, we present a transformation from UML class diagram and OCL concepts into relational logic. Relational logic in turn represents the source for advanced SAT-based model instance finders like Kodkod. This paper focuses on a natural transformation approach which aims to exploit the features of relational logic as directly as possible through straitening the handling of main UML and OCL features. This approach allows us to explicitly benefit from the efficient handling of relational logic in Kodkod and to interpret found results backwards in terms of UML and OCL.

show abstract

Translating Alloy Specifications to UML Class Diagrams Annotated with OCL

Cited by 8 publications

References 12 publications

Finding Achievable Features and Constraint Conflicts for Inconsistent Metamodels

Finding Achievable Features and Constraint Conflicts for Inconsistent Metamodels

Translating between Alloy specifications and UML class diagrams annotated with OCL

From UML and OCL to Relational Logic and Back

Contact Info

Product

Resources

About