Huseyin Ergin and Eugene Syriani. PROBLEM (DIDN’T CHANGE) Development of model transformation is still an error-prone and hard task. One reason is the.

Slides:



Advertisements
Similar presentations
Three-Step Database Design
Advertisements

Eugene Syriani and Huseyin Ergin University of Alabama Software Modeling Lab Software Engineering Group Department of Computer Science College of Engineering.
Huseyin Ergin and Eugene Syriani University of Alabama Software Modeling Lab Software Engineering Group Department of Computer Science College of Engineering.
Architecture Representation
Higher-Order Transformation Eugene SyrianiandHans Vangheluwe.
AToMPM Solution for the IMDB Case Study Huseyin Ergin and Eugene Syriani.
SYSE 802 John D. McGregor Module 2 Session 2 Method Tailoring.
IMS1805 Systems Analysis Topic 3: Doing Analysis (continued from previous weeks)
Huseyin Ergin and Eugene Syriani. PROBLEM Development of model transformation is still an error-prone and hard task. One reason is the lack of a development.
Hüseyin Ergin University of Alabama Software Modeling Lab Software Engineering Group Department of Computer Science College of Engineering.
Systems Analysis and Design 8th Edition
Chapter 4.
Systems Analysis and Design 9th Edition
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Sheet 1© 2005 Lentedagen, 30 March-1 April 2005 IPA Lentedagen on Software Architecture Model Transformations in MDA Ivan Kurtev.
Software Issues Derived from Dr. Fawcett’s Slides Phil Pratt-Szeliga Fall 2009.
Huseyin Ergin Advisor: Dr. Eugene Syriani University of Alabama Software Modeling Lab Software Engineering Group Department of Computer Science College.
1 An introduction to design patterns Based on material produced by John Vlissides and Douglas C. Schmidt.
Formalizing Material Flow Diagrams How can an MDE approach be used to improve the design process of material handling systems? Robert-Jan Bijl.
Proposal of Huseyin Ergin University of Alabama Department of Computer Science College of Engineering Committee Members :Dr. Eugene Syriani (advisor) Dr.
10 December, 2013 Katrin Heinze, Bundesbank CEN/WS XBRL CWA1: DPM Meta model CWA1Page 1.
Deriving AO Software Architectures using the AO-ADL Tool Suite Luis Fernández, Lidia Fuentes, Mónica Pinto, Juan A. Valenzuela Universidad de Málaga
UML Unified Modeling Language. What is UML? Unified Modeling Language (UML) is a standardized, general-purpose modeling language in the field of software.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Software Design Patterns for Information Visualization 薛乃榮 Q NCBCI LAB.
Introduction to MDA (Model Driven Architecture) CYT.
A REFACTORING TOOL FOR DESIGN PATTERNS WITH MODEL TRANSFORMATIONS Zekai Demirezen Yasemin Topaloğlu Ege University Department of Computer Engineering
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 07. Review Architectural Representation – Using UML – Using ADL.
Key Challenges for Modeling Language Creation by Demonstration Hyun Cho, Jeff Gray Department of Computer Science University of Alabama Jules White Bradley.
Unified Modeling Language, Version 2.0
METACASE. WHAT THIS PRESENTATION IS ABOUT  What’s META MODELING?  What’s METACASE?  METAEDIT+ 5.1 EVALUTION PROGRAM  Diagram and its kinds.
Chapter 9 Moving to Design
Validated Model Transformation Tihamér Levendovszky Budapest University of Technology and Economics Department of Automation and Applied Informatics Applied.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
A language to describe software texture in abstract design models and implementation.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
Hybrid Transformation Modeling Integrating a Declarative with an Imperative Model Transformation Language Pieter Van Gorp
Dr. Darius Silingas | No Magic, Inc. Domain-Specific Profiles for Your UML Tool Building DSL Environments with MagicDraw UML.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.
Nathalie Aquino 1, Jean Vanderdonckt 2, Francisco Valverde 1, Oscar Pastor 1 1 Department of Information Systems and Computation, Valencia University of.
Lab 5 CPIT 250 System Analysis and Design.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Visualization Four groups Design pattern for information visualization
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
Modeling the ODP Computational Viewpoint with UML 2.0: The Templeman Library Example José Raúl Romero, Antonio Vallecillo Universidad de Málaga, Spain.
1 Unified Modeling Language, Version 2.0 Chapter 2.
Mapping Objects ↔Relational DB. The Problem with Databases Databases store data in rows in tables, which are not like objects. We can simulate object.
Software Design Patterns in Test Automation
Class Diagrams. Terms and Concepts A class diagram is a diagram that shows a set of classes, interfaces, and collaborations and their relationships.
Yu, et al.’s “A Model-Driven Development Framework for Enterprise Web Services” In proceedings of the 10 th IEEE Intl Enterprise Distributed Object Computing.
Sheet 1 Forum on Specification and Design Languages (FDL), Frankfurt, September 2003 UML to XML-Schema Transformation: a Case Study in Managing Alternative.
Basic Characteristics of Object-Oriented Systems
DBS201: Data Modeling. Agenda Data Modeling Types of Models Entity Relationship Model.
WELCOME TO OUR PRESENTATION UNIFIED MODELING LANGUAGE (UML)
OBJECT ORIENTED VS STRUCTURED WHICH ONE IS YOUR CHOICE.
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
Database Development (8 May 2017).
Design Pattern-Driven Development of Model Transformations
The Movement To Objects
Object-Oriented Modeling with UML
Systems Analysis and Design With UML 2
Object Oriented Analysis and Design
Domain Class Diagram Chapter 4 Part 2 pp
Implementing Language Extensions with Model Transformations
Chapter 9 Architectural Design.
Implementing Language Extensions with Model Transformations
Building pattern  Complete the following tables and write the rule 
Software Architecture & Design
Presentation transcript:

Huseyin Ergin and Eugene Syriani

PROBLEM (DIDN’T CHANGE) Development of model transformation is still an error-prone and hard task. One reason is the lack of a development process. [1] – Design it before implement it. Software developers have been designing using UML. – With help of GoF design patterns. Main goal is: 2 [1] Guerra, E., de Lara, J., Kolovos, D., Paige, R., and dos Santos, O. (2013) Engineering model transformations with transML. Software and Systems Modeling, 12, 555–577.

EXISTING TEMPLATES 3 Existing model transformation design pattern (MTDP) studies. – Not all of them call themselves MTDP though. – The separation between reusable idioms, patterns, design patterns. But the inconsistency is clear. Unification will help what is expected from a pattern and what are the outcomes.

ADDITIONAL CONSTRUCT GoF patterns have the structure field. – Which makes the clear separation with other design pattern studies. – In OMT (UML) design. – The skeleton of the solution. – Easy to understand by most developers. We have proposed a language at ICMT – DelTa. – Assigning a graphical concrete syntax. – Semi-automation while generating model transformation solutions. DelTa structure of a MTDP is also in the unified template. 4

SAMPLE DESIGN PATTERN Top-down Phased Construction [1] : – Summary: This pattern separates the transformation into phases depending on how the target model is composed. The complete summary is found in [1]. – Application conditions: When there is a composition hierarchy in the source metamodel and the sub-element is mandatory in that relation. 5 [1]: Lano, K.; Kolahdouz-Rahimi, S., "Model-Transformation Design Patterns," Software Engineering, IEEE Transactions on, vol.40, no.12, pp.1224,1259, Dec

SAMPLE DESIGN PATTERN – Solution: The transformation is split into two phases. In the formerPhase rule, the target element corresponding to the super-element in the source is first created. In the latterPhase rule, target elements corresponding to the sub-elements in the source are then created. – Benefits: This pattern increases the modularity of the rules, letting each rule create one layer of target elements. – Disadvantages: Since the rules are broken into phases, that will increase the rule count. 6

SAMPLE DESIGN PATTERN – Examples: The UML class diagram to relational database diagrams can be considered a top-down phased construction, where we first use classes to create tables, and then use attributes to create columns. – Implementation: The model transformation languages with explicit scheduling can create phases sequentially. The languages, that have implicit scheduling only, can refer to “simulating explicit rule scheduling” pattern. – Related patterns: The pattern resembles entity relationship mapping pattern (many refs), when the entities are considered the top layer and relations are the layer below. There are also variations of this pattern that starts the construction starting from bottom. 7

CONCLUSION Now we implement a semi-automatic way of generating transformations – Starting with MoTif language, which is our favorite tool The unified template should help in: – What developers are expected. – How they describe a pattern. 8

QUESTIONS Thanks for listening… 9