1. I T & S A e r o s p a c eD e f e n c e THALES Research & Technology THALES recommendations for the final OMG standard on Query / Views / Transformations Nicolas Farcet Benoît Langlois

2. This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES 2003. Template trtco V 6.0.0 2 27, October 2003 THALES Research & Technology OMG QVT Standard – Current status Objective of the QVT standard Define a language to express queries, views and transformations on models Maturity for the final standard Initial submission (2003-03) : 8 submissions Revised submission (2003-08): 5 submissions + Kennedy Carter in list 2 nd revised submission (2004-01) … Major obstructions: Consortiums with different or opposite paradigms for model transformation Current QVT requirements are not user driven, but more technically oriented e.g. no requirement guarantees QVT code portability (e.g. for rule engines) Objective of the paper: Propose recommendations for a unified and open QVT standard meeting end user expectations

3. This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES 2003. Template trtco V 6.0.0 3 27, October 2003 THALES Research & Technology THALES recommendations Recommendation 1: Ensure QVT work product portability User expectations Tool-independence Predictable results on different platforms, the same QVT specification has to produce the same effects. Impact on QVT standard Provide an unambiguous semantics of execution

4. This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES 2003. Template trtco V 6.0.0 4 27, October 2003 THALES Research & Technology THALES recommendations Recommendation 2: Ensure QVT work product durability User expectations Capitalization of QVT work products Impact on QVT standard Provide generics mechanisms to embody know-how and customization facilities to adapt to various needs

5. This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES 2003. Template trtco V 6.0.0 5 27, October 2003 THALES Research & Technology THALES recommendations Recommendation 3: Ensure QVT work product composition capability User expectations Divide to conquer (handle transformation complexity) Promote opportunistic reuse of small methodological bricks Promote QVT COTS Impact on QVT standard Provide QVT work product composition mechanism, statically or dynamically at runtime

6. This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES 2003. Template trtco V 6.0.0 6 27, October 2003 THALES Research & Technology THALES recommendations Recommendation 4 and 5: Have an open and unified QVT standard, and efficiently address multiple concerns User expectations Ability to support multiple languages (graphical, non graphical, declarative, imperative…), coping with: Multiple development communities DSL for business experts, graphical declarative for architects, textual imperative for developers… From inside or outside of the company Developers skills (past experience and personal affinity of developers…) Tasks concerns (functional or non functional aspects…) However a unified standard Not a closed multitude of language standards An consistent extensible open framework for interoperable QVT languages Impact on QVT standard Adopt a reflective and layered architecture ?

7. This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES 2003. Template trtco V 6.0.0 7 27, October 2003 THALES Research & Technology Our approach: reflective and layered architecture QVT-Common Language QVT-Specific Language QVT Mapping Transformation QVT language pattern QVT-RepostiroryAPI QVT-Common Language QVT-Specific Language Layered QVT-Language approach

8. This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES 2003. Template trtco V 6.0.0 8 27, October 2003 THALES Research & Technology Our approach: The Pivot Technique Metamodel Model Instance Model Repository Transf. of transf. spec. to bridge semantics Transf. of transf. spec. to bridge semantics Transf. specification (abstract) Transf. specification (abstract) Transf. of transf. spec. to bridge semantics Transf. of transf. spec. to bridge semantics Transf. specification (concrete) Transf. specification (concrete) Advanced semantics (private) Common semantics (public and shareable) QVT Common Language Infrastructure QVT Specific Language 2 Mapping constrains Public Private Public Private Prop- rietary + Transf. realization (abstract) Transf. realization (abstract) Interoperability through common semantics across transformation components Interoperability through common semantics across transformation components QVT Specific Language 1 Proprietary semantics (requires proprietary EE) Mapping constrains Execution Language Layer Abstract Syntax Layer Concrete Syntax Layer Execution Layer QVT Execution Surface To be standardized OS, libraries… R1 R3 R4, R5 R2

9. This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES 2003. Template trtco V 6.0.0 9 27, October 2003 THALES Research & Technology Contact information CARROLL research programme (THALES, CEA, INRIA) nicolas.farcet@thalesgroup.com www.carroll-research.org MOTOR project benoit.langlois@thalesgroup.com