An OPM-Based Layered Architecture for Modeling Design Patterns

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

Software Architecture Reconstruction By Elizabeth Griffith Derived from a report done by Vijaya Datta Mayyuri.
Applying the Human Views for MODAF to the conception of energy-saving work solutions Dr Anne Bruseberg Systems Engineering & Assessment Ltd, UK on behalf.
CIT731: Database Development Object Oriented Modeling (OOM)
Model Driven Architecture Efficiently react to Changing Architectural and Functional Requirements Stainless Steel Models for Red Rusting Technologies Wim.
Modeling Process-Oriented Integration of Services Using Patterns and Pattern Primitives Uwe Zdun and Schahram Dustdar Distributed Systems Group Institute.
Design Patterns for Metamodel Design Domain-Specific Modeling Workshop Portland, Oregon October 23, 2011 Hyun Cho and Jeff Gray University of Alabama Department.
Design Patterns In OPM Presented by: Galia Shlezinger Instructors: Prop. Dov Dori, Dr. Iris Berger.
Understanding Metamodels. Outline Understanding metamodels Applying reference models Fundamental metamodel for describing software components Content.
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
April 15, 2005Department of Computer Science, BYU Agent-Oriented Software Engineering Muhammed Al-Muhammed Brigham Young University Supported in part by.
Elearning in the semantic age : Emerging web technologies provides exciting new posibilities. : Standards focusing on semantics rather than syntax provides.
A Formal Foundation Supporting MDD --- ZOOM Approach Hongming Liu Lizhang Qin 11/08/2003.
Adaptable Architecture for Meta- Programmable Modeling Tools Matt Emerson Advisor: Janos Sztipanovits The Core Layer The.
Whole Platform Tesi di Dottorato di: RICCARDO SOLMI Università degli Studi di Bologna Facoltà di scienze matematiche, fisiche e naturali Corso di Dottorato.
Who am I? ● Catalin Comanici ● QA for 10 years, doing test automation for about 6 years ● fun guy and rock star wannabe.
10 December, 2013 Katrin Heinze, Bundesbank CEN/WS XBRL CWA1: DPM Meta model CWA1Page 1.
HL7 UK 2003 (c) Abies Ltd Modelling Clinical Information Using UML Tim Benson Abies Ltd
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
COMP 6471 Software Design Methodologies Winter 2006 Dr Greg Butler
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 18 Slide 1 Software Reuse.
Software Engineering Muhammad Fahad Khan
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Workshop on Integrated Application of Formal Languages, Geneva J.Fischer Mappings, Use of MOF for Language Families Joachim Fischer Workshop on.
1 Introduction to Modeling Languages Striving for Engineering Precision in Information Systems Jim Carpenter Bureau of Labor Statistics, and President,
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Second RMSIG Workshop Methodology and Process Wolfram Höpken.
1. 2 Purpose of This Presentation ◆ To explain how spacecraft can be virtualized by using a standard modeling method; ◆ To introduce the basic concept.
Chapter 7 – Design and Implementation Lecture 2 1Chapter 7 Design and implementation.
A Template-Based Model Transformation Approach Using A Simplified Hierarchical Metamodel Ph.D Dissertation Hongming Liu DePaul University.
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
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
2nd TTCN-3 User Conference, June The TTCN-3 Metamodel – A Basis for Tool Integration Ina Schieferdecker TU Berlin/Fraunhofer Fokus Hajo Eichler,
What is MOF? The Meta Object Facility (MOF) specification provides a set of CORBA interfaces that can be used to define and manipulate a set of interoperable.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
© DATAMAT S.p.A. – Giuseppe Avellino, Stefano Beco, Barbara Cantalupo, Andrea Cavallini A Semantic Workflow Authoring Tool for Programming Grids.
L8 - March 28, 2006copyright Thomas Pole , all rights reserved 1 Lecture 8: Software Asset Management and Text Ch. 5: Software Factories, (Review)
ARCH-2: UML From Design to Implementation using UML Frank Beusenberg Senior Technical Consultant.
Hybrid Transformation Modeling Integrating a Declarative with an Imperative Model Transformation Language Pieter Van Gorp
Architectural pattern: Interceptor Source: POSA II pp 109 – 140POSA II Environment: developing frameworks that can be extended transparently Recurring.
INRIA - LaBRICharles Consel Jan-06 1 Domain-Specific Software Engineering Charles Consel Phoenix Research Group LaBRI /INRIA-Futurs January 2006.
Dr. Darius Silingas | No Magic, Inc. Domain-Specific Profiles for Your UML Tool Building DSL Environments with MagicDraw UML.
MDA – Model Driven Architecture Olivier Riboux. Overview What is MDA? The Challenges MDA addresses Developing in the MDA Benefits / Conclusion Case Study:
Sheet 1 DocEng’03, Grenoble, November 2003 Model Driven Architecture based XML Processing Ivan Kurtev, Klaas van den Berg University of Twente, the Netherlands.
1 OO Analysis & Design - Introduction to main ideas in OO Analysis & design - Practical experience in applying ideas.
SwA Co-Chair and Task Lead Strategy Session Agenda Technology, Tools and Product Evaluation Working Group Status Briefing Co-Chair(s) Michael Kass (NIST),
Standards Stephen J. Mellor Chief Scientist. 2 Why Standards? n Increases choice for customers n Increases the size of the market n Promotes competition.
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.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML: UML 2 Metamodel Note to Instructor: The material in this.
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.
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Wolfram Höpken IFITT RMSIG.
Software Reuse. Objectives l To explain the benefits of software reuse and some reuse problems l To discuss several different ways to implement software.
SysML v2 Formalism: Requirements & Benefits
Introduction to Design Patterns
OPM/S: Semantic Engineering of Web Services
Software Reuse ©Ian Sommerville 2006.
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Modelling Clinical Information Using UML
Introduction.
Constructing MDA-based Application Using Rational XDE for .NET
Metadata Framework as the basis for Metadata-driven Architecture
Chapter 7 –Implementation Issues
Metadata The metadata contains
Selecting Services for Web Applications: The Open Hypermedia Case
Software Architecture & Design
Presentation transcript:

An OPM-Based Layered Architecture for Modeling Design Patterns Galia Shlezinger Dr. Iris Berger Prop. Dov Dori

Agenda Design pattern Metamodeling framework Three-layer architecture for modeling design patterns Summery

Design patterns A design pattern is defined as a description of a solution to a recurring design problem. The most common use of design patterns is as a reference for the designer. The system model itself usually contains no record of the patterns that were used.

Design pattern model Most works on design patterns consider only the solution part of the design pattern. The problem part of the design pattern is not less important than the solution part, as it puts the solution in the correct context and enables reuse of the solution.

Modeling the entire design pattern Pattern and Component Markup Language (PCML)[1] – Supported by a design tool. Design pattern matching [3] – extends the PCML meta-model and allows simplified search of patterns. The pattern model is separate from the system model In both solutions.

Classical Framework for metamodeling[2] Meta-metamodel (M3) OPM UML Metamodel (M2) Structure and semantics Design pattern model M1.5 OPM model UML model Model (M1) Information (M0) System implementation

Three design pattern abstraction levels Meta design pattern level (M2) Design pattern level (M1.5) System level (M1)

Meta design pattern level (M2)

Design pattern level (M1.5) The Observer pattern: Problem: Solution:

System level (M0) Observer pattern implementation: The pattern model is mapped to the system model using meta-libraries.

Summery All aspects of the design pattern are modeled (and therefore considered). The knowledge of which design patterns are used in a system model is contained in the model itself. OPM meta-libraries are used to map design pattern models (M1.5) to the system model (M1). The design pattern models can be searched to find problems similar to the one at hand.

References [1] Object Venture Inc. PCML - Pattern and Component Markup Language, www.objectventure.com/pcml.htm [2] OMG, "Meta Object Facility (MOFTM)", version 1.4, 2003, http://www.omg.org/docs/formal/02-04-03.pdf [3] Petri, D., Csertan, G., "Design Pattern Matching". Periodica Polytechnica Ser. El. Eng. Vol. 46, no. 3-4, pp. 205-212