Model Driven Architecture: The Evolution of ObjectOriented Systems Richard Mark Soley, Ph.D. Chairma

1
Model Driven ArchitectureThe Evolution of
Object-Oriented Systems?Richard Mark Soley,
Ph.D.Chairman and CEO
2
Remember Artificial Intelligence?

• Symbolics, Lisp Machines Inc., Intellicorp,
  Inference, Gold Hill Computers, Texas
  Instruments, Computer Thought, Neuron Data,
• Major success stories abounded
• American Express
• Dupont
• General Motors

3
Artificial Stupidity?

• After lots of hype, AI failed
• Nearly none are left, and none of the survivors
  are in the same business
• Some favorite follow-ons
• Object-oriented development tools
• Object-oriented databases
• Business rule systems
• CASE tools

4
An Instructive Path

• Neuron Data
• Blaze Software
• Fair, Isaac
• To survive, technology companies seem to move up
  the abstraction stack
• Marketing people know this
• They call it creation of a whole product
• Technologies do the same thing
• We call it compilation

5
How Can We Take the Next Step?

• So where should the OO technologies and the OO
  companies be headed?
• Up the abstraction ladder!
• What does OMG have to do with it?

6
OMGs Vision
The Global Information Appliance
7
Heterogeneity is Permanent

• Programming languages
• 3 million COBOL programmers
• 1.6 million VB programmers
• 1.1 million C/C programmers
• Operating systems
• Unix, MVS, VMS, MacOS, Windows (all 8!), PalmOS
• Windows 3.1 its still out there!
• Embedded devices (mobile, set-top, etc.)
• Networks
• Ethernet, ATM, IP, SS7, Firewire, USB
• Bluetooth, 802.11b, HomeRF

8
Where Can We Agree?

• There will not be consensus on hardware platforms
• There will not be consensus on operating systems
• There will not be consensus on network protocols
• There will not be consensus on programming
  languages
• There must be consensus on models, interfaces and
  interoperability!

9
OMGs Mission Since 1989

• Develop an architecture, using object technology,
  for distributed application integration,
  guaranteeing
• reusability of components
• interoperability portability
• basis in commercially available software
• Specifications freely available
• Implementations exist
• Member-controlled not-for-profit

10
Who Are OMG?
Alcatel ATT BEA Borland Boeing CA Codagen Daimler
Chrysler Ericsson France Telecom
Fujitsu Glaxo SmithKline Hewlett
Packard Hitachi Hyperion IBM IONA io
Software Kabira Kennedy Carter
John Deere LION Bioscience Metanology MITRE MSC.So
ftware NASA NEC Nokia NTT DoCoMo OASIS
Oracle Pfizer Rockwell SAP SAS Institute Sprint Su
n Telefonica Unisys Vitria
11
OMGs First Major Success

• Common Object Request Broker Architecture
• CORBA remains the only language- and
  platform-neutral interoperability standard
• Middleware itself has proliferated
• CORBA Vendor, OS language independent
  middleware
• COM/DCOM/MTS
• Java/EJB
• XML/SOAP Web Services
• C/.Net
• What will be Next Best Thing?

12
How Can We Protect Software Investment?

• The problem remains
• Tracking the next best thing
• Protecting your investment in existing software
  base
• Retaining qualified staff
• Maintaining existing code base
• Integrating what youve built
• With what you are building
• With what you will build!

13
The Model Driven Architecture

• OMGs Model Driven Architecture (MDATM)
  initiative is aimed precisely at this problem
• You have an opportunity to increase your bottom
  line by integrating your assets
• Industry standards support that goal by
  future-proofing your application design
• The MDA will help you integrate the mix you have
  today, and give you an architecture to support
  the unexpected
• Focus on integrating legacy applications
• Ensure smooth integration of COTS applications
• Models are testable and simulatable
• The aim a 20-year software architecture

14
What is Model Driven Architecture?

• A Way to Specify and Build Systems
• Based on modeling with UML
• Supports full lifecycle analysis, design,
  implementation, deployment, maintenance,
  evolution integration with later systems
• Builds in Interoperability and Portability
• Lowers initial cost and maximizes ROI
• Applies directly to the mix you face
• Programming language ? Network
• Operating system ? Middleware

15
OMGs Modeling Suite

• Unified Modeling Language
• UMLTM remains the worlds only standardized
  object-oriented modeling language, best-known
  part of the standard
• Common Warehouse Metamodel
• CWMTM, the integration of the last two data
  warehousing initiatives
• Meta-Object Facility
• MOFTM, the metadata integration standard
• Defines metadata metadata services
• XML Metadata Interchange
• XMITM, the XML-UML standard
• Cornerstone of UML tool interoperability
• Actually just a collection of mapping rules
  XML/MOF

16
OM Modeling Suite
MOF
XMI
UML
other
CWM
17
Model Driven Architecture
18
Leveraging UML is Critical

• The Unified Modeling Language is the successor to
  the dozens of OO AD notations of the early 90s.
• Result of an OMG adoption begun in 96 and
  completed in 97
• Complemented with repository (MOF) and XML
  Metadata specs (XMI)
• Standardization primed the market
• Over 100 books
• Dozens of commercial tools
• Widely available training
• Supported by an open process
• UML 2.0 process under way now

19
Building an MDA Application
Start with a Platform-Independent Model (PIM)
representing business functionality and behavior,
undistorted by technology details.
A Detailed Model, stating Pre- and
Post-Conditions in OCL, and Semantics in
Action Language
Platform-Independent Model
20
Generating Platform-Specific Model
Map a PIM to Specific Middleware Technologies via
OMG Standard Mappings
MDA tool applies a standard mapping to generate
Platform-Specific Model (PSM) from the PIM. Code
is partially automatic, partially hand-written.
Platform-Independent Model
21
Mapping to Multiple Deployment Technologies
MDA tool applies an standard mapping to generate
Platform-Specific Model (PSM) from the PIM. Code
is partially automatic, partially hand-written.
Map a PIM to Many Middleware Technologies via OMG
Standard Mappings
Platform-Independent Model
22
Generating Implementations
MDA Tool generates all or most of the
implementation code for deployment technology
selected by the developer.
Map PSM to application interfaces, code, GUI
descriptors, SQL queries, etc.
Platform-Independent Model
23
Integrating Legacy COTS
MDA Tools for reverse engineering automate
discovery of models for re-integration on new
platforms.
Reverse-engineer existing application into a
model and redeploy.
Platform-Independent Model
Legacy App
COTS App
24
Automating Bridges
Platform-Independent Model
Bridge generation is simplified by common
application models, simplifying creation of
integrated applications both within and across
enterprises.
MDA Tools combine application and platform
knowledge to generate bridges
XML/SOAPModel
CORBA Model
XML/SOAP System
25
Data Integration Works Too

• MOF is the key here, behind the UML scene
• With one modeling language
• Anything can be modeled
• User must map (code) from domain to modeling
  language constructs
• MOF enables definition of multiple modeling
  languages
• Specific to various domains
• Semantics captured in metamodels
• User no longer needs to map, tools do

26
Data Integration Choices
Meta-meta-model
Programming Language Type
Class
Attribute
Relational Database Model
Association
Object Database Model
Key
XML Schema
27
Data Integration Data Model
Meta-meta-model
Meta-model
Model
Data
Class
Built-in type
string
Attribute
name
Association
last_name
Derived type
Key
country
28
Data Integration Relational
Meta-meta-model
Meta-model
Model
Data
Class
table
order
cust
Attribute
cust_FK
column
Association
key
order_ID
Key
date
29
Data Integration Object
Meta-meta-model
Meta-model
Model
Data
Class
class
person
employee
Attribute
name
attribute
Association
social
Key
birthdate
30
Data Integration XML
Meta-meta-model
Meta-model
Model
Data
Class
tag
ltdocumentgt
Attribute
ltheadergt
data
ltfontgt
Association
attribute
ltsizegt
Key
ltbodygt
31
MDA in Industry Standards

• The MDA promotes standards that are valuable
  across deployment technologies
• Applicable to large small deployments, new
  applications, legacy and COTS
• Applicable to CORBA, DCOM, .Net, etc.
• Allows knowledge leverage for the long-term,
  standards that persist
• MDA has been quickly adopted by OMGs
  standardization groups
• Both PIM and PSM(s) adopted by process
• Standard model lasts decades

32
OMG MDA Adoption Status

• Major direction agreed March 01 overall
  architecture adopted September 01.
• UML 1.4 complete 2.0 in final edit.
• Large suite of standards already done
• Core UML, MOF, CWM, XMI
• Enterprise Models EDOC, EAI
• Platforms RT, CORBA, J2EE
• Platform soon WS, .NET

33
OMG MDA Adoption Status

• More importantly, vertical market groups are
  thriving on MDA approach
• Legacy Transformation
• Financial Services
• Healthcare
• Life Sciences Research
• Manufacturing
• Space Ground Systems
• Telecommunications

34
MDA in Practice

• Several excellent proofs-of-concept
• Wells Fargo (an architecture that has already
  been resilient through a decade of change)
• Lockheed Martin Aeronautics
• GCPR in US government
• Deutsche Bank Bauspar
• Defense Information Systems
• Merrill Lynch
• Österreichische Bundesbahn
• Thales Training Simulation
• Zuercher Kantonal Bank
• CGI
• Chubb and Son

35
Back to the Title

• We must move up the abstraction ladder
• To deal with multi-platform
• To simplify software development
• To better match the real world
• Should this be MDIS next year?

36
To Get More Information

• MDA Information Page
• http//www.omg.org/mda/
• OMG General Information
• http//www.omg.org/
• Contact the Author
• soley_at_omg.org
• http//www.omg.org/soley/oois03.ppt