2013
DOI: 10.1007/s10270-013-0353-5
|View full text |Cite
|
Sign up to set email alerts
|

Translating between Alloy specifications and UML class diagrams annotated with OCL

Abstract: 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 p… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
34
0
1

Year Published

2013
2013
2023
2023

Publication Types

Select...
6
1
1

Relationship

1
7

Authors

Journals

citations
Cited by 41 publications
(35 citation statements)
references
References 29 publications
0
34
0
1
Order By: Relevance
“…In [22] the transformation is done in a reverse direction, but includes similar approach for mapping the Alloy language elements to UML and OCL. The main difference between our work and this solution is that the engineer should use Alloy to formalize the model and do the V&V tasks, while we allow the usage of pure EMF and OCL.…”
Section: Validation Of Ocl Enriched Metamodelsmentioning
confidence: 99%
“…In [22] the transformation is done in a reverse direction, but includes similar approach for mapping the Alloy language elements to UML and OCL. The main difference between our work and this solution is that the engineer should use Alloy to formalize the model and do the V&V tasks, while we allow the usage of pure EMF and OCL.…”
Section: Validation Of Ocl Enriched Metamodelsmentioning
confidence: 99%
“…Ensuring that two equal instances of parameters cannot describe (i.e., be associated to) the same object is a reasoning task that can be solved by many current UML/OCL reasoning tools [8,9,10,5].…”
Section: Using Uml/ocl To Describe the Servicementioning
confidence: 99%
“…E.g., we could use Alloy [8], USE [9], UMLtoCSP [10], or AuRUS [5]. Moreover, these tools are capable of computing the counterexample I that proves when a data-service would compute an undesired output for the data-request.…”
Section: Discovering the Servicesmentioning
confidence: 99%
“…MDE artifacts are translated into Alloy, and then we rely on these features to check consistency and find repairs, respectively. The technical details of such translations have been presented in previous work [12], [13]. Alloy also has an instance visualizer, to which we resort to depict models to the user.…”
Section: B Implementationmentioning
confidence: 99%
“…At the core of Echo we have the following translations: ECore → Alloy embeds ECore meta-models in Alloy [13]; OCL → Alloy translates the OCL constraints over the meta-model to Alloy [13]; XMI ↔ Alloy translates XMI models to and from Alloy instances [12]; QVT-R → Alloy embeds QVT-R transformations, as well as the underlying semantics, in Alloy [12].…”
Section: B Implementationmentioning
confidence: 99%