J.E. Rivera, D. Ruiz-González, F. López-Romero, J. Bautista, and A. Vallecillo MtATL 09 Nantes, July 09.

Slides:



Advertisements
Similar presentations
An ASN.1 Profile Anders Ek
Advertisements

1 Hugo Bruneliere (INRIA) MODELPLEX Interim Review, Brussels (Belgium), 27 th of March 2009 WP3 - Model Engineering D3.2.d “Global Model Management Traceability.
Alternative Approach to Systems Analysis Structured analysis
WebRatio BPM: a Tool for Design and Deployment of Business Processes on the Web Stefano Butti, Marco Brambilla, Piero Fraternali Web Models Srl, Italy.
Software Design Deriving a solution which satisfies software requirements.
Formal Methods of Systems Specification Logical Specification of Hard- and Software Prof. Dr. Holger Schlingloff Institut für Informatik der.
Detailed Design Kenneth M. Anderson Lecture 21
Pieter Van Gorp, Olaf Muliawan, Hans Schippers MoTMoT.sourceforge.net.
Towards Modular Code Generators Using Symmetric Language-Aware Aspects Steffen Zschaler, Awais Rashid FREECO’11 Lancaster, 26 July 2011.
UML Notations Activity diagrams State diagrams Class diagrams Use-case diagrams.
Generative Programming. Generic vs Generative Generic Programming focuses on representing families of domain concepts Generic Programming focuses on representing.
Mining Metamodels From Instance Models: The MARS System Faizan Javed Department of Computer & Information Sciences, University of Alabama at Birmingham.
Chapter 10: Architectural Design
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
CLARIN tools for workflows Overview. Objective of this document  Determine which are the responsibilities of the different components of CLARIN workflows.
Chapter 10 Architectural Design
INFO415 Approaches to System Development: Part 2
An Approach and Tool for Synchronous Refactoring of UML Diagrams and Models Using Model-to-Model Transformations Hafsteinn Þór Einarsson Helmut Neukirchen.
Modelling information systems
1 An Analytical Evaluation of BPMN Using a Semiotic Quality Framework Terje Wahl & Guttorm Sindre NTNU, Norway Terje Wahl, 14. June 2005.
BPMN By Hosein Bitaraf Software Engineering. Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes.
Towards Human-Executable Business Process Modeling Janis Barzdins, Edgars Rencis, Agris Sostaks Institute of Mathematics and Computer Science, University.
Static Control-Flow Analysis for Reverse Engineering of UML Sequence Diagrams Atanas (Nasko) Rountev Ohio State University with Olga Volgin and Miriam.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
Software Design Designing the overall structure (architecture) of a software system Designing small pieces of computation Designing non-automated processes.
METACASE. WHAT THIS PRESENTATION IS ABOUT  What’s META MODELING?  What’s METACASE?  METAEDIT+ 5.1 EVALUTION PROGRAM  Diagram and its kinds.
Object-Oriented Analysis and Design An Introduction.
SOFTWARE DESIGN.
Object Management Group (OMG) Specifies open standards for every aspect of distributed computing Multiplatform Model Driven Architecture (MDA)
Plant Modeling for Powertrain Control Design Modelica Automotive Workshop Dearborn, MI November 19, 2002 Dr. Larry Michaels GM Powertrain Controls Engineering.
Validated Model Transformation Tihamér Levendovszky Budapest University of Technology and Economics Department of Automation and Applied Informatics Applied.
Generative Programming. Automated Assembly Lines.
Conceptual Modelling – Behaviour
1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.
1 Introduction to Software Engineering Lecture 1.
Chapter 12: Design Phase n 12.1 Design and Abstraction n 12.2 Action-Oriented Design n 12.3 Data Flow Analysis n Data Flow Analysis Example n
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
UHD::3320::CH121 DESIGN PHASE Chapter 12. UHD::3320::CH122 Design Phase Two Aspects –Actions which operate on data –Data on which actions operate Two.
Hybrid Transformation Modeling Integrating a Declarative with an Imperative Model Transformation Language Pieter Van Gorp
Flowcharts and Algorithms. Review of Terms  A computer is a machine that can represent and manipulate data –Ultimately the data and the instructions.
Dr. Darius Silingas | No Magic, Inc. Domain-Specific Profiles for Your UML Tool Building DSL Environments with MagicDraw UML.
Dr.Basem Alkazemi
Automata Based Method for Domain Specific Languages Definition Ulyana Tikhonova PhD student at St. Petersburg State Politechnical University, supervised.
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
Graphical Modeling Framework (GMF) Richard C. Gronback Project Lead.
© Siemens AG, CT SE 2 C O R P O R A T E T E C H N O L O G Y 1 Model-Driven Development for Pluggable Collaborations Iris Groher, Stephan Bleicher, Christa.
UML MARTE Time Model for Spirit IP-XACT Aoste Project INRIA Sophia-Antipolis.
Object-Oriented Modeling: Static Models. Object-Oriented Modeling Model the system as interacting objects Model the system as interacting objects Match.
Software Design Process
Lab 5 CPIT 250 System Analysis and Design.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
BPMN.  BPMN will provide businesses with the capability of understanding their internal business procedures in a graphical notation.
Class Diagrams. Terms and Concepts A class diagram is a diagram that shows a set of classes, interfaces, and collaborations and their relationships.
Introduction to Computing Concepts Note Set 19. Design Creating complex software… ▫ Not done by just one person (or two, or three) ▫ Can’t just sit down.
Collaboration diagrams. Deployment diagrams. Lesson 4.
Architectural Complexity  A useful technique for assessing the overall complexity of a proposed architecture is to consider dependencies between components.
UML(Unified Modeling Language)
Atanas (Nasko) Rountev Ohio State University
Unified Modeling Language
Software Design Mr. Manoj Kumar Kar.
Object Oriented Analysis and Design
Unified Modelling Language
Software Design Methodologies and Testing
Presentation transcript:

J.E. Rivera, D. Ruiz-González, F. López-Romero, J. Bautista, and A. Vallecillo MtATL 09 Nantes, July 09

MtATL 09. Nantes, July 09 (2)  Models: key artifacts in all phases of development  They usually address one concern  Implementation of a system obtained by applying a set of transformations

MtATL 09. Nantes, July 09 (3)  Construction of complex model transformations from other transformations already defined  Global Model Management ● Megamodels as registries for resources available: models, metamodels, transformations... ● Reused to build new tools, processes and transformations.  Ant tasks

MtATL 09. Nantes, July 09 (4)  A DSL that enables the high-level orchestration of ATL model transformations. ● Modular and compositional construction of complex model transformations chains  A graphical notation (similar to UML Activity diagrams) and an execution engine  Supports conditional branches, loops, composite transformations, HOT…

MtATL 09. Nantes, July 09 (5)

MtATL 09. Nantes, July 09 (6)  Temporary VS. Persistent Models

MtATL 09. Nantes, July 09 (7)  ATL Units: modules, libraries and queries  Composite Transformation

MtATL 09. Nantes, July 09 (8)  Identity Transformation ● Do not alter data  Generic Transformation ● HOT

MtATL 09. Nantes, July 09 (9)  Several outgoing data flows

MtATL 09. Nantes, July 09 (10)  Decision nodes If-then-else-endif If-then-endif

MtATL 09. Nantes, July 09 (11)

MtATL 09. Nantes, July 09 (12) 1. elements = searchInputElements(); 2. void execute(elements) { 3. for each e in elements { 4. targetElements = searchTargetElements(e); 5. for each targetElement in targetElements { 6. if ( enabled(targetElement) ) { 7. executeOneElement(targetElement); 8. targetOutgoings = searchTargetElements(targetElement); 9. execute(targetOutgoings) 10. } 11. } 12. } 13. }

MtATL 09. Nantes, July 09 (13)

MtATL 09. Nantes, July 09 (14) ● A graphical executable language for the orchestration of ATL transformations ● Provides appropriate mechanisms to enable the modular and compositional construction of complex model transformations chains.  Future Work: ● Static validation of the Wires* models: valid connections between output and input models (subtyping algorithm) ● Other kinds of model transformations: injectors, extractors (e.g., TCS). ● Other transformation languages ● New ATL features