Transcript THALES recommendations for QVT

THALES recommendations for the final OMG
standard on Query / Views / Transformations
I T &S
A e r o s p a c e
D e f e n c e
Nicolas Farcet
Benoît Langlois
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
 2nd 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:

2
Propose recommendations for a unified and open QVT standard meeting end user
expectations
THALES Research & Technology
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

THALES recommendations
Recommendation 1: Ensure QVT work product
portability

Tool-independence

Predictable results

on different platforms, the same QVT specification has to
produce the same effects.
 Impact on QVT standard

3
Provide an unambiguous semantics of execution
THALES Research & Technology
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
 User expectations
THALES recommendations
Recommendation 2: Ensure QVT work product
durability

Capitalization of QVT work products
 Impact on QVT standard

4
Provide generics mechanisms to embody know-how
and customization facilities to adapt to various needs
THALES Research & Technology
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
 User expectations
THALES recommendations
Recommendation 3: Ensure QVT work product
composition capability

Divide to conquer (handle transformation complexity)

Promote opportunistic reuse of small methodological
bricks

Promote QVT COTS
 Impact on QVT standard

5
Provide QVT work product composition mechanism,
statically or dynamically at runtime
THALES Research & Technology
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
 User expectations
THALES recommendations
Recommendation 4 and 5: Have an open and unified QVT standard,
and efficiently address multiple concerns

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

6
Adopt a reflective and layered architecture ?
THALES Research & Technology
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
 User expectations
Our approach: reflective and layered architecture
QVT-Common
Language
QVT Mapping
Layered QVT-Language approach
QVT-Specific Language
QVT-Specific Language
QVT-Specific Language
QVT-Specific Language
Transformation
QVT-Common
Language
QVT-Specific
Language
7
THALES Research & Technology
QVT-RepostiroryAPI
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
QVT language pattern
Our approach: The Pivot Technique
QVT Common Language
Infrastructure
Metamodel
Abstract
Syntax
Layer
Model
Concrete
Syntax
Layer
Instance
Execution
Layer
To be standardized
8
Proprietary semantics
(requires proprietary EE)
R4,
R5
Transf.
specification
(abstract)
Transf.
specification
(concrete)
Transf. of
transf. spec.
to bridge
semantics
OS,
libraries…
THALES Research & Technology
R2
Mapping
constrains
Transf.
realization
(abstract)
Interoperability through
common semantics across Transf.
transformation components realization
(abstract)
Transf. of
transf. spec.
to bridge
semantics
R4,
R5
Transf.
specification
(abstract)
R3
+
Proprietary
QVT Specific
Language 2
Advanced
semantics (private)
Mapping
constrains
Transf. of
transf. spec.
to bridge
semantics
Common semantics
(public and shareable)
Public
Interoperability through
common semantics across
transformation components
Public
Private
Private
QVT Execution
R1
Surface
Transf. of
transf. spec.
to bridge
semantics
Transf.
specification
(concrete)
Model
Repository
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
Language
Layer
Execution
QVT Specific
Language 1
Contact information

[email protected]

www.carroll-research.org
 MOTOR project

9
[email protected]
THALES Research & Technology
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
 CARROLL research programme
(THALES, CEA, INRIA)