Re: [viatra-dev] VIATRA Integrated Demonstrator

[Ujhelyi Zoltán <ujhelyiz@xxxxxxxxxx>]

Hi,

just a minor nitpicking: the CPS example is not entirely an IncQuery demonstrator, as (1) it focuses on model transformation, not model queries, and (2) the transformation is implemented both in IncQuery EVM and VIATRA.

About the example itself, to me it really seems to focus on quick fix generation, so this name is ok by me.

However, the CEP aspect is entirely unclear to me - after reading the description two or three times, I do not see how CEP helps this case study... Maybe I am missing something trivial, so please enlighten me.

---

About the location of the case studies: obviously, eclipse.org would be the best place if possible :) , as that is as neutral as possible. Of course, this would require putting the CPS example there as well... On the other hand, I don't really like the idea of a VIATRA organization on Github - that project already belongs to eclipse.org. Maybe this example would have a place on the eclipselabs Github organization (see https://github.com/eclipselabs/eclipselabs). But this is only my opinion, I am open to any solution.

Cheers,
Zoli
-- Zoltán Ujhelyi
https://www.inf.mit.bme.hu/en/members/ujhelyiz

Fault Tolerant Systems Research Group
Budapest University of Technology and Economics

On 2015.05.03., at 14:38, David, Istvan wrote:

> Hi guys,
> 
> I've been working on a case study on integrating all the three modules of
> the VIATRA stack into one typical MDE workflow:
> 
>   - https://github.com/david-istvan/viatra-cep-examples/tree/master/sosym,
>   -
>   https://github.com/david-istvan/viatra-cep-examples/wiki/CEP-driven-DSE-aided-Model-Synchronization
>   .
> 
> It was originally created as a case study for an upcoming paper to showcase
> the essence of such an integrated approach, thus the implementation is
> really "prototype-like" as compared e.g. to the IncQuery CPS Demonstrator.
> 
> I was wondering whether we should create a de facto VIATRA Integrated
> Demonstrator (similarly to the CPS example now being *the* IncQuery
> demonstrator) and further elaborate on the current case study, provide a
> more detailed implementation and make it the part of  the demonstrator.
> (Later on, we could extend the demonstrator with other case studies, as
> suggested by the following layout:
> https://github.com/david-istvan/viatra-cep-examples/wiki/VIATRA-Integrated-Demonstrator
> .)
> 
> This topic is, of course, strongly related to this thread:
> https://basecamp.com/2559808/projects/5376340/todos/170682756.
> 
> *As a short-term task*: I want to rename the plugins of the case study
> (currently: "org.eclipse.viatra.cep.examples.sosym.*") and refer to them in
> the paper appropriately. *Question*: do you agree that this case study
> should be a part of an integrated demonstrator? If so, do you agree on
> referring to it as the "Quick Fix Generation" case study? Other suggestions
> are very welcome!
> *Related question*: If we agree on having an integrated demonstrator with
> various case studies, what would be the appropriate location for it? I
> assume GitHub, but not sure whether it should be (a)
> https://github.com/FTSRG, or (b) we should create a
> https://github.com/VIATRA group.
> 
> Although every hint from you is greatly appreciated, feel free not to
> answer immediately, as I plan to bring these questions to the next meeting
> on Tuesday.
> 
> Cheers,
> Istvan
> _______________________________________________
> viatra-dev mailing list
> viatra-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/viatra-dev