MDA and Separation of Aspects: An approach based on multiples views and Subject Oriented Design Quercus Software Engineering Group Computer Science Department.

Slides:



Advertisements
Similar presentations
2/11/2014 8:44 AM The CDA Release 3 Specification Stack September 2009 HL7 Services-Aware Enterprise Architecture Framework (SAEAF)
Advertisements

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Professor John Hosking, Dean of Engineering and Computer Science Models, Modelling, MBSE.
SOA and MDA Hand-in-Glove or Square-Peg, Round-Hole? David Piper Principal Consultant.
An Aspect-Oriented Approach For Web Application Access Control Presented by: Mohamed Hassan Carleton University Carleton University
© 2007 ATLAS Nantes 1 Atlas Model Weaver Use Case: Aspect Oriented Modeling Marcos Didonet Del Fabro Atlas Group (INRIA & LINA), Université de Nantes,
Model Driven Architecture Efficiently react to Changing Architectural and Functional Requirements Stainless Steel Models for Red Rusting Technologies Wim.
A Pattern-Driven Security Process for SOA Applications
MDA – Model Driven Architecture: An introduction Franco Flore Senior Product Manager.
Amit, Keyur, Sabhay and Saleh Model Driven Architecture in the Enterprise.
Secure Middleware (?) Patrick Morrison 3/1/2006 Secure Systems Group.
Lecture 23: Software Architectures
Compuware Corporation 1 Begin. Compuware Corporation MDA & OptimalJ Wim Bast Bruce Epstein February 4, 2004.
1 FM Overview of Adaptation. 2 FM RAPIDware: Component-Based Design of Adaptive and Dependable Middleware Project Investigators: Philip McKinley, Kurt.
LUCENTIA Research Group Department of Software and Computing Systems Using i* modeling for the multidimensional design of data warehouses Jose-Norberto.
MDA as Approach to Manage Variability in Software Product Families
Roles and Responsibilities Jahangheer Shaik. Service Specification Specification requires development of three inter-related documents CIM, PIM and PSM.
1 Model Interface Implementation for Two-Way Obliviousness in Aspect-Oriented Modeling Presented by Wuliang Sun Department of Computer Science Baylor University.
ARCH-6: UML Modeling with Enterprise Architect Phillip Magnay Technical Architect.
Model Driven Security Framework for Definition of Security Requirements for SOA Based Applications Authors: Muhammad Qaisar Saleem, Jafreezal Jaafar, and.
Tsinghua University Service-Oriented Enterprise Coordination Prof. Dr. Yushun Fan Department of Automation, Tsinghua University,
MDA Guide Version CYT. 2 Outline OMG Vision and Process Introduction to MDA How is MDA Used? MDA Transformations Other MDA Capabilities Using the.
Desmond DSouza President Kinetium Desmond: add success stories, biz slant (investment and ROI), risks and critical.
Software Engineering CS B Prof. George Heineman.
Software Design Refinement Using Design Patterns Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
An Introduction to Software Architecture
Agenda 23 April, 2007 T Service-Oriented Architecture and Software Engineering 1 Service Oriented and Model Driven Architectures Pankaj Saharan.
Secure Systems Research Group - FAU A Pattern-Driven Process for Secure Service-Oriented Applications Ph.D Dissertation Defense Candidate: N. A. Delessy,
Mihir Daptardar Software Engineering 577b Center for Systems and Software Engineering (CSSE) Viterbi School of Engineering 1.
Developing.NET Web Service- based Architectures with Aspect-Oriented Component Engineering Santokh Singh 1, Professor John Grundy 1,2 and Professor John.
3 April SOA: Services Oriented Architecture MDA: Model Driven Architecture.
Introduction to MDA (Model Driven Architecture) CYT.
Sheet 1 / 21© in Bonn - 21 March 2006 Identification of Crosscutting in Software Design Klaas van den Berg – University.
Aspect Oriented Programming Razieh Asadi University of Science & Technology Mazandran Babol Aspect Component Based Software Engineering (ACBSE)
1 MDWE'2008, Toulouse, France, September 30, 2008 A Comparative Analysis of Transformation Engines for User Interface Development Juan Manuel González.
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
Challenging BX as a Software Engineer: What is a problem? How much BX do we need? Ekkart Kindler.
Secure Systems Research Group - FAU Securing Service-Oriented Architectures using a Model-driven Approach Nelly A Delessy.
Formal Analysis of Problem Domain Workflows Uldis Donins Riga Technical University Baltic DB & IS 2012, July 8-11, Vilnius, Lithuania This work.
Copyright © 2004 InteliData A Real-World Example of MDA without Automation Ed Seidewitz 26 August 2004.
Secure Systems Research Group - FAU Classifying security patterns E.B.Fernandez, H. Washizaki, N. Yoshioka, A. Kubo.
1 Model Compiler Construction Based on Aspect-oriented Mechanisms Naoyasu Ubayashi (Kyushu Institute of Technology) Tetsuo Tamai (University of Tokyo)
RTAS 2003 Workshop on Model-Driven Embedded Systems Washington, D.C., May 27-30, 2003 Juan Pablo Zamora Zapata Francis Bordeleau Defining UML Profiles.
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
1 A Model-Driven Approach For Information System Migration Raymonde Le Delliou 1, Nicolas Ploquin 2, Mariano Belaunde 3, Reda Bendraou 4, Louis Féraud.
1 Model Evolution with Aspect-oriented Mechanisms Naoyasu Ubayashi (Kyushu Institute of Technology) Tetsuo Tamai (University of Tokyo) Shinji Sano, Yusaku.
Introduction Better Faster Cheaper (pick any two) On-going issue that continues to motivate research in software engineering Applications: –continue to.
MDA – Model Driven Architecture Olivier Riboux. Overview What is MDA? The Challenges MDA addresses Developing in the MDA Benefits / Conclusion Case Study:
XML Schemas: From Design to Exploitation and Back Again Irena Mlýnková, Martin Nečaský Charles Univeristy in Prague Svratka 2008.
December 4, ICSSEA’03 The SmartTools Software Factory The MDA approach and Generative programming for Software Development:
Devon M. Simmonds SERP’08, July-14-17, Las Vegas 1 Aspect-oriented Approaches to Model Driven Engineering Devon M. Simmonds Computer Science Department.
Developing Product Line Components Jan Bosch Professor of Software Engineering University of Groningen, Netherlands
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Ontologies Reasoning Components Agents Simulations An Overview of Model-Driven Engineering and Architecture Jacques Robin.
1 February 1-7, Cancun, Mexico ACHI’09 A structured approach to support 3D User Interface Development Juan Manuel Gonzalez-Calleros, Jean Vanderdonckt.
XASTRO vs RASDS CCSDS SAWG Meeting. CCSDS SAWG2 Presentation Outline XASTRO study analysis phase conclusions Relationship between XASTRO and UML 2 / SysML.
Aspect-oriented Code Generation Approaches Abid Mehmood & Dayang N. A. Jawawi Department of Software Engineering Faculty of Computer Science and Information.
Page 1 Hitachi Ltd. – FhI FOKUS TTCN-3 User Conference, June 2005 MDA based approach for generation of TTCN-3 test specifications Hideto Ogawa, Hitachi.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
CHESS Methodology and Tool Federico Ciccozzi MBEES Meeting Sälen, January 2011 January 2011.
Modelowanie i analiza systemów informacyjnych Model Driven Architecture Marek Bazan Marzec 2017.
XASTRO vs RASDS CCSDS SAWG Meeting
MACS 2005 First International Workshop on the Modeling and Analysis of Concerns in Software Concern Management for Constructing Model Compilers -- Towards.
Instructor: Dr. Hany H. Ammar
A Web-enabled Approach for generating data processors
Chapter 13 Logical Architecture.
Evaluating Compuware OptimalJ as an MDA tool
ARCH-5: From Design to Implementation in OpenEdge® using UML and MDA
Chapter 13 Logical Architecture.
Energy-Efficient Storage Systems
Presentation transcript:

MDA and Separation of Aspects: An approach based on multiples views and Subject Oriented Design Quercus Software Engineering Group Computer Science Department University of Extremadura, Spain Pablo Amaya, Carlos González and Juan M. Murillo

MDA and Separation of Aspects: an approach based on Viewpoints Outline Introduction  Model-Driven Architecture  The problem!! The proposal  Case study  Subject Oriented PIM and PSM  Traceability, evolution and change impact Conclusions and future works

MDA and Separation of Aspects: an approach based on Viewpoints Introduction Model-Driven Architecture  OMG’s initiative  To enable Model-Driven Development  Three abstraction levels  To improve development of large complex system CIM PIM transformation PSM transformation

MDA and Separation of Aspects: an approach based on Viewpoints Introduction Large complex systems  e-government Software development with MDA  Problems Each model becomes large and monolithic  Models are not manageable, reusable, adaptable, etc.  Transformations between models are too complex.  Objectives To improve :  modeling  traceability  evolution  … Solution: Separation of Aspects in all MDA levels.

MDA and Separation of Aspects: an approach based on Viewpoints Introduction In all levels MDA Viewpoints skateholder concerns CIM1 CIM2 PIM1 PIM2 PSM1 PSM2 Communication Security Functionality CIM3 PIM3 PSM3 CIMN PIMN PSMN Aspect-Oriented Software Development Crosscutting Concerns == Aspects

MDA and Separation of Aspects: an approach based on Viewpoints Case Study Subject Oriented Design Composition Patterns Use Case  Subject or CP

MDA and Separation of Aspects: an approach based on Viewpoints Subject Oriented PIM and PSM

MDA and Separation of Aspects: an approach based on Viewpoints Transformation/Mapping Subject Oriented PIM and PSM

MDA and Separation of Aspects: an approach based on Viewpoints Traceability, evolution and change impact Create resolving Recover Expedient Authenticate User < < o v e r l a p > > < < i n t e r a c t > > < < i n t e r a c t > > ExpedientPenalty getId() getDate()... setInstructor() storeResolve()..... getAmount() getTypePenalty()... setAmount() setDateExpiration() User getPersonalData()... notifyResolve()..... ExpedientPenalty getId() getDate()... setInstructor() storeResolve()..... getAmount() getTypePenalty()... setAmount() setDateExpiration() User getPersonalData()... notifyResolve()..... CIM PIM PSM New Expedient Create resolving Recover Expedient Authenticate User < < o v e r l a p > > < < ov e r l a p > > > < < i n t e r a c t > > << i n t e r ac t >> StakeInstructorUser > StakeStaffUser > StakeSecExpert package resolvingpackage expedientpackage security > StakeInstructorUser > StakeStaffUser > StakeSecExpert package expedient package security package resolving > CreatResolving > RecovExpedient > AuthenticatUser > NewExpedient <ClassAuth, _AuthOp(..)> > JSPserver bind[ ] b i n d [ < U s e r, g e t P e r s o n a l D a t a ( ) > ] b i nd [ < U s e r, g e t A n t ece d e n t D a t a () > ] > StakeInstructorUser > StakeStaffUser > StakeSecExpert package expedient package security package resolving > CreatResolving > RecovExpedient > AuthenticatUser > NewExpedient <ClassAuth, _AuthOp(..)> bind[ ] b i n d [ < U s e r, g e t A n t e c e d e n t D a t a ( ) > ] { b y N a m e } < < m e r g e > > { b y N a m e } < < m e r g e > > Transformation

MDA and Separation of Aspects: an approach based on Viewpoints Traceability, evolution and change impact Create resolving Recover Expedient Authenticate User < < o v e r l a p > > < < i n t e r a c t > > < < i n t e r a c t > > ExpedientPenalty getId() getDate()... setInstructor() storeResolve()..... getAmount() getTypePenalty()... setAmount() setDateExpiration() User getPersonalData()... notifyResolve()..... ExpedientPenalty getId() getDate()... setInstructor() storeResolve()..... getAmount() getTypePenalty()... setAmount() setDateExpiration() User getPersonalData()... notifyResolve()..... CIM PIM PSM New Expedient Create resolving Recover Expedient Authenticate User < < o v e r l a p > > < < ov e r l a p > > > < < i n t e r a c t > > << i n t e r ac t >> StakeInstructorUser > StakeStaffUser > StakeSecExpert package resolvingpackage expedientpackage security > StakeInstructorUser > StakeStaffUser > StakeSecExpert package expedient package security package resolving > CreatResolving > RecovExpedient > AuthenticatUser > NewExpedient <ClassAuth, _AuthOp(..)> > JSPserver bind[ ] b i n d [ < U s e r, g e t P e r s o n a l D a t a ( ) > ] b i nd [ < U s e r, g e t A n t ece d e n t D a t a () > ] > StakeInstructorUser > StakeStaffUser > StakeSecExpert package expedient package security package resolving > CreatResolving > RecovExpedient > AuthenticatUser > NewExpedient <ClassAuth, _AuthOp(..)> bind[ ] b i n d [ < U s e r, g e t A n t e c e d e n t D a t a ( ) > ] { b y N a m e } < < m e r g e > > { b y N a m e } < < m e r g e > > Transformation

MDA and Separation of Aspects: an approach based on Viewpoints Adding Aspects -- viewpoints New Expedient Create resolving Recover Expedient Authenticate User < < o v e r l a p > > < < ov e r l a p > > > < < i n t e r a c t > > << i n t e r ac t >> StakeInstructorUser > StakeStaffUser > StakeSecExpert package resolvingpackage expedientpackage security > StakeInstructorUser > StakeStaffUser > StakeSecExpert package expedient package security package resolving > CreatResolving > RecovExpedient > AuthenticatUser > NewExpedient <ClassAuth, _AuthOp(..)> bind[ ] b i n d [ < U s e r, g e t A n t e c e d e n t D a t a ( ) > ] { b y N a m e } < < m e r g e > > { b y N a m e } < < m e r g e > > New requirement Persistence Repository To add these aspect to the three levels Complete views or aspects can be modeled and can be added to MDA repositoires

MDA and Separation of Aspects: an approach based on Viewpoints Conclusions and Future Works Improvements in MDA  Concurrent Development  Evolution Change Impact  Additive vs Invasive Change propagation  Traceability  Models more reusable, manageable and adapatable  To allow us to develop aspect repositories Future work directions  In general: To mature the proposal A Foundation for view repositories  To model CIM with other diagrams Workflow, domain models,activity diagrams. etc.  To enhance relationships between views  Intregation of views at model or code level Order of composition  Consistency Check  Transformations between aspect-models

Quercus Software Engineering Group University of Extremadura, Spain Pablo Amaya, Carlos González and Juan M. Murillo MDA and Separation of Aspects: An approach based on multiples views and Subject Oriented Design