(C) IBM Corporation – June 2005 IBM Software Group ® Model Driven Architecture (MDA) meets Service Oriented Architecture (SOA) – Without Making a Loud Bang Dr. Donald Ferguson IBM Fellow, SWG Chief Architect Chair, IBM Software Group Architecture Board OMG TC Meeting Keynote
23
Embed
Dr. Donald Ferguson IBM Fellow, SWG Chief Architect Chair, IBM Software Group Architecture Board
Model Driven Architecture (MDA) meets Service Oriented Architecture (SOA) – Without Making a Loud Bang. Dr. Donald Ferguson IBM Fellow, SWG Chief Architect Chair, IBM Software Group Architecture Board OMG TC Meeting Keynote. ∞. Disclaimer Chief Architect and Timeframe. IBM Fellow. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
(C) IBM Corporation – June 2005
IBM Software Group
®
Model Driven Architecture (MDA) meets Service Oriented Architecture (SOA) – Without Making a Loud Bang
Dr. Donald FergusonIBM Fellow, SWG Chief ArchitectChair, IBM Software Group Architecture Board
• a set of services that a business wants to expose to their customers and partners, or other portions of the organization
• an architectural style which requires a service provider, requestor and a service description
• a set of architectural principles, patterns and criteria which address characteristics such as modularity, encapsulation, loose coupling, separation of concerns, reuse, composability
• a programming model complete with standards, tools and technologies such as Web Services
SOA Defining Concepts Universal Connectivity: Integrates most diverse environments, bridging protocols, languages, platforms, APIs and messaging paradigms – providing scale and scope of integration required by today’s extended enterprise
Service Orientation:
Facilitates loose coupling between
software components
Incremental Integration: Start small and plug in
capability to enrich your implementation as needs
dictate
Open, standards-based: Open APIs and protocols support the interoperability and substitution of middleware from multiple vendors
Event Orientation: Decouples applications that publish business
Transformation Steps…Apply Transformation Logic(drag to Schema editor, BO Editor
or BPEL Editor)Compute and persist mappingRegister notification listener to
map.
EMFModels
ExecutedMaps
End-to-end tool flow; Replace Word and PPT for collaboration betweenbusiness professionals, IT programmers and systems admins.
Pattern Solution
Pattern A
Pattern B Pattern
C
Pattern D
Describes how to knit many patterns together, as a
recipe, to solve larger-grained problems
Describes a solution to a recurring problem
Solution Descriptions
Pattern A
Industry Solution Template: RFID Checkout
Service A
Asset
Param
Asset
ParamBldg Block
DAsset
Param
Bldg Block C
Asset
Param
Asset
Param
Component B
Asset
Param
Industry Solution Template: Payment
MessagesService A
Asset
Param
Asset
ParamBldg Block
DAsset
Param
Bldg Block C
Asset
Param
Asset
Param
Component B
Asset
Param
Solution Extensions
Implement pattern solutions using templates, where assets/artifacts
have parameters
Solution Template
Service A
Asset
Param
Asset
ParamBldg Block
DAsset
Param
Bldg Block C
Asset
Param
Asset
Param
Component B
Asset
Param
Solution Implementations There are no new apps. Mature platforms have the “old guy.” Rich body of written best practices Move from “read the book” to a tool Support industry sols.
Patterns may be implemented as process guidance or may be codified within tooling
The solution described by a pattern may be implemented in a component, or across several components, or in a service. There are various codifications of patterns.
recognizes & documents
+
creates(later)
uses
customizes an asset
The codified pattern may be further customized by less skilled users.
• Configurable Component: parameterized software component implementing one or more patterns; may be published as a service
• RSA Transform, Pattern: implements a pattern through actions which modify model elements and other artifacts
• Template: contains sections marked for substitution with parameters supplied by the user
•Business Process Definition Metamodel (BPDM)•Web Services Business Process Execution Language (WSBPEL)•Business Process Modeling Notation (BPMN)•Business Rules (BSBR, PRR, BRM)
Challenges• Domain/Vertical support in “SOA”• Need to improve the “mapping” between SOA and UML• Modeling IT infrastructure, Security, etc.• End-to-End Policy and Rules• Seamless hand-off from development tools to systems management products• Application development IT Management “meta-model and process”