Eugene Syriani: 

Topics you work on: 
	model transformations, DSM IDE, Simulation, etc.
Interested: 
	* Semantic consistency in multi-view modelling; how to ensure consistency? 
	* Link between product families and modelling languages? How to take advantage of both? 
          Claferlike? Language engineering (how do I design languages with PLM in mind?)
	* Parallelism in Model transformation
	* HCI user experience in DSM IDEs

Istvan David:

Topics you work on:
	* consistency management (collaborative modelling), semantic overlaps, linking in the 
Work on:
	* link semantic to linguistic domain
	* inconsistency tolerance

Marco di Natale:

Topics you work on:
	*  timing analysis and schedulability analysis; use in OS; did not match modelling language; 
           Bran Selic: profile for schedulability; triggered interest in Models; 

Work on:
	* architectural level model in large scale CPS (MARTE, SysML, ?)	
        * Pure functional model together with all other? is it possible (for example, AUTOSAR), What are different models needed? 
	* Simulink behaviour what is platform model? What is missing? What is the mapping model?
	* How to represent this mapping? How to validate consistency?
	* Synthesising the mapping: DSE!
	* What should the industry use? Papyrus? Is this needed because lot of frustration
	* SysML? Lots of problems
	* Teaching CPS modelling in academia?

Intermezzo: 
	* innovators dilemma (Clayton Christensen (three S-es research, industry, teaching)), 
          Gartner group model: Peak of expectation, etc.;
	* Standardization <> DSM 
	* MPM: Mult-Formalism, Multi-Abstraction, Processes.

Clark Verbrugge:

Topics you work on:
	*  Compiler optimisation
		* Automatic parallelisation, nice progress using a new technique: 
                  When to launch threads? Feedback model in the back. 
	* Computer Games
		* Formalising computer games (modern, FPS), big messy software, correctness, stealth game analysing: 
                  sneak from A to B -> geometry , how to visualise, search technique (heuristics from robotics), 
                  features like combat models, distractions: adds complexity; Hierarchical search 

Joachim Denil:

Topics you work on:
	* Embedded engineering focus
	*  consistency: weave into process and optimise with Istvan
	* Co-design with Ken (see Ken)
	* Co-simulation
	* Environment modelling
	

Yentl Van Tendeloo:

Topics you work on:
	*  ModelVerse: metamodelling tool and model repository
		* explicit modelled tool
		* conformance relations (different levels)
		* introspection (modify tool while running)
		* performance aspects (add hints, integrate this into the model verse, leaky abstraction)


Ken Vanherpen:

Topics you work on:
	*  co-design between different engineering domains
	* linguistic properties to ontological properties

Work on:
	* what is the most appropriate language to model these relations between properties
	* refinement of contracts

Stephan Klikovits:

Topics you work on:
	*  Testing background (unit testing, etc.)
	* CERN particle 
	* automatically generate unit test for procedural language 
	* Step back, how do I deal in general with CPS: Modelling for testing in CPS 
Work on:
	* Domain specific test case description is needed? Across a domain might be able to use similar concepts. 
	* Describe a component in a different way. Implicit -> testing only the software

Antonio Cicchetti:

Topics you work on:
	*  Model evolution
	* usability of tools in industry
	* Separation between linguistic and ontology	
Work on:
	* More adaptability in the Language
	* Building multi-view with semantics

Intermezzo:
	using the most appropriate? But engineers know only for example Simulink. 
		* Changing paradigms introduces a lot of overhead. Very iterative approach, even with parallel 
		* They sometimes cannot change tools: tool provider does not develop anymore what company wants; open source with customisation

Antonio Vallecillo:

Topics you work on:
	*  Here for optimism!  The winter is over
	* open framework: 5 views, with consistency with MAUDE, notation independent, 
          industry will not change notation, having universal semantics is not possible
	* Why is industry not using things we use: We do things right, industry wants to make money 
	* let us be flexible
	* uncertainty and tolerance: data uncertainty; UML tolerance: with intervals; 
	* why not use eclipse: not mature enough. They fall apart whit large models, use knowledge from databases. 
          How can we go to companies if we cannot even handle 5m elements. They have 10x more elements 
	* CPS monitorting train: how to model to allow evolution, modelling tools are too complex, cannot change notation, 
          more flexible notation. Provide language together with the model of the semantics. 
	* What makes a company to relive: flexibility and education

Dimitri Racordon:

Topics you work on:
	*  chemists, DSL for toxicity of work environments
Work on:
	* DSL for non-computer scientists 
	* Verification tools in other domains
	* distribution of processes (computing power, etc.

Hans Vangheluwe:

Topics you work on:
	*  world domination through/for/by MPM

Work on:
	* Testing the physical part assumes that you find: experimental frame 
	* If we modulary describe the concepts of tolerance, state automata, diff. equations, etc. 
          As language engineers, should we not reason about modular composition. 
	* Marco: at the industry: why am I not getting the tolerance, clash of communities, do I need a general theory; 
          Timed semantics will kill you; a generic scientific could help you at certain sweet spots. 
	* all topics

	* the essence of abstraction and approximation

Dominique Blouin:

Topics you work on:

Work on:

Pieter Mosterman:

Topics you work on:

Work on: