This document provides guidance on creating a roadmap for service-oriented architecture (SOA) integration. It discusses establishing executive sponsorship, selecting an architecture methodology, creating visions and reference architectures, establishing governance, designing services, and implementing an initial pilot project. The goal is to reduce complexity, costs, duplication of effort, and information silos through standards-based SOA integration. Reference architectures are created first to provide guidance for implementation projects and ensure alignment with goals.

1. Creating Your Roadmap for SOA IntegrationGreg KirkendallFusion517/08/2010 The most comprehensive Oracle applications & technology content under one roof

2. What are we trying to achieve?

3. Reduction! Reduction of Complexity Reduction in Time to Market Reduction of the Cost of Change Reduction of Duplicated Effort Reduction of Information Silos

4. Promises, Promises… Lots of technologies and methodologies have promised to deliver one or all of the “reductions”. As a result, standards bodies and professional organizations have been formed to create standards.

5. Important SOA Standards Bodies TOGAF 9 – Architecture Methodology FEA – Reference Architecture, Complexity Reduction Techniques OASIS – SOA Standards, XML Document Standards OMG – UML, BPMN, XMI, CORBA Industry specific standards exist as well

6. Where to Begin? Executive Sponsorship SOA projects usually cross departments Gather business requirements Select an Architecture Methodology Zachman, TOGAF, FEA, Gartner May use components from more than one

7. Create a Vision Agree on business goals and requirements Gap analysis Establish architecture vision Establish the value proposition Establish scope

8. Create the Architectures Business Architecture As Is and To Be with roadmap Application Architecture Identify current systems and create roadmap for target Data Architecture Establish source(s) of truth, replication requirements Technical Architecture Software, hardware and networking

9. Establish Governance Ensures alignment to architecture Creates a framework for reuse Manages and enforces run time SLAs Security policy management & enforcement Lifecycle management

10. No Programs Written, Yet By establishing strategy, vision and reference architectures first, a blueprint is created for all implementation project work to use as guidance Governance ensures that the architecture is being followed, SLAs are being met, policies enforced and ensures visibility of your enterprise assets

11. Idea to Action Use your roadmap to determine the pilot project Use your swim lanes to identify integration points, services, applications and systems involved

12. Create Swim Lanes for Business Processes

13. Detailed Business Processes Create detailed business processes Identify gaps (automation required, business process change, compliance risks) Identify existing interfaces Indentify new interfaces

14. Midlevel Web Services Breakdown Identify existing and “to be” web services Cross-reference with swim lanes/business processes

15. Canonical Analysis and Creation Canonicals are simply model documents like invoices and purchase orders that contain all possible fields that could appear. Universal Business Language (UBL) can be used as a starting point (OASIS) Oracle AIA Foundation Pack has 140+ EDI Documents can be used as a starting point as well Design others as needed

16. Enterprise Service Design Use the reference architecture, canonicals and identified web services as the basis for the design. There are several types and “layers” of services Create the service contracts

17. Reporting, Monitoring and Security All SOA-related reporting and monitoring should be identified and specified Should include business and technical control panel Security roles and users should be established

18. Detailed Design Intended for technical audience implementing specifications Includes all services and XML documents Product-specific modifications also identified, if needed Security and monitoring policies specified as well Will need to be reviewed for compliance with reference architectures

19. Implement! Need promotion policies in place, usually different from existing non-SOA promotions. Load testing is important, use the initial load as a stress test, if possible

20. Links TOGAF 9 - http://www.opengroup.org/togaf/ FEA - http://www.whitehouse.gov/omb/e-gov/fea/ OASIS - http://www.oasis-open.org/home/index.php UBL - http://docs.oasis-open.org/ubl/os-UBL-2.0/UBL-2.0.html OMG - http://www.omg.org/ Oracle AIA Foundation Packs - http://www.oracle.com/us/products/applications/054252.html Fusion5 – http://www.fusion5.com.au/

21. Tell us what you think… http://feedback.insync10.com.au