| Re: [henshin-dev] questions on: trace model, static analysis and the graphical editor |
Hi Matt, I send this mail yesterday already but thanks to a typo this mail did not made it. So let's try it again: 1) I'm not aware of such trace tooling... maybe Enrico or Christian are ?! However, this sounds like an interesting idea. 2) Our approach bases on formal definitions and we actually have several analysis techniques e.g. termination analysis and critical pair analysis. These analysis techniques are already implemented but unfortunately for an older system (http://user.cs.tu-berlin.de/~gragra/agg/). We need to port these analyses to Henshin, which is quite an attempt as Henshin is much more advanced as AGG and among others provides additional control-flow structures. Long story short: It is not implemented yet. Nevertheless, we provide a tooling called "Statespace-Explorer" at which you can, as the name says, explore possible statespaces i.e. possible applications of rules on graphs. Is this explained correctly, Christian? Just play around with it, you'll like it. 3) Fixed, pls use our svn-repository to check out the current sources. greetx, Stefan Am 16.03.2010 16:30, schrieb Matthias Biehl: > Hi, > > First of all, thanks for henshin, it is a great model transformation tool. > > 1.) Does henshin produce a trace model (similar to qvt) or are there > some framework functions that can help me build one? > Background: I have a number of transformation rules that are executed > on an source model. In the target model I would like to point at a > certain model element and find out which transformation rule has > created it. A trace model could help me find out. > > 2.) On the homepage I read that static analysis of the transformation > is one of the selling points of henshin. Are there already library > functions available for static analysis? > > 3.) The graphical editor apparently has a check to allow only edges > between model elements, which have a defined relationship in the ecore > metamodel. However, this check does not take inheritance into > consideration. Example: EClass A has a EReference named b to EClass B, > EClass C inherits from A. According to the inheritance rules, every C > should have a reference to B. However, the graphical editor does not > allow me to draw an edge between C and B. > > Thanks, > Matt > _______________________________________________ > henshin-dev mailing list > henshin-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/henshin-dev >
Attachment:
signature.asc
Description: OpenPGP digital signature