GitLab

Signed-off-by: Alexander Diewald <diewald@fortiss.org>

- Keep original ratings

- Delete unused class HistoryStaticImpl that also suffered from this problem

refs 3353

Remove outdated methods that are not used any more. Their referencing methods from deprecated EClasses have been modified to return empty lists.
refs 3201

refs 3201

refs 3201

refs 3201

* Fix TODOs in the migrators.
* Use Queues in the DSEMigrationProvider.
* Remove DSEUtils utility class since the defined strings are not used anywhere.
refs 3201

* Nevertheless, createHop is still used. Moving this method is not reasonable at this point in time and would lead to a confusing structure of the utility classes. The Hop element should be removed anyways.
refs 3283

* Addresses a TODO from the last code review.
* Mark Class as YELLOW.
refs 3201

refs 3354

refs 3201

When using a non-z3 backend (here: the unofficial MOEA backend) that makes a more extensive use of the ExplorationSolution, invalid models can be produced. The reason for this behavior are faulty containment relations since the produced model fragments of the DSE were not contained in any other EObject. Here, it shall be noted that the SuperSets themselves are not intended as containers as of now since they are also used to pass around references to the relevant elements of a DSE.

Furthermore, one warning was produced due to an EAttribute not being set (noticeable on the console).

Technical details:

* getCastedType(...): Used to avoid ugly casting in client code. The DSE language is based on generic IModelElements, whereas the Sets/SuperSets are strict w.r.t. to the types to provide guarantess for the DSE I/O.
* The ExplorationSpecification now contains the the map of input parameters passed to the DSE (Tracing), but not its elements (!).
* ExplorationSolution: 
* * Contains the returned SuperSetMap.
* * Added a "pool" for SuperSets: They are accessible via the SuperSetMap.
* * Added a element "pool" for the generated elements referenced by the returned SuperSets.
* DSMLModelElementFactory: Creating Sets now requires a reference to the SuperSet (reduced code redundancy; can be used for robustness checking later).
* Adapt to the meta-model changes when using SuperSets/Sets (esp in the smt plugin).
refs 3353

refs 2920

- Adjust the Visualization to ExplorationSolution Mapper.
- Adjust the UI code to operate on entries of the above map.
- Fix some wrong types in the allocation transformation.
- Adjust the deployment generation code for the new allocations returned by the DSE.
refs 3255

* Change the MM accordingly.
* Introduce static helper methods to implement the getters/setters of the affected maps: Runtime exceptions are thrown on mismatching types.
* Add a migrator to set the DSESuperSet types of old models.
* Adjust the factory methods.
refs 3289

refs 3241

refs 3273

=================
| Exploration

exploration.ecore
=================
- ExplorationSpecification
  - targets: non-contained (Migrator!)
  - Add superSet reference to pass required SuperSets to the DSE backend.
- Remove ExplorationSolution interface: No Migration needed.
- Rename ExplorationSolutionSet --> ExplorationSolution
  - Deprecated inputModelAdapter: No migration needed, only used in MOEA.
  - Renaming: targetSpecification --> explorationSpec
    - targetSpecification marked @deprecated
    - No mirgator needed: Class was not used in previous stable releases.
- Add EClass SuperSetMap: Relates types of elements to SuperSets
  - solution: EJavaClassToSuperSetMap (containment!)
- Add EClass EJavaClassToSuperSetMap: internal map of "SuperSetMap"
  - key: Class
  - Value: SuperSet (NO containment!)
- ExplorationSolution
  - Renamed solutionModelMap -> solutionSets
    (Type EJavaClassToEJavaObjectMap -> EJavaClassToSuperSetMap)
  - Adjust EOperations to modifications in backend map.
- SingleExplorationSolution
  - Add the solution state for single solutions.
  - Adjust EOperations to modifications in backend map.
- Removed EJavaClassToEJavaObjectMap

dseproject.ecore
================
- DSE:
  - Add EReference target: ExplorationTarget (containment)
  - Remove explorationSpecification (Migrator!)
- Add an ExplorationTargetPool that contains all ExplorationTargets of a DSE
  project.
- DSERun:
  - Add EReference explorationSolution (containment)
  - Remove EReference visualization (Migrator!)
  
dsl_v2.ecore
============
- Overwrite the accept method for the Sum expression: Do not return null if the
  associated set is empty, evaluate to Zero, instead.

New Migrators
=============
- DSEExplorationTargetContainmentMigrator
  Migrates the set of explorationTargets to the DSE project
- VisualizationToExpSolutionMigrator:
  Migrates the Visualization data to the ExplorationSolution representation that
  allows a better traceability.
  
Other Business
==============
- Adjust plugin.xml to account for recently removed Objective- and
  ConstraintExpression classes. Now, ExplorationObjective and
  ExplorationConstraint is used.
  
=================
| Exploration.alg

- Adjust the Opt4JBackend to be comply to the new DSE Backend Specification
- The output type detection in the base decoder is more robust.
- The ITaskAdapter temporally references its corresponding component to ease
  the refactoring of the DSE backend interface. This shall not be needed when
  the transformation framework is integrated again.
- Temporally transform the internal solutions to a superset of
  ComponentToExecutionUnitAllocations to create s solution model. Workaround
  until the transformation framework is integrated again.
- Misc adjustment for backend changes.

=================
| Exploration.smt

- Adjust the Z3Backend to be comply to the new DSE Backend Specification
- Base the results of the DeploymentRun2 and SolverRun2 on the
  ExplorationSolution (see above).

================
| Exploration.ui

- Adjust the GUI logic to account for the changed containment relations.
- Update the DSE project import wizard for the Meta-Model changes.
- Move the ExplorationSolutionVisualizationUtils class to the UI plugin (here).
  It is used to transform ExplorationSolutions to a Visualization representation
  (i.e., DataSetCollection).
- Use doubles instead of ints in the SpiderChartUtils. Although not a proper
  solution, this covers more cases... Instead the generic should be reflected.
refs 3273

to createDseSuperSets(TaskArchitecture architecture, DSEPlatformArtifact platformArtifact, AllocationTableCollection allocCol) 
in DSEProjectModelElementFactory

changed transform(Component topLevelComponent) to transform(Component topLevelComponent, AllocationTableCollection atc) in ComponentArchitectureTransformationBase

* No migration needed due to the eClasses' abstract/interface nature.
* Removed ObectiveExpression
* Removed ConstraintExpression
* Removed ExplorationTargetExpression
* Removed GenericObjective
* Removed GenericConstraint
refs 3273

refs 3241

refs 3240

* The DSEInputParameter container is no longer used --> Remove.
* Remove several porting classes of the MOEA-based DSE.
refs 3200

Use raw types instead. This bug could be caused by using a newer JDK.

* Modify (Super)Sets to use a generic that denotes the types of elements within a set. Thereby, it is ensured that only elements of this kind are contained/referenced in a specific set.
* Introduce a SuperSetMap that allows to associate the types of elements of supersets with superset instances.
* Use the SuperSetMap as the main entity to pass model elements from the DSE Project to backends.
* Add the ComponentToTaskAllocationTable to the DSESuperSet and the DSE model element: This is the new way to identify which Tasks belong to which Component.
refs 2939

 - Base: af3.component[.ui]
   - IComponentArchitectureTransformation
   - ComponentArchitectureTransformationBase
   - ComponentArchitectureTransformationMenuBase
 - Specializations: af3.task[.ui]
   - ComponentToTaskArchitectureTransformation
   - TransformComponentToTaskArchitectureMenu
refs 3067

* The current filterByType methods has fairly strict expectations
  towards inheritance which restricts the use of the method.
* Add a more generic filterType method that has less restrictions
  w.r.t. the generics.
* Rename the existing method to filterTypeSafe.
refs 3203

Eliminate support for multi-instance annotations, which was mostly unused and only complicated the code.
refs 2964