1. OMG - EDOC Bringing together business goals, standards, processes and technologies for the e-enabled enterprise Enterprise Distributed Object Computing

2. Copyright © 2001, Data Access Technologies, Inc. Integrating Enterprises, People & Systems - Worldwide Using Internet Technologies Enabling e

3. Copyright © 2001, Data Access Technologies, Inc. Integrating Enterprises, People & Systems - Worldwide zBusiness Requirements yVirtual Enterprises yEnterprise Integration (EAI) ySupply-chain automation (B2B) yCustomer Integration (B2B) yWeb deployment (B2C) yInternet Marketplace (B2C) zCollaboration and Integration

4. Copyright © 2001, Data Access Technologies, Inc. The dynamic reality zThe information system must facilitate; yRapid realization of business goals yIntegration of independent processes and systems yMultiple and Changing xbusiness requirements xbusiness processes xtechnologies xstandards xenterprise boundaries xpartners

5. The e-enabled enterprise Has a competitive advantage in its capability to embrace collaboration and change

6. Copyright © 2001, Data Access Technologies, Inc. Components Workflow Repositories Metadata OpenCollaborativeEnterprise Embracing collaboration and change Model Driven Architecture Shared Data EAI zWe need to extract the meat from the buzzwords zAnd figure out how these concepts fit together zTo e-enable the enterprise Web Services Middleware Messaging & Events

7. Copyright © 2001, Data Access Technologies, Inc. Business & Technology Coupling “Open B2B” Ad-hoc business “Community B2B” - Business Partners & Independent Divisions Integration within a managed domain Integration or production of an application Internet Computing Model ebXML Soap Events & Messaging JMS MQ-Series Synchronous Transactional RPC Corba EJB Shared Data SQL IMS-DB Collaborative Components EDOC Model (UML) Traditional EDI

8. The role of open systems in the enterprise Supporting open distributed computing while meeting local requirements

9. Copyright © 2001, Data Access Technologies, Inc. The Enterprise “The Enterprise” The “open domain” zIndependent domains collaborating via open standards zNo assumption of “the same thing” on both sides! zAppropriate inside and outside the enterprise (EI & B2B) zRequires business (process collaboration and information) and technical (middleware) standards zThe open domain needs a point of ownership in the enterprise Enterprise boundaries are not static!

10. Copyright © 2001, Data Access Technologies, Inc. The Internet Computing Model zCollaboration of independent entities zDocument exchange over internet technologies yLarge grain interactions zNo required infrastructure * zLong lived business processes zBusiness transactions Business Party Business Party Portals

11. Copyright © 2001, Data Access Technologies, Inc. Requirements for the “ICM” zContract of Collaboration yShared business semantics yMeta-Model (EDOC-ECA) and representation (I.E. XMI, ebXML-BPSS) yShared Repository for Contracts (MOF, UDDI, ebXML) zConnectivity (middleware) which meets requirements of the contract zImplementation 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

12. Copyright © 2001, Data Access Technologies, Inc. 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

13. Copyright © 2001, Data Access Technologies, Inc. Drilling down – inside a role zThe open domain should make no assumptions about the “inside” of a role. zInside one role you frequently find more collaborating “parts” of the enterprise - the same model may be used zUntil you get to system inside a managed domain yShared resources (DBMS) yCommon Management yFrequently a legacy system Inner Role Legacy Inner Role Inner Role Domain Cust

14. Copyright © 2001, Data Access Technologies, Inc. Collaborative Business Semantics zDefined: The processes, information and contracts of interaction between collaborators within a community zCollaborative business semantics are a valuable long- term asset zCaptures information and process zRequires ownership and support in the open domain zDo not put this valuable asset in a (transient - one size fits all) technology specific form yUse technology independent models (MDA) yMap to the technology of the day (E.G. DTD)

15. Copyright © 2001, Data Access Technologies, Inc. Required support for the open domain zConnectivity standards and infrastructure yProviding the enterprise “bus” (Intranet) yhttp, Soap, ebXML zCommon processes and lexicon yWhat goes on the bus - the real business value! yFacilitating communities of practice zMeta-model standards (UML, ebXML-BPSS, EDOC...) yHow to represent shared processes and information zRepositories yFinding services, models and components for design time and runtime integration

16. Standards for Global Internet Computing UML4EDOCUML4EDOC SOAP WSDL XML XML-Schema.NET BPML

17. Copyright © 2001, Data Access Technologies, Inc. XML Standards zXML Schema & DTD yDescription and packaging of data zSoap yBasic messaging and packaging yExtensions for Soap-RPC with WSDL yMay be extended to support collaborative messaging

18. Copyright © 2001, Data Access Technologies, Inc. Vision zEDOC (a UML Profile) yProvide an architecture for open collaborative computing ySimplify the development of component based distributed systems by means of a modelling framework, based on UML 1.4 yProvide a platform independent, recursive collaboration based modelling approach supporting multiple technologies. yEmbrace Model Driven Architectures (MDA) – Provide design and infrastructure models and mapping zebXML yCreating a single global electronic market xIncludes process specification, transport and repositories

19. Copyright © 2001, Data Access Technologies, Inc. ebXML & EDOC Transport Distribution Repository Runtime Enterprise Integration Components Information Model MDA Collaboration Process Model ebXML EDOC

20. Copyright © 2001, Data Access Technologies, Inc. Standards for collaboration EDOC-ECAebXML-BPSS Business CollaborationsYes – Community ProcessYes – Multi Party Collaboration Contract of InteractionYes – Protocol with Choreography & Object Interface Yes – Binary Collaboration with Choreography and Business Transactions Content ModelYes – Document ModelUses external forms, such as XML Schema Recursive CompositionYes – Recursive Composition into Enterprise No – Only “B2B” Detail sufficient to drive communications No – Requires technology mappingYes – As ebXML transport. BPSS includes timing and security parameters. Computing Models Supported Internet document exchange, entities, business processes, objects and events Internet document exchange

21. Copyright © 2001, Data Access Technologies, Inc. Parts of EDOC zEnterprise Collaboration Architecture (PIM) yComponent Collaboration Architecture yBusiness Process Specification yEntities yBusiness Events yPatterns zTechnology Mapping (PSM – in progress) yFlow Composition Model (Messaging) yEJB & Corba Components yebXML y.NET yOthers… zMAPPING – Precise models are are source code

22. Copyright © 2001, Data Access Technologies, Inc. XML Corba EJB.NET Events HTTP Web Server Applications Enterprise Architecture SQL DBMS, Client/Server & Legacy Applications Client Applications EAI Applications & B2B E-Commerce Web Browser Supply Chain Enterprise Components

23. Copyright © 2001, Data Access Technologies, Inc. Parts of ebXML zBusiness Process Specification (Like EDOC-CCA) yXML Representation of business process zCore Components yBusiness Data Types & documents based on context zCollaboration Protocol Profile yWhat business partners implement what business processes using what technologies yOne-One agreement for doing business zTransport Routing & Packaging yMessaging Built on Soap zRegistry & Repository yFinding business partners, document and process specifications

24. Copyright © 2001, Data Access Technologies, Inc. ebXML Architecture BP Specification Business Process Core Data Blocks Business Messages CPA Context ForBuilt With Implement one Partner Role Implement other Partner Roles Register Designtime CPP Transport Package Business Service Interface Internal Business App Business Service Interface Runtime

25. Copyright © 2001, Data Access Technologies, Inc. Summary of points thus far zWe must enable the emerging Internet Computing Model yLoosely coupled roles exchanging documents based on a contract of collaboration zWeb need interoperability at two levels yMessaging for the data yMetadata for the contract of collaboration, stored in repositories zThis model of collaborating roles is recursive, extending into the enterprise, into managed domains and into applications yInside the enterprise we want to include resources entities, business events and business processes zSupporting the open domain has some required parts and can be augmented with a “treasure chest” of tools and infrastructure zBetween EDOC & ebXML we are covering B2B and intra enterprise

26. EDOC Component Collaboration Architecture The model of collaborative work

27. Copyright © 2001, Data Access Technologies, Inc. The Marketplace Example Mechanics Are Us Buyer Acme Industries Seller GetItThere Freight Shipper Order Conformation Ship Req Shipped Physical Delivery Delivered Status Process Complete

28. Copyright © 2001, Data Access Technologies, Inc. The Seller’s Detail Order Conformation Shipped Ship Req Shipped Delivered Order ProcessingShipping Receivables Event

29. Copyright © 2001, Data Access Technologies, Inc. Parts of a CCA Specification zStructure of process components and protocols yProcess components, ports, protocols and documents xClass Diagram or CCA Notation zComposition of process components yHow components are used to specify components xCollaboration diagram or CCA Notation zChoreography yOrdering of flows and protocols in and between process components xActivity Diagram

30. Copyright © 2001, Data Access Technologies, Inc. The Community Process zIdentify a “community process”, the roles and interactions Protocol

31. Copyright © 2001, Data Access Technologies, Inc. Protocols

32. Copyright © 2001, Data Access Technologies, Inc. Composition

33. ECA Entity Profile The model of things Data Inside a “shared domain ”

34. Copyright © 2001, Data Access Technologies, Inc. Adding Entities zEntities are added to manage entity data zEntity Roles are managers that provides a view of the same identity in another context zThe Entities have ports for managing and accessing the entities zNon-entities which are owned by (aggregate into) an entity are managed by the entity

35. ECA Business Events The model of when… Loosely coupled integration within the enterprise and with “aligned” business partners

36. Copyright © 2001, Data Access Technologies, Inc. Business Process Business Entity Business Rules Business Events Business Actions Business Process Business Entity Business Rules Business Events Business Actions Event Based Business Processes Event Notification

37. Copyright © 2001, Data Access Technologies, Inc. App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions Point to point Event Notification Event Notifications

38. Copyright © 2001, Data Access Technologies, Inc. App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions App Business Process Business Entity Business Rules Business Events Business Actions Pub/Sub Pub/Sub Event Notification

39. Copyright © 2001, Data Access Technologies, Inc. Event Example

40. Vision Building and adapting systems for collaboration, reuse and change

41. Copyright © 2001, Data Access Technologies, Inc. Business Component Marketplace zThe business component marketplace is projected to be a 10b market in 5 years zConsider the value of XML components that wrap popular legacy zNew application functionality built from components zComponents for integration and transformation zXML and web services makes an excellent basis for such components zTechnology components, such as for repositories and DBMS zMarketplace my be inside the enterprise or commercial

42. Copyright © 2001, Data Access Technologies, Inc. OMG Model Driven Architecture (MDA) zHigh level – platform independent models zTechnology Models zMapping yCustom yStandard zStandard Models produce technology specific standards artifacts

43. Copyright © 2001, Data Access Technologies, Inc. Automated MDA Profile (E.G. EDOC) Framework & Infrastructure (E.G. XML) InfrastructureMapping Mapping is tuned to the infrastructure Tools Produce & Integrate EnterpriseComponents UMLDesign

44. Copyright © 2001, Data Access Technologies, Inc. Technology Independence Business Logic Component ebXml Business Logic Component BizTalk Business Logic Component RosetaNet Business Logic Component Ejb Adapters EJB Business Logic Component ebXml BizTalk Rosetanet Adapters CICS EJB MQ Corba

45. Copyright © 2001, Data Access Technologies, Inc. Iterative Development Build Release Build Deploy Business Model Design Infrastructure Development Automation

46. Copyright © 2001, Data Access Technologies, Inc. High level tooling & infrastructure zMUST BE SIMPLE! yWe must be able to create better applications faster yWe must separate the technology and business concerns, enable the user zTooling + Infrastructure yExecutable models are source code yTooling must be technology aware yInfrastructure must support tooling, not manual techniques zModel based component architectures

47. Copyright © 2001, Data Access Technologies, Inc. High level tooling & infrastructure zMUST BE SIMPLE! yWe must be able to create better applications faster yWe must separate the technology and business concerns, enable the user zTooling + Infrastructure yExecutable models are source code yaTooling must be technology aware yInfrastructure must support tooling zModel based component architectures Executable Models

48. Copyright © 2001, Data Access Technologies, Inc. Net effect zUsing these open standards and automated techniques we can; yAchieve the strategic advantage of an open and flexible enterpise yProduce and/or integrate these systems FASTER and CHEAPER than could be done with legacy techniques yProvide a lasting asset that will outlive the technology of the day

49. Copyright © 2001, Data Access Technologies, Inc. Typical Requirement B2B Buyer Web Service Seller Buyer Web Page HTML Seller

50. Copyright © 2001, Data Access Technologies, Inc. B2B Buyer Multi-tier implementation Buyer Web Page HTML Buyer Proxy Web Service Seller Could have multiple implementations using different technologies Could have multiple implementations using different technologies

51. Copyright © 2001, Data Access Technologies, Inc. Legacy Seller Applications Event Cloud B2B Buyer Multi-tier implementation Buyer Web Page HTML Buyer Proxy Web Service Seller Event Implementing seller using events

52. Model Driven Architecture Automating Design To execution

53. Copyright © 2001, Data Access Technologies, Inc. MDA Overview zUse high level UML models made precise with profiles zWith technology specific mappings zTo produce substantial parts of the executable system

54. Copyright © 2001, Data Access Technologies, Inc. Models and mapping zSpecification zImplementation zSolution Provisioning zBXS map Platform-specific artifacts (IDL/DTD) Platform Independent Model Versioned repository Business Model UML/CORBA UML/EJB XML OAG SOAP ebXml RosettaNet Legacy Management Over Time

55. Copyright © 2001, Data Access Technologies, Inc. Model to Deployed Artifacts Map source Automated platform-specific process object module application runtime compile package assemble deploy Supplier-Specific artifacts overrides Process control parameters Configure map Select Tools Locate Resources Platform-specific Process steps artifacts

56. Copyright © 2001, Data Access Technologies, Inc. Generated Artifacts Implementation Artifacts (EJB Examples) Java Source Class Objects Stubs, Skeletons, Helpers, Holders, Interfaces Jars,Wars,Ears BeanInfo,Editors.. Business Object Implementation Logic Homes, Managers, Primary Keys SQL Descriptors Documentation M0/M1 XMI/DTD Serialization, Persistence Management Artifact generation involves multiple tools EJB Container provider;Deployment tools;Packagers; java development tools(IDE);persistence provider;… Typical 10-20 per PIM Classifier 0-20% manual override

57. Copyright © 2001, Data Access Technologies, Inc. PIM Reverse Engineering model navigation process disposition algorithms Production rule engine Native artifacts Native meta-model is platform-specific XML DTD/Schema; java introspection; SQL tables; legacy model; etc. Map navigates the native meta-model, populates PIM Limited semantic recovery Information and middleware models work best

58. Copyright © 2001, Data Access Technologies, Inc. MDA and Components zSpecification zImplementation zSolution Provisioning zBXS Platform Independent Model Business Model Direct Execution Components

59. Summary of MDA benefits zIsolates domain specifications from platform details yReduces complexity yPreserves domain model semantics yIncreases stability and lifetime yGenerates to platform/legacy of choice  Decreased development time  fast iterative development  separation between the engineering and business requirements  Increased quality. zBuilds on industry directions DomainSpecifications MDA Users