Alloy Transformation: No synchronization

[GoogleCodeExporter]

When a model is built directly on OLED and then translated to Alloy, when 
classes’ names are modified in the model the following Alloy transformations 
do not consider the changes.

E.g. Class X is translated to X in Alloy, if a user modifies its name to A1, 
the following Alloy transformation still considers it as X.

Original issue reported on code.google.com by pedropau...@gmail.com on 9 Aug 2013 at 2:05

[GoogleCodeExporter]

Hi Pedro Paulo,

There's no problem with our approach since the classes still have unique names 
in Alloy. The issue is that the generated unique name do not reflect exactly 
the source name. This could in turn become a traceability issue if one wanted 
to know the source class of that Alloy field declaration.

So far, we do not intend to modify this. But if your suggestion turns out to be 
a better approach(which seems to be the case) we will change it as soon as we 
get some time left to work on it. In that case, we will report the modification 
here for you.

Thanks a lot,
John

Original comment by johnguer...@gmail.com on 3 Nov 2013 at 7:54

• Changed state: Accepted

[GoogleCodeExporter]

Hi Pedro Paulo,

I just did this modification in the code. Now, there is sinchronization between 
the name of a model element and its Alloy counterpart. 

This will be available in the next version of OLED, perhaps 0.8.29, as soon as 
we test this a little bit more.

Thanks a lot,
John

Original comment by johnguer...@gmail.com on 9 Dec 2013 at 12:15

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by johnguer...@gmail.com on 9 Dec 2013 at 12:28

• Changed state: Verified