Eclipse Community Forums: QVT-OML » Best practice to check OCL invariants from inside QVTo script

Help

Home

Home » Modeling » QVT-OML » Best practice to check OCL invariants from inside QVTo script

Show: Today's Messages :: Show Polls :: Message Navigator

Best practice to check OCL invariants from inside QVTo script [message #899794]

Thu, 02 August 2012 07:34

Christopher Gerking is currently offline

Christopher Gerking
Messages: 33
Registered: April 2011

Member

Several OCL invariants are specified as part of my meta-model. During generation of an instance of this meta-model, I have to check conformance with all specified invariants from inside the QVTo script. The check must happen during the transformation, since further results depend on it.

I see different possibilities to achieve this:

1. Move all invariants to operations/attributes. Call the operation or attribute inside the invariant and also from my QVTo script.

2. Create a blackbox library and introduce an evaluation operation, which uses existing validation code.

3. Make invariants 'callable'. Is there an example available? Inserting the keyword to my ecore file recently crashed it...

Using the blackbox library brings the advantage of not invoking all the invariants individually. Is this the solution to go for?

Report message to a moderator

Re: Best practice to check OCL invariants from inside QVTo script [message #899815 is a reply to message #899794]

Thu, 02 August 2012 08:39

Ed Willink
Messages: 3185
Registered: July 2009

Senior Member

Hi

I would do both.

Use the blackbox for development for which Java debugging will be helpful.

Raise a Bugzilla on your bad callable example please.

Regards

Ed Willink

On 02/08/2012 12:34, Christopher G. wrote:
> Several OCL invariants are specified as part of my meta-model. During
> generation of an instance of this meta-model, I have to check
> conformance with all specified invariants from inside the QVTo script.
> The check must happen during the transformation, since further results
> depend on it.
>
> I see different possibilities to achieve this:
>
> 1. Move all invariants to operations/attributes. Call the operation or
> attribute inside the invariant and also from my QVTo script.
>
> 2. Create a blackbox library and introduce an evaluation operation,
> which uses existing validation code.
> 3. Make invariants 'callable'. Is there an example available?
> Inserting the keyword to my ecore file recently crashed it...
>
>
> Using the blackbox library brings the advantage of not invoking all
> the invariants individually. Is this the solution to go for?

Report message to a moderator

Previous Topic:	Code style / Performance / Best practice question
Next Topic:	Modifying QVT Traceability.

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat May 25 07:22:25 EDT 2013