The document outlines 5 things to avoid when creating a service-oriented architecture (SOA): 1) Using the wrong people for the job and not ensuring those working on it have the proper skills and understanding of SOA. 2) Selecting technologies too early before properly analyzing requirements and testing options. 3) Not properly considering service design principles and how services should be designed. 4) Not fully understanding and factoring in business needs and how the SOA will improve key business processes. 5) Not planning and designing for the long-term and strategically how the SOA can evolve over time with the business.

1. 5 Things to Avoid When Creating Your SOA David S. Linthicum, Managing Partner, ZapThink, LLC November , 2007 Building a Foundation for Continuous Change

2. Current Issues Competing frameworks/approaches Zachman Framework Gartner/Meta Group Open Group’s TOGAF (SOA Reference Architecture) Vendors (IBM, Oracle, BEA, etc.) Roll-your-own Hype-driven confusion (e.g., “SOA 2.0”) Lack of leadership Processes moving outside of the firewall Departments operating independent of oversight More enterprise applications are Web-delivered Technology as a business advantage and cost saving mechanism

3. Business Constant: Change CHANGE Competition Changing Marketplace Customer Demands Mergers & Acquisitions Optimizing Processes New Technologies Business Partners A Business is Never STATIC

4. We’ve had IT challenges for years …

5. … but even after yesterday’s promises…

6. … we still have the same IT mess, only worse. Copyright © 2007, ZapThink, LLC

7. The Business Inflexibility Trap Inflexibility is the Mother of All Business Problems If you’re flexible enough, you can solve all the other problems Information Technology (IT) is an impediment to business change It wasn’t supposed to be that way!

8. Companies require Business Agility… Responding quickly to change, and Leveraging change for competitive advantage Business Agility J Agility is the key to innovation

9. The Problems of IT are The Problems of Business

10. If you are in a Hole, Stop Digging! IT Decision Making’s Fatal Flaw: Choice between “take some extra time & money and do it right” vs. “give me what I want the cheapest & fastest way” – guess which wins? Repeat enough times, leads to the IT “Rat’s Nest”

11. The Integration “Rat’s Nest” FBT PAY G NTS TRDS Client Customs RRE IPS Integrated A/C Refunds RBA Def Payments Excise CR PKI ECI ADD AWA ELS Client Staff Remote Staff TAX AGENTS GCI Call Centers WOC CCD TASS Staff Phone Compliance Staff BOA Ref material Bus. Intel NTS A/c BEP CDCC CWMS BANK DDDR 1 Data……. Penalty Business IVR 1

12. 5 Things to Avoid Using the wrong people. Selecting the technology too early. Not considering “service design.” Not factoring in the business. Not thinking long term, and strategic.

13. Using the Wrong People Perhaps this is something you should not outsource. This is architecture, not development. This is strategic, not tactical. Existing talent may not be up to speed. You may love your current team, but perhaps they are not up for the job. Make the cuts now, not later. Don’t let consultants or vendors drive the project.

14. Selecting the Technology too Early Don’t “manage by magazine.” Don’t overuse “comfort vendors.” Avoid VDA (vendor driven architecture) Business -> Requirements -> Analysis -> Technology. Now repeat! Make sure to do a POC, and other testing. Never be afraid to toss out technology.

15. Not Considering “Service Design” Services are not applications. Services are not APIs. Services are services, and should be designed properly. Consider granularity. Consider repeatable design. Consider testing.

16. Not Factoring in the Business Always do ROI analysis before you begin work on your SOA. Understand core business processes, and what needs to improve. Understand core business drivers, and be able to sell them within the organization. Make sure business analysts have input at various stages.

17. Not Thinking Long Term, and Strategic SOA has a positive impact after years, not months. SOA is not a development project, it’s a journey. SOA requires a systemic change in how you do architecture, it’s not just an instance of an architecture. SOA requires long term corporate commitment to be successful.

18. Understand your business objectives and define success. ROI Define ROI Create Business Case Business Case

19. Define your problem domain System Descriptions System Complexity Analysis SOA POC POC Results Domain Descriptions Vendors

20. Understand all application semantics in your domain. SOA Metadata Meta data analysis Data abstraction layer definition Data Abstraction Layer Data services definition Data Services Legacy Metadata External Metadata (B2B)

21. Understand all services in your domain. Candidate Services Service analysis Metadata and services analysis Services And Information Performance analysis Services And Performance Legacy Services External Services (B2B) SOA Metadata

22. Copyright 2007 The Linthicum Group, LLC Understand all processes in your domain. Candidate Processes Process analysis. Define metadata, services, and processes Processes, Services, And Information Process integration analysis. Process Integration Diagrams Candidate Services External Processes (B2B) SOA Metadata

23. Copyright 2007 The Linthicum Group, LLC Define new services. Candidate Processes Service definition. Service design. Processes, Services, And Information Service implementation. Process Integration Diagrams SOA Metadata Candidate Services Service Definition Service Design Service Implementation

24. Copyright 2007 The Linthicum Group, LLC Define new processes. Candidate Processes Process definition. Process design. Processes, Services, And Information Process implementation. Process Integration Diagrams Metadata Candidate Services Process Definition Process Design Process Implementation

25. Select your technology set. Technology Requirements Define requirements. Technology analysis. Technology solution Vendors Define candidate technology. Technology selection. Technology validation.

26. “ SOA is Good…” Pay me now, or pay me later. Make sure you do it right the first time…get the help you need. Don’t be afraid to experiment, and admit you’re wrong…backup and try again. Keep your vendors working with you. Empower those working, so they can work to get things done. Avoid politics, if possible. Learn all you can, but don’t get caught up in the hype. Put standards in their proper place. Small battles win the war…Keep that in mind. Give yourself plenty of time, never skimp on any of the steps.

27. Thanks! Blogs: InfoWorld “Real World SOA” Intelligent Enterprise “SaaS Advisor” Weekly Podcast InfoWorld SOA Report Columns Web Services Journal SD Times