Ian O'Connor 	Lyon Institute of Nanotechnology, École Centrale de Lyon, Lyon, France.

 Area: Heterogeneous systems (analog/digital, optics/electronics/3D/...)

 Problem: extracting information about interaction between objects
  need to abstract functionality 
  need to predict impact of choices
 Solution: (optimal) design methods. Functionality + non-functional.

 Would like: framework/tools for dealing with abstraction
 
Gabriela Nicolescu 	École Polytechnique, Montréal, Canada.

 Area: Heterogeneous systems (hardware/software)
       focused on (multi-formalism) modelling and (co-)simulation
       try to assure/analyze correctness
       abstraction/refinement within design flow

 Would like: abstraction/refinement with focus on heterogeneous
 
Eugene Syriani 	Modelling, Simulation and Design Lab, School of Computer Science, McGill University, Canada.

 Area: Transformation Language Engineering
       Apply MPM principles

 Would like: more precise definitions of MPM
             transformation ++

Antonio Cicchetti 	Malardalen Research and Technology Centre (MRTC), Vasteras, Sweden.

 Area: evolution of models, representation of versions, co-evolution of meta-models

 Would like: (co-)evolution

Manuel Wimmer 	Institute for Software Technology and Interactive Systems, Vienna University of Technology, Austria. 

 Area: systematic (and easy) development of model transformations
        by-example approaches 
        model versioning (in the context of concurrent modelling - keep consistency) 
          not only syntax, but also semantics

 Would like: systematic (and easy) development of model transformations
             compare approaches (with others)
             (co-)evolution

Marouane Kessentini 	DIRO, Université de Montréal, Montréal, Canada.

 Area: automatic model transformation using examples
       model refactoring   (what is a "well designed" model?)
       trace-ablity to identify origin of faults

 Would like: comparing different approaches for model transformation
             (in particular, by-example)

Mark Asztalos 	Department of Automation and Applied Informatics, Budapest University of Technology and Economics, Hungary.

 Area: VMTS tool
       model transformation language (graph-rewriting based) 
        formal methods for verification of transformation (forall input models)
        uses mapping onto declarative description
       design patterns for model transformation, for re-use, can be pre-analyzed

 Would like: offline verification of model transformation
             model transformation language engineering
             (co-)evolution (in particular, transformation)

Bart Meyers 	Modelling, Simulation and Design Lab, Department of Mathematics and Computer Science, University of Antwerp, Belgium.

 Area: evolution of modelling languages (and transformations)
       dealing with semantics in above context

 Would like: discuss about semantics and how to represent it
             (co-)evolution

Pieter Mosterman (organizer) 	Design Automation Department, The MathWorks, USA.
 
 Area: design automation (DEA, M&S, ...)
       computational (correct, efficient, ...) modelling and simulation

 Would like: multi-abstraction, ~ design refinement
             ~ different paradigms used in practice in design approaches
             (co-)evolution

Jonathan Sprinkle 	Electrical and Computer Engineering, The University of Arizona, USA.

 Area: Cyber Physical Systems (computation + communication + control)
        current methods don't scale 
       language evolution
       obfuscation of algorithms, guarantee properties
       language engineering: quality metrics for meta-models
       domain-specific modelling languages for human-in-the-loop applications

 Would like:
       (co-)evolution 
       abstraction ~ co-design 

Bruno Barroca 	Departamento de Informatica, Universidade Nova de Lisboa, Portugal.

 Area: language engineering, rapid prototyping
       use existing components in MDE, PIM vs. PSM (in both directions)

 Would like: reverse engineering
             case studies of abstraction/refinement/factorization, as basis for formalization

Ghizlane El Boussaidi  	École de Technologie Supérieure, Montréal, Canada.

 Area: tools and techniques to help designers to transition from analysis to design
       software patterns (good/bad), find instances, then apply transformations
       constraint satisfaction to implement pattern matching

 Would like: meta-modelling languages (UML+OCL not enough)
             quality of models and transformations (guarantee preservation of properties)

Levi Lucio 	Departamento de Informatica, Universidade Nova de Lisboa, Portugal.

 Area: test generation from formal models (test specification language)
       what is the purpose of formalization?
        as reference? to prove properties? ... 
       transformation language (formalized, proved properties -- confluence and termination
                                            by construction)
       checker for model transformations (for a specific transformation, forall input models)

 Would like: abstraction, formalization, what is the optimal level?
             what is the purpose of formalization?
             express resilience
             formalization of MDD

Felipe Frantz Ferreira 	Lyon Institute of Nanotechnology, École Centrale de Lyon, Lyon, France.

 Area: heterogeneous designs: different simulation languages, different design flows
       unified high-level specifications which can be transformed to lower-level realizations
        how to distribute design constraints, use experience to guide transformation
       re-use low-level "building blocks" !!

 Would like: refimenent of models (framework for)

Hans Vangheluwe (organizer) 	Modelling, Simulation and Design Lab, School of Computer Science, McGill University, Canada.

 Area: CAMPaM

 Would like: foundations for DSM (re-use of building blocks), (co-)evolution, abstraction



Notes: Pieter: evolution ~ refinement
       refinement: only on models, or also impact on language?