Co-Evolution Basic Concepts [message #1776208] |
Mon, 13 November 2017 14:36  |
Eclipse User |
|
|
|
Dear All,
We are trying to develop an interactive bridge between an internal EMF model and Capella using Co-evolution.
Our starting point is the useful Capella2APA example provided with the source code.
However, it is not entirely clear to us what the starting point for developing bridges using co-evolution is. There are prevalent concepts such as queries, rules, matching policies, etc. We thus would like to kindly ask for a pointer to where relevant information regarding the use of Co-evolution could be found.
One main goal of our search is to resolve the following issue:
The provided APA<->Capella bridge does not synchronize a physical structure recursively. Only nodes directly owned by the main Physical System are synchronized. Nodes containing other nodes, contained in other nodes, etc, are not.
The bridge we intend to develop does require that recursive structure synchronization. That way we figured out that our knowledge is at this stage quite limited regarding the underlying concepts of Co-evolution and what the intended programmatic use of queries, rules, etc, is. Hence our call for help in this forum.
Thanks in advance, and best regards.
|
|
|
|
Re: Co-Evolution Basic Concepts [message #1776519 is a reply to message #1776473] |
Fri, 17 November 2017 03:59  |
Eclipse User |
|
|
|
A small addition to my post.
Similarly to the idea that Co-Evolution should allow you to use the transformation technology you want, the idea behind mapping queries is that you can use the query technology you want to implement them (as long as it can be called from Java). Depending on the technological constraints you have, you may consider to stick to Java (that is usually what we do) or use higher-level technologies. We did experiments with Viatra Queries, but OCL and Xtend should also be pretty simple to integrate, to name a few. OCL and Viatra Queries have high-level support for recursive navigation (built-in for VQ, using the closure operator in OCL).
|
|
|
Powered by
FUDForum. Page generated in 0.03381 seconds