Model Driven Architecture (MDA): Motivations, Status & Future

47
Copyright 2001, UNISYS Corporation Slide 1 Model Driven Architecture (MDA): Motivations, Status & Future September 4-7, 2001, Seattle, WA Sridhar Iyengar Unisys Fellow OMG Architecture Board, MDA Evangelist [email protected]

description

 

Transcript of Model Driven Architecture (MDA): Motivations, Status & Future

Page 1: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 1

Model Driven Architecture (MDA):Motivations, Status & Future

September 4-7, 2001, Seattle, WASridhar IyengarUnisys Fellow

OMG Architecture Board, MDA Evangelist [email protected]

Page 2: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 2

Presentation OverviewPresentation Overview■ Introduction - The integration problem■ Motivation for MDA

– Investment Protection of Intellectual and IT Assets – Managing Technology Innovation and Churn

• Mapping to J2EE• Mapping to .Net {Web Services - Initial target}• Mapping to Transition (legacy architecture)

■ OMG Model Driven Architecture (MDA) Overview ■ MDA Status : What is in the pipeline?

– UML2, Action Semantics, UML Profile for EDOC– XMI for XML Schemas, CWM Web Services...

■ Future of MDA

Page 3: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 3

■ Global services and technology company– 2000 Revenues : $6.9 Billion– www.unisys.com

■ Focus on Enterprise Class E-Business Solutions and Servers around the world– Integrated Solutions for Financial, Telcom, Publishing and Government

markets– Windows 2000 DataCenter focus (ES7000) and ClearPath Servers

■ Actively using several – OMG MDA Technologies : UML, XMI, MOF, CWM and MDA– Java Technologies : J2EE, JMI, UML4EJB...– Microsoft Technologies : Win2K, COM+, .Net platform and tools– W3C Technologies : XML Suite of standards

■ Member of OMG, W3C, UDDI Consortium, OASIS...

Page 4: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 4

Architect (XML!)

‘‘Muddleware’Muddleware’ Architect’s Dilemma Architect’s Dilemma

BEAWeblogic

Distributed, Heterogeneous, Client/Server !Multiple Clients, Servers, Tools, Apps, O/S, File systems, Databases, Repositories, Data Models, Object Models...

DataMartsSQL/Server

UnisysLINC,DMSII

WarehouseBuilder

Oracle Apps

Microsoft.NET ServersSQL Server

SAPBI WareHouse

SiebelWarehouse

NCRTeradata

Middleware (Tuxedo, TIP, DCOM, IIOP, RMI, EJB, COM+, SOAP…)Information Models/Schemas (MOF, XML, UML, CWM, SPE, BODs, ….)

Page 5: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 5

The Technology Salad Bar The Technology Salad Bar (A small subset!)(A small subset!)

Capability J2EE COM+ CORBA/OMA Web Services OMG MDA .NetNetwork Layer TCP/IP TCP/IP TCP/IP TCP/IP TCP/IP TCP/IPWeb Protocol HTTP HTTP HTTP HTTP HTTP HTTP

Interface Definition Java Microsoft IDL CORBA IDL WSDL IDL/XMI/WSDL WSDLMeta Language XML XML XML/XMI XML MOF/XML XMLRPC Mechanism RMI DCOM IIOP SOAP; XMLP SOAP; IIOP SOAPRegistry/Repository JNDI; LDAP LDAP; ADSI I/F Repository UDDI MOF;UDDI UDDIProcess Flow Proprietary Proprietary Proprietary ebXML; WSFL UML XLANGModeling Language UML UML UML UML UML UML

Page 6: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 6

Solving the Integration ProblemSolving the Integration ProblemWhat is needed?What is needed?

■ Short Answer is XML and HTTP!■ Slightly longer answer is SOAP, WSDL, UDDI■ Even longer answer is SOAP, WSDL, UDDI, WSFL, ebXML,

XAML, ACML, PIPs…■ The real answer is

– Things are a lot messier – We need to think and build software like engineers and architects– All these acronyms are great, but where is the process, methodology

and architecture!– We need to integrate the systems we have with the newer technologies– We need to rethink ‘Integration Platform’ & ‘Systems Integration

Platform’!– etc.

Page 7: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 7

Solving the Integration ProblemSolving the Integration ProblemWhat is needed?What is needed?

■ Methodology for building, evolving and integrating software across the life cycle

■ A mechanism for cataloging, indexing and searching enterprise assets (metadata and data, internal and external)

■ A flexible service based distributed component architecture that spans the enterprise

■ A set of shared standard vocabularies (information models) and notation (meaning and context of data usage)

■ A metadata driven approach to automate integration between islands of information

■ A set of open modeling, metadata and distributed computing standards■ Infrastructure products and applications that address these concerns; The

domain expertise needed to use these products and apply it to a customers situation ---> Unisys Global Industries Technology Roadmap

Page 8: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 8

The Enterprise Application Life CycleThe Enterprise Application Life CycleArchitecture Centric, Business driven,

Complex Life Cycle, Many Tools

And do this with quality in a distributed environment

Discovery and Transformation

BusinessRequirem

ents Modeling

Modeling Architecture,

Object, Data…

AddBusiness

Logic

Build /Wrap Components

Assemble& Test

Components

Configure &Deploy

Components

Models, Metadata, Mappings, Middleware

Manage

Components

ComponentRuntimes

(EJB, COM+)

Acquired

Components

Rapid

Rigorous

Page 9: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 9

Unisys ‘GITA’ Development Unisys ‘GITA’ Development Framework (The case for MDA!)Framework (The case for MDA!)

Business,Componentand Data Modeling

Business,Componentand Data Modeling

Visual IDE

& Legacy Wrapping

Visual IDE

& Legacy Wrapping

.NET or J2EEGeneration &Deployment

.NET or J2EEGeneration &Deployment

.NETor

J2EE Framework

.NETor

J2EE Framework

ComponentManagementComponent

Management

ClearCase DeveloperPortal

XMLXMLUMLUML

J2EEJ2EE

.NET.NET

CWMCWMVCSVCS

MOF/XMIMOF/XMI

Metadata, Models,Components,

code...TraceabilityLinks &

Transformations

XMI

WebGainWebGain

VS.NETVS.NET

The Key is Forward & Backward Traceability – From Components to Requirements and Business Vision

GITA : Unisys Global Industries Technology Architecture

The Key is Forward & Backward Traceability – From Components to Requirements and Business Vision

GITA : Unisys Global Industries Technology Architecture

RationalRequisitePro

Rational Rose

WebLogicWebLogic

.NET .NET SvrSvr Rational ClearCase

Page 10: Model Driven Architecture (MDA): Motivations, Status & Future

An Overview of OMG Model Driven An Overview of OMG Model Driven ArchitectureArchitecture

A vision that uses and integrates the 4M’s - Models, Metadata, Mapping and Middleware of software.

MDA allows developers and users to productively design, build, integrate and manage applications throughout the lifecycle irrespective of hardware or middleware platform

Page 11: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 11

OMG HistoryOMG History■ 800+ Vendors and End User members■ 1989 OMA Vision & Architecture■ 1991 CORBA 1.0■ 1995 CORBA 2.0 IIOP - CORBA Interoperability■ 1997 UML and MOF adopted, Domain specs

begin to be adopted■ 1999 XMI (XML Metadata Interchange) adopted■ 2000 CWM, XML/Value, EAI, EDOC, XMI for

XML Schema, Additional domain specs begin■ 2001 UML for EDOC, EAI, UML 2.0, MOF 2.0■ 2001 OMG reinvents itself using MDA

Page 12: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 12

OMG Analysis & Design OMG Analysis & Design Platform Task Force PremisePlatform Task Force Premise

■ The use of Modeling and Metadata enabled architectures allows us to manage the complexity of software development, application integration and data warehouse management

■ Modeling and Metadata standards are necessary for interchange of software artifacts and interoperability between tools, applications, middleware and data stores across platforms

The unification of the original OMG vision of OMA for distributed object interoperabilitywith this ADTF premise gave birth to MDA

Page 13: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 13

Solution for Managing Complexity : Solution for Managing Complexity : MDA: Model Driven Architecture MDA: Model Driven Architecture

■ An eclectic integration of best practices in Modeling , Middleware, Metadata, Internet and Software Architecture

■ Model Driven (UML, MOF, CWM…)– Platform Independent Models (PIM)– Platform Specific Models (PSM)– Mappings : PIM <==> PSM– Applies across the software life cycle

■ Key Benefits– Improved Productivity for Architects,

Designers, Developers and Administrators– Lower cost of Application Development

and Management– Enhanced Portability and Interoperability– Business Models and Technologies evolve

at own pace on platform(s) of choice

Page 14: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 14

Mapping Platform Independent Mapping Platform Independent Models to Specific PlatformsModels to Specific Platforms

PIM Software

InfrastructurePSMJ2EE

PIMHealthCare BusinessApplication (CIAS)

UML

UML

.J2EE

PIM to PSMTransformation

Model

.NET

PSM.Net

UML.Net

UML4J2EE

Page 15: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 15

OMG MDA OMG MDA -- Details Details

Middleware Platforms

E-BusinessApplication

Development

E-BusinessIntelligence,E.I. Portals

Information Models, Metadata Formats

E-BusinessApplicationIntegration

Community & Enterprise Knowledge Portals

HealthCare Financial Manufacturing Insurance...

Mappings to PlatformsSPECIFIC

APLATFORM

AGNOSTIC

Page 16: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 16

OMG MDA OMG MDA -- Specific Specific Models/Work in ProgressModels/Work in Progress

Middleware Platforms (.NET, CORBA, J2EE, SOAP…)

E-BusinessApplication

Development(UML, SPEMUML4EDOC)

E-BusinessIntelligence,E.I. Portals

(CWM)

Information Models, Metadata (UML, MOF, XMI, XML...)

E-BusinessApplicationIntegration(UML4EAI)

Community & Enterprise Knowledge Portals (KM)

HealthCare Financial Manufacturing Insurance...

Mappings to Platforms (UML4EDOC, UML4EJB, UML.NET*)SPECIFIC

APLATFORM

AGNOSTIC

* Opportunity

Page 17: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 17

OMG Model Driven ArchitectureOMG Model Driven ArchitectureMDA for Enterprise IntegrationMDA for Enterprise Integration

Model Driven App Development

Model DrivenApp Integration

Business Components

Vertical Industry Applications

MetaDataManagement

Business ProcessIntegration

Integration for

EDOCUML4EDOC*(PSM)

UML4EAI*(PSM)2001

EJBUML4EJB* (PSM)

2001

CORBAUML4CORBA(PSM)

2000

UMLModel & Design (PIM)

1997

PIM : Platform Independent ModelPSM : Platform Specific Model *Coming

Page 18: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 18

Early examples of MDAEarly examples of MDA■ OMG has been using MDA principles for about 3 years in

several specifications■ Metadata and Object Interchange/Integration

– UML and MOF for modeling, MOF and XMI for metadata integration– MOF is a subset of UML (Class diagrams) used to model metadata

■ Application Development – UML for modeling, XMI and IDL for tool integration and interchange– UML profile CORBA : UML for modeling, IDL for Integration

■ Data Warehousing – UML and CWM for Modeling, XMI and IDL for Warehouse

integration

■ Application Integration– UML profile for Enterprise Application Integration (UML4EAI),

Distributed Object Computing (EDOC)

Page 19: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 19

OMG Model Driven ArchitectureOMG Model Driven ArchitectureMDA for Metadata IntegrationMDA for Metadata Integration

Model Driven App Development

B2B Application Integration

Data Warehousing

Vertical Industry SpecificationsUML

Model & Design (PIM)

XMIMOF2XML (PSM)

DTD, DocumentSchema (XMI 2.0)

JMIMOF2Java(PSM)

IDLMOF2IDL (PSM)

MetaDataManagement

And So On

Framework(PIM)

Metadata for

1999

20011997

1997

PIM : Platform Independent ModelPSM : Platform Specific Model *Opportunity UML2C#

Page 20: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 20

XML Streams (Models)(Many - based on each metamodel DTD)

XML DTD (MetaModels) (1 per metamodel used for validation)

CWMDTD

UMLDTD

TravelDTD

Transform UML models to DTDTransform UML models to DTDXMI 1.1 :XMI 1.1 : ad/99ad/99--1010--02, ad/9902, ad/99--1010--0303

XMLSyntax and Encoding

MOFMetadata Definitions

& Management

XMI

UMLModel

Analysis & Design

UMLUML

Models UMLCWMModels UML

TravelDocuments

Validate

PSM

PIMMOFTO

DTD,XML

Page 21: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 21

<Auto> <Color>red</Color> <Door>2</Door></Auto>

Design-driven XMI for a car

<element name="Auto" /><!ELEMENT Auto (Color*, Door*)>

DoorColor

Auto

Objects and Designs

XMI Document

XMI DTD, Schema

<Class> <Name>Auto</Name></Class>

Model in XMI

Model Interchange

Instance Interchange

Page 22: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 22

XML Streams (Models)(Many - based on each metamodel Schema)

XML Schema(MetaModels) (1 per metamodel used for validation)

CWMXSD

UMLXSD

TravelXSD

Transform Models to SchemasTransform Models to SchemasXMI 2.0 OMG Document :XMI 2.0 OMG Document : ad/01ad/01--0606--12,1312,13

XMLSyntax and Encoding

MOFMetadata Definitions

& Management

XMI

2.0MOF2XSDUML

Model Analysis & Design

UMLUML

Models UMLCWMModels UML

TravelDocuments

Validate

PSM

PIM

Page 23: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 23

XMI Production of XML XMI Production of XML Schemas : OMG Vote next weekSchemas : OMG Vote next week

■ Bi-directional mappings from UML/MOF to XML Documents and XML Schema

■ Formal metamodels for XML Schema and XML■ Reverse engineering of XML DTDs to assist

transformation to schemas and UML■ Integrate the Analysis and Design of XML

applications to be better integrated with the web services platform

■ Accelerates tool integration and new methods for modeling web services

Page 24: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 24

Java Model Servers(Many - based on each metamodel Schema)

Java Packages (1 per metamodel used for validation)

CWMJAR

UMLJAR

TravelJAR

Transform Models to JavaTransform Models to JavaJMI 1.0 Draft : JMI 1.0 Draft : http://http://jcpjcp.org/.org/jsrjsr/detail/40./detail/40.jspjsp..

JavaSyntax and Encoding

MOFMetadata Definitions

& Management

JMI

1.0MOF2JavaUML

Model Analysis & Design

UMLUML

Models UMLCWMModels UML

TravelObjects

Validate

PSM

PIM

Page 25: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 25

Quick Lessons LearnedQuick Lessons Learned

■ Platforms and protocols come and go– Some become ubiquitous over time; most don’t

■ Just in the pace of 2 years DTD mania has become XML Schema mania! { YML and ZML are next!)

■ We used MDA to map UML/MOF to IDL and XML DTDs■ We used MDA to map UML/MOF to XML Schema■ We used MDA to map UML/MOF to EJB/Java respectively■ We even reverse mapped XML DTD and Documents to UML■ So design your models in UML and transform to DTD, XML

Schema, Java, C#, IDL.. Etc. ■ Use well defined, standard design patterns to save time

Page 26: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 26

OMG MDA Technologies OMG MDA Technologies

UML MOF

CWMUMLCWMCCM

EAIEC

UMLCWMCCM

EAIEC

MOF CWMCCM

EvaluatingCORBA Med

UML

EJB Java UML Profile forEDOC...

IDLUML4CORBA

Submissions

Standards

Life Sciences

ElectronicCommerce

Manufacturing

Enterprise App Integration

DocumentManagement Etc.

SPE

CIAS

Page 27: Model Driven Architecture (MDA): Motivations, Status & Future

Integrating MDA and Integrating MDA and Web Services ArchitectureWeb Services Architecture

We finally apply the MDA principles - Modeling the Web Services Architecture (and its components) so we

can formally define web service models with rich semantics (remember the ‘semantic web’) so we can

manage the full application life cycle for .NET applications.

P.S : We do the same for the next ‘fad’ or ‘real platform’

Page 28: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 28

How to apply MDA principles to How to apply MDA principles to Web ServicesWeb Services

■ Of course we start by modeling the various parts of the web services architecture

■ The key components of the architecture to model are – XML itself– UDDI– WSDL– Transformations from UML/MOF to these technologies

■ These models of models are called ‘Metamodels’ in OMG parlance

■ Having these metamodels and transformation models assists semantic integration of applications and data

Page 29: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 29

Mapping Platform Independent Mapping Platform Independent Models to Specific PlatformsModels to Specific Platforms

PIM Service Registry

Model

PSMWSA - WSDL

PIMService Definition

Model

UML

UML

OMA

PIM to PSMTransformation

Model

WSA

PSMWSA - UDDI

UML4UDDI

UML4WSDL

WSA: Web Services ArchitectureOMA: Object Management ArchitectureIR: Interface Repository

PSMOMA - IR

UML4CORBA

Page 30: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 30

Metamodels of XML and XML Metamodels of XML and XML Schema itselfSchema itself

■ XML and XML Schema Model– Defined in the OMG XML Production for XML Schemas

proposal– OMG Document # : ad/01-06-12,13– A complete MOF model using UML notation of XML and

XML Schema is available– Forward and reverse mappings from UML/MOF to XML

and XML Schema have been specified

■ Goal is to over time unify multiple schema models such as XML Schema, XMI, RDF etc using MOF

■ See also UML profile for XML at xmlmodeling.com

Page 31: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 31

Fragment of XML Schema Fragment of XML Schema ModelModel

Page 32: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 32

Metamodel of UDDIMetamodel of UDDI

■ Formally defining a metamodel for UDDI will make it more easy to integrate the structure and semantics of other directories and registries

■ An alternative approach is to define a generic interface (JAXR - Java API for XML Registries) -but this is not likely to capture the richer semantics in models

■ Models of UDDI are being developed at IBM, Unisys and Microsoft (among other vendors)

Page 33: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 33

Metamodel of UDDI Metamodel of UDDI -- SubsetSubset

BusinessService BusinessTemplate

BusinessContact

BusinessEntity0..*0..*

0.. *0.. *

IdentifierBag0..10..1

TModel

0..10..1

OverviewDocument

This is only a subset of the UDDI metamodel. A complete model will be in an upcoming OMG Proposal.

See xmlmodeling.com for a

Page 34: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 34

Metamodel of WSDL Metamodel of WSDL ■ Formally defining a metamodel for WSDL will make

it more easy to integrate the structure and semantics of other interface definition languages (IDL, Java…)

■ A formal model (MOF metamodel) of WSDL is being defined by IBM and Unisys for an OMG submission – The CWM Web Services RFP - so that it becomes easier to

integrate analytical web services with the rest of the database/data warehouse integration infrastrcucture

■ This model can be integrated with additional metamodels of Java and IDL that have already proposed in OMG specifications

Page 35: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 35

WSDL Metamodel FragmentWSDL Metamodel FragmentDocumentation

text : St ringWSDLElement

undef in ed : boo lean0..1

+eDocumentation

0..1

Extensib leElement

Message

PortType

Binding

Service

Types

Defini tion

0..*

+eMessages

0..*

0..*

+ePortTypes

0..*

0..*

+eBindings

0..*

0..*

+eServices

0..*

0..1+eTypes0..1

Import

0..*+eImports 0..*

Metamodel : Courtesy IBM

Page 36: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 36

How do we use these metamodels How do we use these metamodels of WSDL, UDDI and XML!of WSDL, UDDI and XML!

■ Within the OMG suite of metamodels, UML is the most well known and used to integrate application development and deployment tools

■ CWM - Common Warehouse Metamodel is more recent, but is a landmark model that addresses the integration requirement of various types of databases (network, relational, XML, multidimensional etc,)

■ The OMG is now in the process of integrating these suite of metamodels and the information they represent into the world of web services.

■ A quick peek at CWM will show us the way!

Page 37: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 37

OMG Common Warehouse OMG Common Warehouse Metamodel (CWM)Metamodel (CWM)

■ Scope– Data Warehouse lifecycle metadata interchange and

management

■ Initial submission : IBM, Unisys, NCR, Hyperion, Oracle, Genesis, UBS, Dimension EDI...– Metamodel - Single logical & physical!– Generated XML DTDs– Generated MOF - IDL mappings– Generated XML document

■ Approved by OMG Board in June 2000■ Endorsed by Meta Data Coalition in October 2000■ CWM 1.1 Revision is being now worked on

Page 38: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 38

CWM Package ArchitectureCWM Package Architecture

Modular Design– Minimum dependencies

• Cross package services provided by links to UML

– Avoid subpackages– Reduced complexity, improved

understanding– Use only the packages you

need

org.omgObjectModelCWM

Foundation<<metamodel>> DataTypes<<metamodel>> TypeMapping<<metamodel>> KeysIndexes<<metamodel>> Expressions<<metamodel>> BusinessInformation<<metamodel>> SoftwareDeployment

Resource<<metamodel>> Relational<<metamodel>> Record<<metamodel>> Multidimensional<<metamodel>> XML

Analysis<<metamodel>> Transformation<<metamodel>> Olap<<metamodel>> BusinessNomenclature<<metamodel>> DataMining<<metamodel>> InformationVisualization

Management<<metamodel>> WarehouseProcess<<metamodel>> WarehouseOperation

CWMX

Page 39: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 39

MDA for Data Warehouse MDA for Data Warehouse Integration using CWMIntegration using CWM

Page 40: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 40

What next for CWM : CWM Web What next for CWM : CWM Web ServicesServices

■ CWM is now being used by IBM, Unisys, Hyperion, Oracle, and many others for integrating enterprise data, metadata and content

■ However this interchange even though it uses XML (CWM is XMI compliant and uses XML for its interchange) has the following problems– The interchange patterns are too fine grained– The interchange patterns need to be formalized between

the integration partners– The interchange protocol does not support web services

■ To address these needs OMG is standardizing ‘CWM for Web Services’

Page 41: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 41

CWM Web Services RFP CWM Web Services RFP ■ Requires Integration of

– CWM Metamodel– XMI - The XML DTDs and Schemas that conform to

CWM– WSDL– SOAP– UDDI

■ A key principle of OMG MDA is define formal models (platform independent and platform specific) of these technologies and their transformations

■ The suite of metamodels and transformations being proposed will integrate MDA and Web Services

Page 42: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 42

CWM Web Services RFP CWM Web Services RFP --A Potential SolutionA Potential Solution

■ The specific interchange patterns model will be specified using UML and MOF and this metadata interchanged using XMI

■ Mappings from UML/MOF to WSDL and UDDI will make it possible to – Design web services applications and components using

UML– Manage all related metadata using MOF/XMI and XML– Automatically publish the interfaces/service definitions in

CORBA IR, UDDI registry and JNDI/LDAP servers!– Maintain traceability across the life cycle (try this today!)

Please note that the final adopted proposal may be different - Too early to tell!

Page 43: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 43

MDA meets Web Services bringing MDA meets Web Services bringing some order to the web services Chaos!some order to the web services Chaos!

PIM Service Registry

Model

PSMWSA - WSDL

PIMService Definition

Model

UML

UM

L

OMA

PIM to PSMTransformation

Model

WSA

PSMWSA - UDDI

UML4UDDI

UML4WSDL

WSA: Web Services ArchitectureOMA: Object Management ArchitectureADSI: Active Directory Services Interface

PSM.NET -ADSI

MOF.NET

UML 1.4App Design

UML

UM

L PSMDIR - LDAP

MOF.LDAP

Page 44: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 44

OMG MDA : What is Coming?OMG MDA : What is Coming?

XMI MOF

XML

UMLUMLCWM

CCMEAI

EC

UMLCWMCCM

EAIEC

MOF CWMCCM

EvaluatingCORBA Med

UML

EJB Java UML Profile forEDOC...

IDLUML4CORBA

Submissions

Standards

Life Sciences

ElectronicCommerce

WSDL

UML Profile for EAI

WorkFlow Etc.SPEMCIAS

ActionSemantics

UML2

UML Profile for EJB - JSR 26

UDDI

MOF 2.0

JMI - JSR-40

Page 45: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 45

What about UML 2.0?What about UML 2.0?■ Massive industry interest (30+ LOIs)■ ‘Gang of 17’ proposal

– Unisys/IBM/Rational/Oracle/Telelogic et al [Show model?]

■ Kinetium/Adaptive et al proposal■ 4 others■ Expect

– A radical restructuring of UML/MOF kernel– Better support for component architectures– Much better extensibility– Delays and some surprises!– Much better next generation tools!

■ MOF 2.0 coming on the heels■ UML/MOF/XMI/JMI will power the MDA platform

Page 46: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 46

Concluding ThoughtsConcluding Thoughts■ Ensuring a unified model and metadata driven architecture

is key to solving the heterogeneous integration problem– Use models and metadata to enable transformation– Use MDA principles through out the life cycle– OMG MDA is the realization of this vision

■ Most customers have and will continue to have components/services and information/data from multiple sources and formats that need integration

■ Integration problem continues to be complex and challenging– Use MDA principles to abstract complex models, map these

models to platforms and interchange artifacts across life cycle

■ Mapping MDA to .NET and J2EE frameworks will make the developers and systems integrators work easier– We handle the next platform even more easily!

Page 47: Model Driven Architecture (MDA): Motivations, Status & Future

Copyright 2001, UNISYS Corporation Slide 47

For More InformationFor More Information

■ OMG : www.omg.org, www.omg.org/cwm■ MDA : www.omg.org/mda■ Unisys : www.unisys.com■ UML : www.omg.org/uml, www.rational.com■ CWM : www.cwmforum.org, www.omg.org/uml■ W3C : www.w3c.org■ DSTC : www.dstc.edu.au■ Sridhar : [email protected]■ UML RTF : [email protected]■ MOF RTF : [email protected]■ XMI RTF : [email protected]■ CWM RTF : [email protected]■ JMI : http://java.sun.com/aboutJava/communityprocess/jsr