2. Model Representation Transformation

Another part of the research investigates transforming a model representation based on the specification of its initial and target formalism [22]. This allows one to:

• Generate a functional model from software or even execution trace (e.g., a solver procedure can be synthesized from the concepts that are part of the domain specific ontology, i.e., function calls, and their respective execution ordering);
• Automate generation of different views on a system (e.g., scenario diagrams from a functional model) or even an implementation model when translating to a domain specific formalism;
• Automate design by generating specifications from requirements, ultimately leading to automated code synthesis (or at least stub generation), which, in turn, can be integrated in an automated optimization and run-time architecture reconfiguration scheme for hardware and software, or software only (e.g., for System-on-Chip applications [52]);
• Automatically derive a reconfiguration model for guiding run-time system changes from functional and architectural models [3];
• Use best-of-class methods and tools by generating the required data and model representation format to prevent inconsistencies at the boundaries between engineering teams, engineering software, and multiple modeling paradigms, and to enable the sharing and coordinating of information flow with minimal overhead [17].