Implement an evolution-aware prototype

[thiagomael]

To jumpstart an evolution-aware analysis tool, we need to be able to persist/reuse analysis results in the scenario where we explicitly (and deterministically) control the impact of evolution in SPL models.

To address this, we will leverage the evolution scenarios from the IST experiments and refactor ReAna to reuse intermediate results.

[thiagomael]

Before we can close this issue, I suggest that we first handle issues #15 and #18, and then finish testing #16. When all 3 are done, I consider that we will have a working prototype.

[thiagomael]

I have a suggestion for distributing the work:

• It seems to me that @brenoafb worked in both ddsPersistence-Andre and reanaE, right? If so, he should feel comfortable merging both branches and removing the ones that are no longer used (#15).
• @andrelanna bootstrapped the tool, so I think he could help to define the evolution-aware CLI (#20) and then propose how to evolve the implementation (#19) so that the others can collaborate.
• @tobiassena could implement an automation script (#18), as mentioned earlier in the Skype meeting.
• Both @tobiassena and @SrRaposo could walk @andrelanna through the current implementation, to select candidate refactorings.
• After all tasks are done, we will be all tackling #19 to implement the refactorings suggested by @andrelanna (of course, everyone should feel free to propose changes and suggest different ones). Then, we can start to create smaller tickets to cover more focused implementation/research activities.

What do you guys think?

[andrelanna]

Hi Guys! I agree with Thiago's suggestion. I will take on the evolution-aware CLI ( #20 ) now and then I will work on a proposal for implementing future evolutions.