Atl

Jouault, Frédéric; Allilaire, Freddy; Bézivín, Jean; Kurtev, Ivan; Valduriez, Patrick

doi:10.1145/1176617.1176691

Cited by 107 publications

(11 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Models are transformed into different models of the same or a different meta-model via the so-called model transformations. Driven by the appeal of DSLs, a plethora of dedicated MTLs have been introduced since the emergence of MDE as a software development approach [3,7,38,43]. Unlike general-purpose programming languages, MTLs are designed for the sole purpose of enabling developers to transform models.…”

Section: Model Transformation Languagesmentioning

confidence: 99%

Claimed advantages and disadvantages of (dedicated) model transformation languages: a systematic literature review

2020

View full text Add to dashboard Cite

There exists a plethora of claims about the advantages and disadvantages of model transformation languages compared to general-purpose programming languages. With this work, we aim to create an overview over these claims in the literature and systematize evidence thereof. For this purpose, we conducted a systematic literature review by following a systematic process for searching and selecting relevant publications and extracting data. We selected a total of 58 publications, categorized claims about model transformation languages into 14 separate groups and conceived a representation to track claims and evidence through the literature. From our results, we conclude that: (i) the current literature claims many advantages of model transformation languages but also points towards certain deficits and (ii) there is insufficient evidence for claimed advantages and disadvantages and (iii) there is a lack of research interest into the verification of claims.

show abstract

Section: Model Transformation Languagesmentioning

confidence: 99%

Claimed advantages and disadvantages of (dedicated) model transformation languages: a systematic literature review

2020

View full text Add to dashboard Cite

show abstract

“…Moreover, intra-model storage of traceability links is a human-friendly approach but progressively pollutes the models involved with information of secondary importance. The authors of Jouault et al [14] propose an extension of the UML use case metamodel to refine an abstract use case to more refined ones. The refinement of use cases enables to trace use cases at different abstraction levels, but the authors do not explain how to establish these traces.…”

Section: Related Workmentioning

confidence: 99%

Traceability and Synchronization Between BPMN and UML Use Case Models

Bouzidi¹,

Haddar²,

Haddar³

2019

ISI

View full text Add to dashboard Cite

The purpose of this paper is to ensure and maintain the alignment between business modeling and requirement elicitation. To do this, we propose an approach that combines the strengths of traceability and model transformations to bridge the gap between BPMN model and the UML use Case models in particular, we propose an intermediate integrated model (BPSUC), and bidirectional transformation rules between the use case and BPMN models into the BPSUC and vice versa. We have implemented an editor to design and visualize BPSUC, and ATL transformation rules to carry out transformation and have successfully tested our approach on a case study, and evaluation criteria. The engineers and the business design can use BPSUC to work together in a single integrated diagram as well as they can synchronize their initial model through the bidirectional model transformations.

show abstract

“…Graph transformation allows one to safely apply graph‐transformation rules by assessing if they can be applied in parallel or sequentially and whether the application order matter . It takes the assumption that such transformation rules are well‐defined and come with precondition and postcondition formalized.…”

Section: Related Workmentioning

confidence: 99%

A delta‐oriented approach to support the safe reuse of black‐box code rewriters

Benni

Mosser

Moha

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

Large-scale corrective and perfective maintenance is often automated thanks to rewriting rules using tools such as Python2to3, Spoon, or Coccinelle. Such tools consider these rules as black-boxes and compose multiple rules by chaining them: giving the output of a given rewriting rule as input to the next one. It is up to the developer to identify the right order (if it exists) among all the different rules to yield the right program. In this paper, we define a formal model compatible with the black-box assumption that reifies the modifications (Δs) made by each rule. Leveraging these Δs, we propose a way to safely compose multiple rules when applied to the same program by (a) ensuring the isolated application of the different rules and (b) identifying unexpected behaviors that were silently ignored before. We assess this approach on two large-scale case studies: (a) identifying conflicts in the Linux source-code automated maintenance and (b) fixing energy antipatterns existing in Android applications available on GitHub.

show abstract

Atl

Cited by 107 publications

References 6 publications

Claimed advantages and disadvantages of (dedicated) model transformation languages: a systematic literature review

Claimed advantages and disadvantages of (dedicated) model transformation languages: a systematic literature review

Traceability and Synchronization Between BPMN and UML Use Case Models

A delta‐oriented approach to support the safe reuse of black‐box code rewriters

Contact Info

Product

Resources

About