1. Copyright © 2008 Model Driven Solutions. Standards for Service Architectures SOA for e-Government Conference Cory Casanave cory-c (at) modeldriven.com May 2008 A division of Data Access Technologies, Inc.

2. Page 2Copyright © 2008 Model Driven Solutions Topics Object Management Group (OMG) Modeling Standard Efforts for SOA SOA and Model Driven Architecture (MDA) Overview of SOA-Pro by Example Tie to Web Services – Executable Architectures Model Driven Solutions

3. Page 3Copyright © 2008 Model Driven Solutions Who Are OMG? Adaptive BEA Borland Boeing CA Citigroup Compuware DaimlerChrysler Data Access EDS Everware Fujitsu GSA Harris Hewlett Packard Hitachi IBM io Software Kennedy Carter Kaiser Permanente klocwork Metamatrix Model Driven Solutios NASA NEC NIST NTT DoCoMo Northrop Grumman OASIS Oracle PRISM Sandpiper SAP Satyam Select Sun TCS Unisys Visa W3C

4. Page 4Copyright © 2008 Model Driven Solutions OMGs Mission Since 1989 Develop an architecture, using appropriate technology, for modeling & distributed application integration, guaranteeing: –reusability of components –interoperability & portability –basis in commercially available software Specifications freely available Implementations exist Member-controlled not-for-profit See more at: www.OMG.org

5. Page 5Copyright © 2008 Model Driven Solutions What is Model Driven Architecture? A Better Way to Specify and Design & Develop –Based on modeling standards like UML, MOF –Is extensible to all modeling problems –Supports full lifecycle: analysis, design, implementation, deployment, maintenance, evolution & integration with later systems –Builds in Interoperability and Portability –Lowers initial cost and maximizes ROI –MDA Models are Executable and Actionable

6. Page 6Copyright © 2008 Model Driven Solutions OMG Modeling Standards OMG is the première standards organization for architecture and modeling. Some OMG Specification Examples: –Model Driven Architecture (MDA) –Unified Modeling Language (UML) –Business Process Modeling Notation (BPMN) –Systems Modeling Language (SysML) –Meta-Object Facility for Metadata Management (MOF) –Enterprise Distributed Object Computing (EDOC) –Common Object Request Broker (Corba) –Semantics of Business Vocabulary and Rules (SBVR) –Business Motivation Model (BMM) –Records Management (RM) –Air Traffic Control –Federal Transition Framework (FTF)

7. Page 7Copyright © 2008 Model Driven Solutions Current SOA Related Standards Unified Modeling Language (UML-2) –Provides basis for modeling, but little specific to SOA. Out of the box it is hard to know how to use UML for SOA or business modeling and has no support for mapping to web services Enterprise Distributed Object Computing (EDOC) –Encompasses many SOA concepts but pre-dates SOA and UML-2 – concepts are being merged into newer standards Business Process Definition Metamodel (BPDM) –Pure meta model for BPM and some SOA concepts – SOA part does not have a diagram standard people can readily use – this is being addressed in BPMN-2 Conclusion – Current modeling standards do not sufficiently address SOA

8. Page 8Copyright © 2008 Model Driven Solutions SOA-Pro & UPMS This presentation is largely a preview of SOA-Pro, the proposed standard expected to come out of the current UPMS processes. The UML Profile and Metamodel for Services (UPMS) standards process in in the final stages – adoption can be expected well within this year. The discussions are largely over – all the submitters have merged on a common approach and are now working on the final document. Submitting team: –88Solutions, Adaptive, Azora, BAE, CapGemini, EDS, –France Telecom, Everware, GSA, Hewlett Packard, Inherit, –Mega International, Model Driven Solutions, Syntef, –TALES Group, Telelogic An early version of SOA-Pro is already in use within the government – in the GSAs Financial Management Architecture.

9. Page 9Copyright © 2008 Model Driven Solutions What you can expect out of SOA-Pro A UML Profile which specifies how to use UML for SOA and tailors UML tools for SOA modeling A UML Metamodel – which will provide a standard XML exchange format for service architectures Separation of concerns between the business systems and technology architectures – executable SOA specifications A (non normative) mapping to Web Services – so that Web Service specifications can be generated from a services architecture and Web Services can be reverse engineered into an architecture. SOA-Pro will support a variety of SOA methodologies and technology architectures. Commercial and Open Source Tools can then be built for Web services, Java, Corba,.NET, etc. SOA-Pro works both Top Down and Bottom Up.

10. Page 10Copyright © 2008 Model Driven Solutions Architecture - the in SOA Architecture is done at two levels in SOA –The technology architecture – service distribution, message structures, wire protocols, registries, encryption, etc. –The domain (Business/Mission/Systems of Systems) architecture – service definition, responsibilities and how services work together to meet business needs. Our focus today is the domain architecture – what we call the architecture of services. The specification of services and how services work together for a purpose – to support business goals and processes. Technology architectures are encompassed in many exiting standards and products, this should be reusable across domains. Model Driven Architecture (MDA) provides mechanisms for mapping the domain architecture to the technology architecture of choice. Separation of these concerns is vital!

11. Page 11Copyright © 2008 Model Driven Solutions SOA as a Business and Technology Concept Business Services –Business Services connect people, organizations and systems as a network of services. A business entity is understood in terms of the services it offers and consumes – the supply chain. –The business process shows how the business entity achieves its goals, using and supplying services. Technology Services –Technology services connect systems in well defined ways to facilitate both business services and the technology infrastructure. –Technology services should mirror and facilitate the business services and should support business processes A primary goal of SOA-Pro is to connect the dots between the business and technology viewpoints SOA can help a top down and bottom up approach meet in the middle through services.

12. Page 12Copyright © 2008 Model Driven Solutions The enterprise as services Think about the enterprise as a set of interacting roles providing and using services to enable agility, cost savings and an effective transition framework Externally –The enterprise is part of the global supply chain, providing services to customers and using the services of suppliers Internally –Consider parts of the enterprise as providing services to other parts of the enterprise, and in term using the service of others –Like everything was outsourced as a service, it just happens to be done inside the organization. Business is modeled in terms of interacting roles – providing and using services – the essential concepts of enterprise SOA

13. Page 13Copyright © 2008 Model Driven Solutions Business Concerns Goals Policy Customers Costs Agility Technology Specification JMS, JEE, Web Services WSDL, BPEL, XML Schema Technology Specification JMS, JEE, Web Services WSDL, BPEL, XML Schema Logical System Model Technology Services (t-SOA), Components Interfaces, Messages & Data Logical System Model Technology Services (t-SOA), Components Interfaces, Messages & Data Business Focused SOA Using Model Driven Architecture Business Model Enterprise Services (e-SOA) Roles, Collaborations & Interactions Process & Information Business Model Enterprise Services (e-SOA) Roles, Collaborations & Interactions Process & Information Refinement & Automation Line-Of-Sight Computation Independent Model Platform Independent Model Platform Specific Model MDA Terms

14. Page 14Copyright © 2008 Model Driven Solutions Value derived from the architecture Component Acquisition Specification Technology Interfaces Test & Simulation OMB 300 FEA/FTF BRM SRM DRM* Business Driven Technology Facilitating Business Processes Adapters Components DataDeployment

15. Page 15Copyright © 2008 Model Driven Solutions Incorporating Legacy Analysis

16. Copyright © 2008 Model Driven Solutions. SOA Profile by Example Using UML for Services Architectures with the SOA Profile Note: Some of the examples are somewhat out of date with the current proposed standard, but the differences are minor.

17. Page 17Copyright © 2008 Model Driven Solutions Example use case Enable a marketplace of dealers and manufacturers with a services architecture. There are many dealers and manufactures that form a community. Each dealer may deal with many manufactures and each manufacturer can deal with many dealers. Each may use the services of many shippers. We want a way for dealers and manufactures to work together but not get overly coupled to each other. Each organization should be independent and agile. Each organization may have its own business processes and systems. Our job is to enable this community with a Service Oriented Architecture Principles: –Participants proprietary systems should be hidden behind services –Supplying and using services according to the architecture is the way an organization participates in the community –The growing set of services should support long-lived and multi-party services –All relationships are peer-peer, there is no controller – the challenge is then reliable interoperability and collaborative behavior within this loosely coupled community –Services should be specified independently from any technology or organizational structure

18. Page 18Copyright © 2008 Model Driven Solutions SOA Marketplace Community Mechanics Are Us Dealer Acme Industries Manufacturer GetItThere Freight Shipper Order Conformation Ship Req Shipped Physical Delivery Delivered Status

19. Page 19Copyright © 2008 Model Driven Solutions Marketplace Services Mechanics Are Us Dealer Acme Industries Manufacturer GetItThere Freight Shipper Order Conformation Ship Req Shipped Physical Delivery Delivered Status Provider Consumer Provider Consumer Provider

20. Page 20Copyright © 2008 Model Driven Solutions Community Architecture for the dealer network

21. Page 21Copyright © 2008 Model Driven Solutions Focus on the middle Service Contract Service Contract Service Contract

22. Page 22Copyright © 2008 Model Driven Solutions Similar Example From Financial Management Service representing delegated responsibility for interaction with an external participant. Service representing interaction with another participant within Financial Management. Roles of participants inside of finance

23. Page 23Copyright © 2008 Model Driven Solutions Similar Example From Financial Management

24. Page 24Copyright © 2008 Model Driven Solutions Simple Service Contract A Service Contract represents the terms and conditions by which a service is provided and consumed. The Service Contract is the specification of the middle – a collaboration between the provider and consumer. The service contract specifies the roles each party plays, the interfaces they offer and the behavior of enacting the service. The service contract is binding on those participating in the service The service interface types, which are the types of the roles, define the interaction points (service ports) for providing and using services. The service contract can scale up to choreographed and nested asynchronous interactions over an extended time period – which is the norm for business services. Multi- party contracts are easily supported The service contract (collaboration and service interfaces) are a unit – a single specification of a service without regard for implementation or dependencies. Collaborative View Systems Interface View

25. Page 25Copyright © 2008 Model Driven Solutions [Web] Services Implement the Services Architecture Mechanics Are Us Dealer Acme Industries Manufacturer GetItThere Freight Shipper Order Conformation Ship Req Shipped Physical Delivery Delivered Status Web Service Web Service Web Service Web Service Web Service

26. Page 26Copyright © 2008 Model Driven Solutions A bi-directional service contract Collaborative View Systems Interface View May include conditions

27. Page 27Copyright © 2008 Model Driven Solutions Choreography for bi-directional service contract Choreography View Data

28. Page 28Copyright © 2008 Model Driven Solutions Compound Service Contract Composition reduces complexity while providing for arbitrarily complex service contracts Any participant can initiate any sub-service Can be built top down or bottom up

29. Page 29Copyright © 2008 Model Driven Solutions Compound Service Contract Interface View Each role binding implies a port On the roles type Interface can be mapping to a technology, such as WSDL or Corba

30. Page 30Copyright © 2008 Model Driven Solutions A Services Architecture (SOA) shows how Participants Provide and Use Services for a Common Purpose. Service Contract is USED here.

31. Page 31Copyright © 2008 Model Driven Solutions Participants Participants can play roles in multiple community architectures, defining their external requirements. Each service contract they are bound to must interact through a compatible port. Participant

32. Page 32Copyright © 2008 Model Driven Solutions Inside the Manufacturer Order Conformation Shipped Ship Req Shipped Delivered Order ProcessingShipping Production Event Web Service Web Service Web Service Web Service Web Service Web Service Web Service Web Service

33. Page 33Copyright © 2008 Model Driven Solutions Inside the manufacturer, Participant Architecture

34. Page 34Copyright © 2008 Model Driven Solutions There was an existing Productions service that we can reuse Imported From an Existing Web Service

35. Page 35Copyright © 2008 Model Driven Solutions Completed Service Component Architecture for Order Processing

36. Page 36Copyright © 2008 Model Driven Solutions Business Concerns Technology Architecture Technology Specification JEE, JMS, Web Services WSDL, BPEL, XML Schema Logical System Model Technology Services (t-SOA), Components Interfaces, Messages & Data Business Model Business Services (b-SOA) Roles, Collaborations & Interactions Process & Information

37. Page 37Copyright © 2008 Model Driven Solutions Example Web Services Generation <wsdl:input message="tns:BillSubmissionCluster name=billSubmission"> <wsdl:input message="tns:BillDeliveredCluster name=billDelivered"> <wsdl:input message="tns:BillReturnedCluster name=billReturned">

38. Page 38Copyright © 2008 Model Driven Solutions Example Transaction Message XML Document … … … … … … … … … … … …

39. Page 39Copyright © 2008 Model Driven Solutions Mapping to Web Services

40. Page 40Copyright © 2008 Model Driven Solutions Mapping to Web Services public class Asset_Record_Establishment_ProviderAsset_Record_Establishment_Provider_InterfaceInternal { …… static public Document establish_asset_record(Document request) throws CheckedException { … // for an inbound operation, determine if we delegate or execute return gov.gsa.fmea.Asset_Record_Establishment_Transaction_Manager. Asset_Record_Establishment_ProviderAsset_Record_Establishment_Provider_InterfaceInternal. establish_asset_record(request); public class Asset_Record_Establishment_ProviderAsset_Record_Establishment_Provider_InterfaceInternal{ … static public Document establish_asset_record(Document request) throws CheckedException { … // for an inbound operation, determine if we delegate or execute return ServiceFactory.getPipeline("Asset_Record_Establishment_Transaction_Manager. Asset_Record_Establishment_Provider.establish_asset_record.Pipeline").execute(request); }

41. Page 41Copyright © 2008 Model Driven Solutions Mapping to Web Services Asset_Project_Status_Notification_Transaction_Manager.Asset_Project_Status_Notification_Provider.notify_asset_project_status..xslt … … Asset_Project_Status_Notification_Transaction_Manager.Asset_Completion_Establishment_Consumer.establish_asset_completion..xslt … <xsl:function name="mdf:Asset_Project_Status_Notification_Transaction_Manager.Asset_Completion_Establishment_Consumer.establish_asset_completion.UsageOut" as="node() ?"> <xsl:with-param name="namespace" select="'http://www.modeldriven.org/xsd/FMEA_Asset_Accounting_Implementation_Model.uml/Asset_Completion_Establishment_Message_Elements'"/> …

42. Page 42Copyright © 2008 Model Driven Solutions Information model to XML Schema ABC123 Vienna VA … ABC123 Vienna VA … <Organization__Schema identity=http://ocfo.gsa.gov/fmea/organization/1> true … <Organization__Schema identity=http://ocfo.gsa.gov/fmea/organization/1> true …

43. Page 43Copyright © 2008 Model Driven Solutions Conclusion SOA-Pro takes SOA to the next level, embracing the full life- cycle of business, systems of systems and technology services. Having industry standards for SOA at the architecture level will help make the transition to SOA easier and provide a better link to business requirements and SOA governance Modeling above the technology makes a SOA more approachable for our business stakeholders and able to withstand technology change. The combination of SOA-Pro with Web Services provides for a comprehensive System of Systems approach

44. Page 44Copyright © 2008 Model Driven Solutions Model Driven Solutions Full Life-Cycle Executable Architectures –Enterprise Architecture –Model Driven Architecture –Service Oriented Architecture –Business Architecture –System of Systems Architecture –Systems & Solutions Architecture –Business Process Architecture –Federal Enterprise Architecture –Semantic Web Model Driven SOA Implementation Open Source Tools & Infrastructure SOA Transformations for a more effective Enterpise