Replies: 1 comment
-
|
I can't really speak to what's provided by OCL and ATL. You can specify named constraints directly in the Ecore model, e.g., here for Ecore.ecore itself: and then implement them in the generated validator, e.g., |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
I've been experimenting a little with Eclipse Ecore + ATL and wonder if they support satisfiability checking?
From what I have seen, normally an approach would like the following. In Ecore specify a
Productand anArticleboth with aprice. Then (I believe) specify a constraint in OCL likeprice > 0for bothProductandArticle. Furthermore, in ATL I can write a transformation that instantiates anArticlefrom aProductthat copies theprice. If the transformation is erroneous (e.g., it always sets thepriceto zero), that can be detected by validation ofArticle.Now I want to "lift" my meta model; in Ecore I want to specify an
Entitywhich can be instantiated as aProductandArticleincluding their constraintprice > 0. Is there any way I can prove my model transformation fromProducttoArticlepreserves the truth of this constraint (assuming it was true forProduct)? I know I can use tools like Z3 to accomplish this, but I wonder if this capability is included in Eclipse EMF itself?Beta Was this translation helpful? Give feedback.
All reactions