- Used to semantically mark AllocationTables and AllocationEntries (e.g., which layers of the system are connected by allocation, and which system entities)
 - Add IAllocationService.addAllocationEntryType() and getAllocationEntryTypes() to register and query IAllocationTypes
 - Apply IAllocationTypes specializations to Task, Partition and Hardware architecture allocations

2) Move TaskToExecutionUnitAllocationTable and TaskWcetTable to af3.task (to avoid circular dependencies that would arise from the introduction of IAllocationType)

3) Schedule model UI
 - Use IAllocationTypes to provide unified generic UI in af3.schedule.ui
 - Remove most of the temporary hacks since allocation[.ui] is now in the build
 - TODO: Remove SystemScheduleDeploymentPropertySection once Deployment has fully been replaced by AllocationTable

refs 2950,3188,3067

- Register af3.timing / Wcet and Period annotations to tasks. Wcet is the assumed WCET of a Task (independent of the ExecutionUnit to which it mapped)
- Add TaskWcetTable that allows to specify the WCET for (Task,ExecutionUnit) pairs.
  - For now, the values can be edited in the annotation view only
  - TODO: Integrated task WCET table as secondary TaskArchitecture editor
refs 2562

TODO:
 - Enable selection of execution type
 - Mapping of ports (see also: #3223)
refs 2562

refs 3220

refs 3192,3177

refs 3190

* Exploration.alg:
  * Register the .alg plugin via an IStattup extension to avoid dependencies on this plugin.
  * Create a objective and a constraint evaluator that can handle DSML expressions.
  * Adjust the opt4j extensions.
  * Temporally introduce the MappingEncoding marker interface to support the DSML evaluators (--> allocation expressions).
  * Fix some minor bugs and warnings.
  * Move the porting utils to the alg plugin (previously in alg.ui).
  * Move the plot code to the alg plugin (previously in alg.ui) until the transition to the AF3 visualization framework is finished.
* Exploration.smt:
  * Create a backend implementation for the smt-based exploration.
  * Minor adjustments (I/O) to comply with the backend mechanism.
* Exploration:
  * Package renaming of the DSE backend mechanism.
  * Make the DSE backend mechanism independent of the eclipse extension mechanism.
  * Integrate the Exploration solution Classes in the EMF model.
  * Minor adjustments of the DSE backend API.
* Exploration.ui:
  * Add a combobox to select the DSE backend for the Deployment synthesis
  * Adjust the GUI backends to comply with the DSE backend interfaces.
refs 2939

Please fix your SVN configurations!

See https://af3-developer.fortiss.org/projects/autofocus3/wiki/Developer_Installation, Section "Initial Workspace Content Check-out", §6.