From UML to Alloy and Back Again

Shah, Seyyed; Anastasakis, Kyriakos; Bordbar, Behzad

doi:10.1007/978-3-642-12261-3_16

Cited by 25 publications

(19 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Conceptually, the graph generation approach could be applied on other modeling formalisms too, e.g. UML Class Diagrams for defining the types and Object Constraint Language (OCL, [9]) for defining constraints as in [19], [35].…”

Section: Domain-specific Modeling Languagesmentioning

confidence: 99%

“…There are several approaches aiming to validate standardized engineering models enriched with OCL constraints [58] by relying upon different back-end logic-based approaches such as constraint logic programming [36], [59], [60], SAT-based model finders (like Alloy) [7], [16], [35], [50], [51], [61], [62], [63], CSP solvers [64], first-order logic [65], constructive query containment [66] or higher-order logic [67]. Partial snapshots and WF constraints can be uniformly represented as constraints [7].…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Automated Generation of Consistent Graph Models With Multiplicity Reasoning

Marussy

Semeráth

Varró

2022

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Advanced tools used in model-based systems engineering (MBSE) frequently represent their models as graphs. In order to test those tools, the automated generation of well-formed (or intentionally malformed) graph models is necessitated which is often carried out by solver-based model generation techniques. In many model generation scenarios, one needs more refined control over the generated unit tests to focus on the more relevant models. Type scopes allow to precisely define the required number of newly generated elements, thus one can avoid the generation of unrealistic and highly symmetric models having only a single type of elements. In this paper, we propose a 3-valued scoped partial modeling formalism, which innovatively extends partial graph models with predicate abstraction and counter abstraction. As a result, well-formedness constraints and multiplicity requirements can be evaluated in an approximated way on incomplete (unfinished) models by using advanced graph query engines with numerical solvers (e.g. IP or LP solvers). Based on the refinement of 3-valued scoped partial models, we propose an efficient model generation algorithm that generates models that are both well-formed and satisfy the scope requirements. We show that the proposed approach scales significantly better than existing SAT-solver techniques or the original graph solver without multiplicity reasoning. We illustrate our approach in a complex design-space exploration case study of collaborating satellites introduced by researchers at NASA Jet Propulsion Lab.

show abstract

Section: Domain-specific Modeling Languagesmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Automated Generation of Consistent Graph Models With Multiplicity Reasoning

Marussy

Semeráth

Varró

2022

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

show abstract

“…Shah et al [32] proposed a model transformation from Alloy to UML to convert model instances generated by the Alloy Analyzer to UML Object Diagrams. This translation complements the UML2Alloy tool [2,1], which must be used before to generate an Alloy specification, and can be used to map back to UML counterexamples of UML+OCL specifications found using the Alloy Analyzer.…”

Section: Related Workmentioning

confidence: 99%

Translating between Alloy specifications and UML class diagrams annotated with OCL

2013

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

“…Note that the current paper focuses execution traces and their replaying, therefore related work regarding traceability is not detailed. Approaches regarding traceability models [11,39,48] generally define static traceability models which record the correspondence between various model structures and suggest techniques, methods and tools for generating, managing or processing such models.…”

Section: Related Workmentioning

confidence: 99%

Replaying Execution Trace Models for Dynamic Modeling Languages

Hegedüs¹,

Ráth²,

Varró³

2012

Per. Pol. Elec. Eng.

View full text Add to dashboard Cite

Back-end analysis tools aiming to carry out model-based verification and validation of dynamic behavioral models frequently produce sequences of simulation steps (called execution traces) as their output. In order to support back-annotation of such traces, we need to store and replay them within a modeling environment (outside the analysis tool). In the paper, we present a technique for replaying recorded execution traces of dynamic modeling languages. Our approach complements static and dynamic metamodels by introducing a generic execution trace metamodel which is used to replay completed executions of a simulation directly over the dynamic model. Furthermore, we present a technique to drive a simulation according to execution trace models. Our approach will be exemplified by the modeling language and trace information of the SAL model checker and BPEL business processes.

show abstract

From UML to Alloy and Back Again

Cited by 25 publications

References 12 publications

Automated Generation of Consistent Graph Models With Multiplicity Reasoning

Automated Generation of Consistent Graph Models With Multiplicity Reasoning

Translating between Alloy specifications and UML class diagrams annotated with OCL

Replaying Execution Trace Models for Dynamic Modeling Languages

Contact Info

Product

Resources

About