New features of Phoenix 2.15
Platform update
Build on Eclipse 2018-12
Requires Java 11
Retire deployment model in favor of allocation table
Allocation tables enable to model deployments of logical architectures to multiple layers of the technical architecture (e.g., tasks, partitions, hardware platform).
A direct replacement for the previous deployments is the "component-to-execution unit" allocation
All modules depending on deployments (DSE, code generators, ...) have been ported to the new metamodel
Old deployment models are migrated automatically (WCET specifications are now found in "Timing" tab of the task architecture)
Introduce timing specification model
Aligned with TADL language defined in the TIMMO2USE project that served as input for industrial standards such as AUTOSAR TIMEX and APP4MC/AMALTHEA
Used to define reaction/synchronization constraints between tasks and/or messages that are considered by DSE
Design-Space Exploration (DSE)
Overhaul of DSE project model, process support, and UI
Supported operations: import input model, define constraints/objectives, perform exploration, pick/export solution
Use snapshots to freeze input model before performing exploration steps
Old DSE projects will not be migrated to the new DSE project model due to the massive structural changes. They are automatically removed, and a new DSE project has to be created manually (using the import wizard)
Improved deployment and schedule synthesis (joint exploration of deployments and schedules, minimization of latencies, task hardware decoupling constraint)