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.

Slides:



Advertisements
Similar presentations
Profiles Construction Eclipse ECESIS Project Construction of Complex UML Profiles UPM ETSI Telecomunicación Ciudad Universitaria s/n Madrid 28040,
Advertisements

© Chinese University, CSE Dept. Software Engineering / Software Engineering Topic 1: Software Engineering: A Preview Your Name: ____________________.
Professor John Hosking, Dean of Engineering and Computer Science Models, Modelling, MBSE.
By Xiangzhe Li Thanh Nguyen.  Components and connectors are composed in a specific way in a given system’s architecture to accomplish that system’s objective.
Presented by: Thabet Kacem Spring Outline Contributions Introduction Proposed Approach Related Work Reconception of ADLs XTEAM Tool Chain Discussion.
Formal Techniques in Software Engineering Universiteit AntwerpenIntroduction 1.1 Formal Techniques in Software Engineering 3de BAC Informatica Chapter.
Amit, Keyur, Sabhay and Saleh Model Driven Architecture in the Enterprise.
Design Patterns CS is not simply about programming
Ontologies Reasoning Components Agents Simulations An Overview of Model-Driven Engineering and Architecture Jacques Robin.
CASE Tools CIS 376 Bruce R. Maxim UM-Dearborn. Prerequisites to Software Tool Use Collection of useful tools that help in every step of building a product.
CS 290C: Formal Models for Web Software Lecture 6: Model Driven Development for Web Software with WebML Instructor: Tevfik Bultan.
Itntroduction to UML, page 1 Introduction to UML.
Reuse Activities Selecting Design Patterns and Components
Community Manager A Dynamic Collaboration Solution on Heterogeneous Environment Hyeonsook Kim  2006 CUS. All rights reserved.
Software Product Line Architectures (SPLA) Nipun Shah
Comparing M2T & M2M Complementary Approaches © 2008 INRIA, University of York & SINTEF Comparing M2T & M2M Complementary Approaches Hugo Bruneliere,
Spectra Software Defined Radio Products Applying Model Driven Design, Generative Programming, and Agile Software Techniques to the SDR Domain OOPSLA '05.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
Software Engineering Muhammad Fahad Khan
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
Workshop on Integrated Application of Formal Languages, Geneva J.Fischer Mappings, Use of MOF for Language Families Joachim Fischer Workshop on.
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Second RMSIG Workshop Methodology and Process Wolfram Höpken.
MDA and QVT  Tom Gullion, Director of Product Management, Together Products.
MDE Model Driven Engineering Xavier Blanc Université Pierre et Marie Curie
Model transformation with a dedicated imperative language IRISA Rennes (France) - Triskell team Jean-Marc Jézéquel Didier Vojtisek Jean-Philippe Thibault.
Introduction to MDA (Model Driven Architecture) CYT.
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
Alignment of ATL and QVT © 2006 ATLAS Nantes Alignment of ATL and QVT Ivan Kurtev ATLAS group, INRIA & University of Nantes, France
Building Tools by Model Transformations in Eclipse Oskars Vilitis, Audris Kalnins, Edgars Celms, Elina Kalnina, Agris Sostaks, Janis Barzdins Institute.
2nd TTCN-3 User Conference, June The TTCN-3 Metamodel – A Basis for Tool Integration Ina Schieferdecker TU Berlin/Fraunhofer Fokus Hajo Eichler,
© Mahindra Satyam 2009 Decision Analysis and Resolution QMS Training.
ISO/IEC CD and WD : Core Model and Model Mapping ISO/IEC JTC1/SC32/WG September 2005, Toronto SC32/WG2 Japan (Kanrikogaku Ltd) Masaharu.
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
On the Role of Abstract Platform in Model Driven Development* Marten van Sinderen Centre for Telematics and Information Technology, University of Twente,
Dr. Darius Silingas | No Magic, Inc. Domain-Specific Profiles for Your UML Tool Building DSL Environments with MagicDraw UML.
ModelPedia Model Driven Engineering Graphical User Interfaces for Web 2.0 Sites Centro de Informática – CIn/UFPe ORCAS Group Eclipse GMF Fábio M. Pereira.
Sheet 1 DocEng’03, Grenoble, November 2003 Model Driven Architecture based XML Processing Ivan Kurtev, Klaas van den Berg University of Twente, the Netherlands.
Common Terminology Services 2 CTS 2 Submission Team Status Update HL7 Vocabulary Working Group May 17, 2011.
Model transformation with a dedicated imperative language IRISA Rennes (France) - Triskell team Jean-Marc Jézéquel Didier Vojtisek Jean-Philippe Thibault.
EMEA Beat Schwegler Architect Microsoft EMEA HQ Ingo Rammer Principal Consultant thinktecture
Programmability Hiroshi Nakashima Thomas Sterling.
Developing Product Line Components Jan Bosch Professor of Software Engineering University of Groningen, Netherlands
OpenCCM: Status and Work plan Dr. Philippe Merle LIFL - INRIA ObjectWeb Architecture Meeting, Grenoble, 21 – 22.
Session 1 What Is the UML? Written by Thomas A. Pender Published by Wiley Publishing, Inc. October 5, 2011 Presented by Kang-Pyo Lee.
Nigel Baker UWE & CERN/EP-CMA Design Patterns for Integrating Product and Process Models The C.R.I.S.T.A.L. Project ( C ooperative R epositories & I nformation.
Ontologies Reasoning Components Agents Simulations An Overview of Model-Driven Engineering and Architecture Jacques Robin.
1 4th of October, 2006 © ATHENA Consortium 2006 B5 EADS CCR piloting Nicolas Figay, EADS Flora Robin, EADS ATHENA Intermediate Review October 2006.
Sheet 1MDAFA2004 Linköping, June 2004 A Language for Model Transformations in the MOF Architecture Ivan Kurtev, Klaas van den Berg University of Twente,
7/2/2016 1:52 AM HL7 SOA-Aware Enterprise Architecture Executive Summary HITSP October 28, 2008 Executive Summary HITSP October 28, 2008.
Advanced Software Engineering Dr. Cheng
Review of last class Software Engineering Modeling Problem Solving
SysML 2.0 Requirements for Visualization
Object-Oriented Analysis and Design
SysML v2 Formalism: Requirements & Benefits
Towards Effective Adaptive User Interfaces Design
Proposed SysML v2 Submission Plan
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Cloud Modeling Framework CloudMF
SysML 2.0 Concept and Needs for Visualization
Evaluating Compuware OptimalJ as an MDA tool
UML profiles.
An Introduction to Software Architecture
Execute your Processes
QVT Operational 1.0 Mini-deck
Model Driven Software Development
FRAMEWORKS AND REUSE What is “Framework”?
Test Domain and Description Language Recommendations
Software Architecture & Design
Presentation transcript:

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

This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES Template trtco V , 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 ( ) : 8 submissions Revised submission ( ): 5 submissions + Kennedy Carter in list 2 nd revised submission ( ) … 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

This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES Template trtco V , 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

This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES Template trtco V , 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

This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES Template trtco V , 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

This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES Template trtco V , 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 ?

This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES Template trtco V , 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

This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES Template trtco V , 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

This document and any data included are the property of THALES. They cannot be reproduced, disclosed or used without THALES' prior written approval. ©THALES Template trtco V , October 2003 THALES Research & Technology Contact information CARROLL research programme (THALES, CEA, INRIA) MOTOR project