MDA for Web Services. Applying Model Driven Architecture to

Click here to load reader

  • date post

  • Category


  • view

  • download


Embed Size (px)



Transcript of MDA for Web Services. Applying Model Driven Architecture to

  • 1. MDA for Web Services Applying Model Driven Architecture to Web Services Document webserv/2002-04-05 EDOC-ECA

2. Problem Space

  • Integration Nightmare
  • Infrastructure, Version & Vendor lock-in
  • Complex, divergent and manual development and deployment processes

3. Goals

  • A scalable and robust enterprise architecture
  • Loosely coupled enterprise components
  • Enable rapid provisioning of business solutions
    • Simple, reproducible processes supporting reuse
  • Technology & vendor independence
  • Enable the integration and collaboration of multiple;
    • Business units (internal and external)
    • Customers
    • Suppliers
    • Systems
    • Technologies

4. Solution Triad Service Based Architecture Standards Tooling & Infrastructure Development Process Components Web Services Corba OMG ECA J2EE .NET Model Driven Development 5. The new center

  • The strategic core of you systems must be the business itself
  • Onlytechnology independent business focused modelswill survive the transience of technology and lock-in
  • These models can becomepart of your source code , driving enterprise applications
  • Enabler: Model Driven Architecture (MDA) with EDOC-ECA

Extreme Modeling 6. Collaboration and Web Services Collaboration is the center of applying web services to core enterprise problems. 7. EDOC Enterprise Collaboration Architecture Provides the standard UML PIM profile suitable for enterprise application of web services EDOC 8. What is the Enterprise Collaboration Architecture?

  • ECA is a profile of UML, a way to use UML for a specific purpose - it is an OMG standard
    • That purpose ismodeling enterprise systems .
  • You can also think of this as a modeling framework for enterprise computing
  • ECA is part of the Model Driven Architecture (MDA) initiative of the OMG
    • Using precise modeling techniques as part of the development lifecycle to speed development and provide technology independence
  • ECA has been adopted by the OMG as part of the EDOC RFP.

9. Using MDA for WSDL WSDL & Soap Mapping PIM PSM Business Focused ECA Model 10. Collaboration is Key

  • Collaboration is a key differentiation and key cost center (Healthcare Example)
    • Customer Collaboration
    • Claim processing
    • Disputes
    • Physician Collaboration
    • Payer Collaboration
    • Hospital Collaboration
    • Broker Collaboration
    • Government Collaboration
    • Employee Collaboration
    • Others...

The systemintegrates multiple collaborations 11. Automated Model Driven Architecture Profile (E.G. EDOC) Framework & Infrastructure (E.G. Web Services) Infrastructure Mapping (E.G. Web Services) Mapping is tuned to the infrastructure Tools Produce & Integrate Enterprise Components Business Focused Model (UML) Manual Coding Minimize and structure manual implementation 12. Loose Coupling

  • Loose coupling is the ability for independent parts of systems to be built and evolve independently
  • Tightly coupled systems
    • Prevent change (the next legacy system)
    • Cause lock-in
    • Become unmanageable
    • Prevent reuse
  • Quality architecture is essential for loose coupling

13. Enterprise Components

  • Enterprise Components must be independent
  • While being able to interoperate with each other
  • Making the information system a lattice of cooperating components

Open Standards Open Standards Open Standards 14. Poor Monolithic Architecture Traditional data sources SQL DBMS & Client/Server Bad Thing All business rules, data rules,application logic, technology and userinterface code are contained here The data goes here Monolithic Applications Monolithic Applications HTTP Web Browser Making a monolithic web application doesnt help! 15. Enterprise Architecture HTTP Web Server Applications SQL DBMS, Client/Server& LegacyApplications Client Applications Business and data rules go here User interface and application logic go here The datagoes here EAI Applications & B2B E-Commerce Web Browser Standard Middleware connects applicationsto components &components tocomponents XML Corba EJB DCOM MQ Supply Chain Enterprise Components 16. Technology Independence What the infrastructure vendors would have you do Business Logic Component ebXml Business Logic Component .NET Business Logic Component RosetaNet Business Logic Component Ejb Adapters EJB Business Logic Component ebXml BizTalk Rosetanet Adapters CICS EJB MQ Corba 17. Typical Requirement Buyer Web Page HTML Seller Redundant Work! B2B Buyer Web Service Seller 18. Multi-tier implementation B2B Buyer Web Service Seller Could have multiple implementations using different technologies Could have multiple implementations using different technologies Buyer Web Page HTML Buyer Proxy 19. Multi-tier implementation Legacy Seller Applications Event Cloud B2B Buyer Web Service Seller Event Event Implementing seller using events Buyer Web Page HTML Buyer Proxy 20. Understanding Collaborations 21. The Connected Enterprise Content and Communication Police Dispatcher Role Aerial Photos Digital Map Census Data House Drawings Police Records 22. Multiple roles in a collaboration 23. Roles to Systems ImplementationNet Hardware Operating System Framework, Middleware & Container Interaction Path Component in Role Interaction (With Information) RoleCollaboration 24. The Internet Computing Model The technology model behind WSDL and ebXML and others 25. The Internet Computing Model

  • Collaboration of independent entities
  • Document exchange over internet technologies
    • Large grain interactions
  • No shared infrastructure required *
  • Long lived business processes
  • Business transactions

Business Party Business Party Portals 26. Requirements for the ICM

  • Contract of Collaboration
    • Shared business semantics
    • Meta-Model (EDOC-ECA) and representation (I.E. XMI, ebXML-BPSS)
    • Shared Repository for Contracts (MOF, UDDI, ebXML)
  • Connectivity (middleware) which meets requirements of the contract
  • Implementation of each contract role providing connectivity (application server)

Business Partner Business Partner Repository Contracts (Metadata) Contract of collaboration can be mapped to the format of various technologies. (ebXML, Soap, .NET) Instance Data 27. Two levels of interoperability Instance data and interoperability Metadata (contract) interoperability Business Partner Business Partner Bridge Each can be transformed Purchasing Model .NET ebXML BPSS ebXML Biztalk Normal Form Over Soap Over Soap 28. Drilling down inside a role

  • The open domain should make no assumptions about the inside of a role.
  • Inside one role youfrequentlyfind more collaborating parts of the enterprise - the same modelmaybe used
  • Until you get to system inside a managed domain
    • Shared resources (DBMS)
    • Common Management
    • Frequently a legacy system

Inner Role Legacy Inner Role Inner Role Domain Cust 29. Collaborative Business Semantics

  • Defined: The processes, information and contracts of interaction between collaborators within a community
  • Collaborative business semantics are avaluable long-term asset
  • Capturesinformationandprocess
  • Requiresownership and support
  • Do notput this valuable asset in a (transient - one size fits all)technology specificform
    • Usetechnology independent models(MDA)
    • Mapto the technology of the day (E.G. DTD)

30. Generic web services

  • Generic web services is any set of technologies that can implement the internet computing model.
  • WSDL, ebXML, .NET

31. Standards for GlobalInternet Computing EDOC SOAP WSDL XML XML-Schema .NET BPML XLANG 32. XML Standards

  • XML Schema & DTD
    • Description and packaging of data
  • WSDL
    • Specification a services, operations and flows available via that service
  • Soap
    • Basic messaging and packaging
    • Extensions for Soap-RPC with WSDL
    • May be extended to support collaborative messaging