1. SOA: Candidate Focus for AIC for 2006 SOA Concepts and Technologies being Exploited by Many Target Architecture: Reference Models of 2002 need to be updated!

2. Summary Chart of TRM Review  PDF/PDFA = Approve (Later cycle should Investigate with More Thorough Analysis of Content Management, e.g., other formats such as TIFF, use cases, relationship to Records Mgmt Profile)  - X3D Graphics = Approve  Satellite Network Communications = Investigate with More Thorough Analysis  - Eliminate Platform Dependent/Independent in Service Platform and Component Framework = Approve  Reorganize data related items into a Data Management Area = Investigate with More Thorough Analysis  Additional SOA/XML/Web Services Standards need to be added= Investigate with More Thorough Analysis

3. Data Management – New Area in TRM Database Design (See spreadsheet for details)  Database and Metadata Design Tools Database Connectivity and Interchange (See spreadsheet for details)  Data Exchange  SQL Connectors Operational Database Systems (See spreadsheet for details)  Relational DBMS  Legacy and Pre-relational DBMS  Information Retrieval for Unstructured or Semi-Structured Data  Data Quality, ETL, and Data Profiling  Data Reporting and OLAP Tools  Other Operating DBMSs and Data Stores

4. SOA Fit with AIC  Governance: Business Governance, Service Governance and Project Governance –What are the key Service Elements that have to be defined in a consistent manner for Interoperability, Information and Data Sharing, Identity Management and other key cross-government concerns? –What are governance best practices and how to create Service Taxonomy, make Core.gov the service sharing and collaborative environment?  Components- Service Component Paper- needs to address many of the elements –Define existing shared service candidates  Emerging Technology- what is the maturity of SOA technologies, standards, and areas where industry is working and not working. How can we leverage ongoing standards initiatives and focus others on key government gaps?

5. What are going on in the different key government initiatives?  DHS- Shared Services and Architecture- relate to Transformation efforts  FHA- SOA oriented elements Medicaid, FDA, National Health Information Network and Electronic Health Record with Service Interfaces, CDC/NEDSS, etc  DOD- BMMP, NCES, DISA efforts….all moving toward SOA- relate to Transformation efforts  EPA- Environment Information Network/CDX  Justice Network  FAA- TFM/M  Etc…..

6. Steps 1. Define a Service Life Cycle 2. Review and Extend OASIS SOA RM and recommend updates to BRM, PRM, SRM, TRM, DRM, Security and Privacy Profile….etc 3. Map to SOA/Web Services Standards efforts and gather information with Core.gov and et.gov of usage and products and compatibility and maturity issues 4. Focus on key concern areas: Interoperability, Data Sharing, Reuse, Service Sharing, Service Quality and Management, Security and Privacy of Services……and share “government point of view with industry and standards organizations”…….market will respond government is a big player and Standards First- tell us your objectives and expectations can work. 5. Capture Success and Lessons Learned from the many adopters

7. Service Offering Life Cycle: TRM Has to be aligned with Some Service Offering approach such as this! Source: Global Information Grid, Core Enterprise Services, Draft, version 1.1a, dated July 9, 2003

8. Core Enterprise Services: Needs to be reviewed!  Collaboration Services  Storage Services  Discovery Services  Messaging Services  User Assistant Services  Enterprise Service Management Services  Information Assurance and Security Services  Mediation Services  Application Services Leverage Core.gov and et.gov…….

9. Components of Enterprise Architecture: Standards First Approach Description (WSDL, XSD) Registration Discovery (UDDI) Transport (SOAP/ HTTP) Events & Messaging (JMS WS-*) Data Lifecycle Mgmt BP Simulation Analysis Monitoring and Mgmt Service Orchestra tion Metadata Mgmt Security (SAML WS-Sec) Event Correlation Advanced SOA (Services Mgmt) Enterprise Architecture (Events + Services) Event Modeling Event Analysis Event Mgmt Reliability Availability Scalability Basic SOA (Services) Predictive Modeling Predictive Analytics Service Oriented Architecture (SOA) Elements Need to be defined in consistent manner Link to SOA RM: OASIS showing Phased Approach Many organizations are defining their Target Architecture with SOA elements that are not in the TRM

10. The Reference Model for SOA …  Is not intended to be architecture for a single SOA system.  Is an ABSTRACT model for a range of Service Oriented architectures and analysis / comparison thereof.  Is a framework for understanding significant relationships among the entities in a SOA environment.  Is based on a small number of unifying concepts of all SOA ’ s.

11. How does a RM relate to other stuff?

12. So what is SOA exactly?  A paradigm for organizing and using distributed capabilities that may be under the control of different ownership domains.  A framework for matching needs and capabilities.  A view of architecture focusing on “Services” as a mechanism to allows interactions between those with needs and capabilities.

13. Core Model for SOA Dynamic perspective: 3 base concepts for interacting with services: the visibility between service and consumers; the interaction between them, and real world effect of interacting with a service.

14. Additional Service concepts

15. Core Concepts for SOA - expanded

16. Core Concepts of SOA (Definitions)  Service: A mechanism by which needs and capabilities are brought together.  Service Description: Artifact declaring all relevant aspects of a service required to interact with the service.  Capability: an ability to perform a specific set of functions resulting in a real world effect.  Visability: The capacity for those with needs and those with capabilities to see each other and interact.

17. Core Concepts of SOA (DRAFT)  Execution Context: Set of technical/business elements that form path between those with needs and capabilities. Permits information to be exchanged, actions to be performed and provides a decision point for any policies and contracts that may be in force.  Policy: A set/range of constraints imposed on any entity when invoking a service. If ignored, the invocation request may be denied.

18. Core Concepts of SOA (DRAFT)  Exchange: The act whereby two or more entities come together within the context of a single interaction.  Real World Effect: The result of an interaction with a service.  Interchange: the activity of using the capability. An “act” rather than an “object”

19. Concepts around Visibility

20. Interaction with Service

21. Real World Effect – shared state

22. Service Description

23. Service Capabilities Service Consumers Where do things live? Core SOA Business Process, State alignment, orchestration, choreography, etc.. Applications, ECM, DB, … In a layer diagram, layer “n” is only visible to layers (n +1) and (n – 1) VisibleVisible Not visible What services are used for Sources, functionality for capabilities

24. BPM is a layer over SOA. Data Server Service Server Courtesy Booz Allen Hamilton – http://www.bah.comhttp://www.bah.com Business & Application Tier Service Oriented Tier Business Process Acquisition Business Process Human Resources Business Process Grants Management Business Process Customer Service Business Process Budgeting and Forecasting Process & Orchestration Tier Service

25. Processes can be in front of OR behind services  Processes aggregate multiple services and can themselves be exposed as services.  Since services hide the resources behind them, not all details of the process may be available.

26. Existing situation in Web Services WSDL XML & Schema SOAP Base Standards WS-RM WS Addressing Reg/Rep UDDI WS-Security WS-Trust WS-* Requirements Question: How do I account for my requirements and organize components when building a concrete architecture?

27. Thoughts on developing specific SOA’s  Probably not logical to try and develop a “one size, fits all” architecture for SOA or WS.  Not rational to develop multiple architectures in standards bodies for every set of requirements.  Best solution: develop an SOA reference Model. –Used by architects to guide development of specific service oriented architectures. –Model for a “way of thinking” when architecting. –Re-useable by multiple architects writing SOA for multiple domains. –Helps architects slot existing standards into their architectures.

28. SOA RM used for range of service oriented architectures WSDL XML & Schema SOAP Base Standards WS-RM WS Addressing Foo UDDI WS-Security WS-Trust WS-* Requirements Guides developments of SOA-RM Specific Architectures Uses Input for

29. Components of an Enterprise SOA Infrastructure Service Container for Coding All-New Services J2EE,.Net, Axis, SAP, Systinet, webMethods Fabric Containers host services and provide basic infrastructure (such as a SOAP stack, and network connectivity) Service Container for Wrapped Services and Assembled Composite Services BusinessWorks, TIBCO Runtime Agent Same as above, but these containers focus on wrapping legacy services and assembled composite services. Service NetworkTIBCO EMS, BusinessWorks Blue Titan, Sonic, Fiorano, CapeClear The Network or Bus is the intermediary that provides location independence, protocol bridging, transport QoS, simple transformation, and content based routing Service Registry (UDDI) Windows 2003, IBM, Systinet, Infravio, UDDI, ebXML Registries are were you go to search for services that you can reuse or to advertise your service to others Assure Vendor Independence with Options: Sample of what needs to be done with Further Investigation

30. Components of an Enterprise SOA Infrastructure Web Service SecurityTIBCO Policy Server Actional,Layer 7 Web Service Security (WSS) adds a protective layer around otherwise un-secure Services Management of Web Services (MOWS) TIBCO Policy Server Amberpoint, Actional Web Service Management (WSM) adds a monitoring & control layer around otherwise un-managed Services Enterprise Metadata Management TIBCO XML Metadata Repository Metamatrix Meta Data Repositories are were you store XML assets for versioning, validation, dependency checking, and change management MOF and XML Recommend that companies place information into et.gov & government industry team classify and make full recommendation of periodic basis

31. Closing Thoughts… THANK YOU!!!!! (Moving Forward…..IAC can support further Reference Model Maintenance Activities)

32. References  OASIS SOA RM TC - http://www.oasis- open.org/committees/tc_home.php?w g_abbrev=soa-rm http://www.oasis- open.org/committees/tc_home.php?w g_abbrev=soa-rm  Thank you – Duane Nickull, dnickull@adobe.com dnickull@adobe.com