Creating your roadmap to soa integration


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Page from Colt 45 US patent filing from February 25,1836
  • Creating your roadmap to soa integration

    1. 1. Creating Your Roadmap for SOA IntegrationGreg KirkendallFusion517/08/2010<br />The most comprehensive Oracle applications & technology content under one roof<br />
    2. 2. What are we trying to achieve?<br />
    3. 3. Reduction!<br />Reduction of Complexity<br />Reduction in Time to Market<br />Reduction of the Cost of Change<br />Reduction of Duplicated Effort<br />Reduction of Information Silos<br />
    4. 4. Promises, Promises…<br />Lots of technologies and methodologies have promised to deliver one or all of the “reductions”.<br />As a result, standards bodies and professional organizations have been formed to create standards.<br />
    5. 5. Important SOA Standards Bodies<br />TOGAF 9 – Architecture Methodology<br />FEA – Reference Architecture, Complexity Reduction Techniques<br />OASIS – SOA Standards, XML Document Standards<br />OMG – UML, BPMN, XMI, CORBA<br />Industry specific standards exist as well<br />
    6. 6. Where to Begin?<br />Executive Sponsorship<br />SOA projects usually cross departments<br />Gather business requirements<br />Select an Architecture Methodology<br />Zachman, TOGAF, FEA, Gartner<br />May use components from more than one<br />
    7. 7. Create a Vision<br />Agree on business goals and requirements<br />Gap analysis<br />Establish architecture vision<br />Establish the value proposition<br />Establish scope<br />
    8. 8. Create the Architectures<br />Business Architecture<br />As Is and To Be with roadmap<br />Application Architecture<br />Identify current systems and create roadmap for target <br />Data Architecture<br />Establish source(s) of truth, replication requirements<br />Technical Architecture<br />Software, hardware and networking<br />
    9. 9. Establish Governance<br />Ensures alignment to architecture<br />Creates a framework for reuse<br />Manages and enforces run time SLAs<br />Security policy management & enforcement<br />Lifecycle management<br />
    10. 10. No Programs Written, Yet<br />By establishing strategy, vision and reference architectures first, a blueprint is created for all implementation project work to use as guidance<br />Governance ensures that the architecture is being followed, SLAs are being met, policies enforced and ensures visibility of your enterprise assets<br />
    11. 11. Idea to Action<br />Use your roadmap to determine the pilot project<br />Use your swim lanes to identify integration points, services, applications and systems involved<br />
    12. 12. Create Swim Lanes for Business Processes<br />
    13. 13. Detailed Business Processes<br />Create detailed business processes<br />Identify gaps (automation required, business process change, compliance risks)<br />Identify existing interfaces<br />Indentify new interfaces<br />
    14. 14. Midlevel Web Services Breakdown<br />Identify existing and “to be” web services<br />Cross-reference with swim lanes/business processes<br />
    15. 15. Canonical Analysis and Creation<br />Canonicals are simply model documents like invoices and purchase orders that contain all possible fields that could appear.<br />Universal Business Language (UBL) can be used as a starting point (OASIS)<br />Oracle AIA Foundation Pack has 140+<br />EDI Documents can be used as a starting point as well<br />Design others as needed<br />
    16. 16. Enterprise Service Design<br />Use the reference architecture, canonicals and identified web services as the basis for the design.<br />There are several types and “layers” of services<br />Create the service contracts<br />
    17. 17. Reporting, Monitoring and Security<br />All SOA-related reporting and monitoring should be identified and specified<br />Should include business and technical control panel<br />Security roles and users should be established<br />
    18. 18. Detailed Design<br />Intended for technical audience implementing specifications<br />Includes all services and XML documents<br />Product-specific modifications also identified, if needed<br />Security and monitoring policies specified as well<br />Will need to be reviewed for compliance with reference architectures<br />
    19. 19. Implement!<br />Need promotion policies in place, usually different from existing non-SOA promotions.<br />Load testing is important, use the initial load as a stress test, if possible<br />
    20. 20. Links<br />TOGAF 9 -<br />FEA -<br />OASIS -<br />UBL -<br />OMG -<br />Oracle AIA Foundation Packs -<br />Fusion5 –<br />
    21. 21. Tell us what you think…<br /><br />