Open TheoLeCalvar opened 1 year ago
About 50 lines of kmehr.km3 were manually modified (to remove feature names that clash with OCL type names, in particular). But this step could be automated within the ecore to KM3 mapping. Currently however it would need to be maintained.
The UML-RSDS from ATL works for regular ATL, but doesn't fully handle the ATL version used in the case.
Much of the inversion process can be automated, but as I explain in the paper, sometimes customised inverse functions need to be created (eg., to extract address items from an address line).
Description
The UML-RSDS solution to the TTC 2023 KMEHR to FIHR case consists in two transformations: a forward one in ttc23.km3 (from KMEHR to FIHR), and an inverse one in fihr2kmehr.km3 (from FIHR to KMEHR). These two files describe mappings and operations in a declarative constraint-like form. There is also a huge (around 8500 lines of code) kmehr.km3 file containing both source and target metamodels. The solution compiles, and seems to work without error, although we have not checked the results.
Positive points
Negative points
Questions to authors
Open questions