Inconsistencies in CORE metamodel

[Matthias Schoettle]

Currently, in the CORE metamodel (and the implementation in TouchCORE), COREContributions are contained in the feature model, even though they are part of the impact model. There is a bidirectional association but the containment is set on both. Only the COREImpactModelElement should contain the contribution.

Furthermore, the two references ImpactModel and FeatureModel in COREConcern need to be changed to lowercase (of first character) to be consistent with the rest of the metamodel.

[Matthias Schoettle]

References #273: Changes all occurrences of "FeatureModel" and "ImpactModel" to start with lowercase to respect the changes in the CORE metamodel.

→ <<cset 8172e2ec7af0>>

[Matthias Schoettle]

In addition, COREContribution to COREFeature and COREImpactModelElement needs to be navigable. I.e., it needs to be possible to from the contribution to get the source and destination (this probably requires a super-class for both for the source link). Also, COREFeature to COREContribution should also be navigable (to be able to go top down).

[Matthias Schoettle]

Resolved with recent CORE metamodel update. Existing code (mostly UI) now just needs to be updated.