Ciber Soa April 2007 Omaha


Published on

Published in: Business, Technology
  • 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
  • Ciber Soa April 2007 Omaha

    1. 1. The Service Oriented Architecture (SOA) Roadmap: Overview and Lessons Learnt Dr. Khalid Mansour [email_address]
    2. 2. Who is CIBER? <ul><li>Areas of Expertise </li></ul><ul><li>Application Development and Management </li></ul><ul><li>Enterprise Integration </li></ul><ul><li>Business Intelligence </li></ul><ul><li>ERP </li></ul><ul><li>IT Security </li></ul><ul><li>IT Operations </li></ul>Global IT services company that focuses on driving business value by building , integrating , and supporting mission-critical applications and infrastructures <ul><li>Fast Facts </li></ul><ul><li>More than 8,250+ employees </li></ul><ul><li>$1B in revenue </li></ul><ul><li>NYSE: CBR </li></ul><ul><li>Global Headquarters in Denver </li></ul><ul><li>85 offices in 18 countries </li></ul><ul><li>Expanded to Omaha in 01/2007 </li></ul><ul><li>ISO 9001 certified </li></ul><ul><li>Included in 4 Gartner magic quadrants </li></ul>
    3. 3. <ul><li>Local Relationships with Global Distributed Delivery </li></ul><ul><li>Local resources </li></ul><ul><li>Global technology practices </li></ul><ul><li>Domestic development centers </li></ul><ul><li>Offshore development and support </li></ul><ul><li>IT operations outsourcing </li></ul><ul><li>Delivery Model </li></ul><ul><li>Leverages the right resources to </li></ul><ul><li>achieve the optimal balance between </li></ul><ul><li>risk and cost </li></ul><ul><li>Flexibility </li></ul><ul><li>Proven tools, frameworks, and processes </li></ul><ul><li>to reduce cost and complexity </li></ul>How CIBER Drives Value ONSITE TEAM OFFSITE TEAM NEAR/OFFSHORE TEAM
    4. 4. Agenda <ul><li>Business and IT drivers </li></ul><ul><ul><li>What is the problem(actual client example)? </li></ul></ul><ul><ul><li>Current IT challenges </li></ul></ul><ul><li>SOA overview </li></ul><ul><ul><li>What is SOA? </li></ul></ul><ul><ul><li>How does it work? </li></ul></ul><ul><ul><li>Benefits and obstacles </li></ul></ul><ul><ul><li>Lessons learned </li></ul></ul><ul><ul><li>Possible roadmap adoption activities </li></ul></ul><ul><li>Q & A </li></ul>
    5. 5. Essence of SOA <ul><li>“ It is not the strongest of the species that survive, nor the most intelligent, but the one most responsive to change .” Charles Darwin </li></ul><ul><li>Companies need strategies to enable operational agility and flexibility </li></ul>
    6. 6. Business Drivers and IT Challenges <ul><li>Business drivers : </li></ul><ul><ul><li>Support for business agility and innovation </li></ul></ul><ul><ul><li>Mergers and acquisitions </li></ul></ul><ul><ul><li>Regulatory and compliance requirements. </li></ul></ul><ul><ul><li>Faster time to market </li></ul></ul><ul><ul><ul><li>Improve capacity and responsiveness of IT </li></ul></ul></ul><ul><ul><ul><li>Improve operational effectiveness </li></ul></ul></ul><ul><li>IT issues that affect the business : </li></ul><ul><ul><li>Increasing complexity and little re-use </li></ul></ul><ul><ul><ul><li>Monolithic applications and tightly coupled rigid systems </li></ul></ul></ul><ul><ul><ul><li>Complexity and cost - multiple development platforms, tools, support teams </li></ul></ul></ul><ul><ul><li>Lack of available skills and expertise to maintain established systems </li></ul></ul><ul><ul><li>Data quality and data management issues </li></ul></ul><ul><ul><ul><li>Multiple, inconsistent sources exist for each data entity (master data) </li></ul></ul></ul>IT is Barely reactive to changing business needs
    7. 7. Real life Case Study: B2B Parts Supplier <ul><li>Cannot efficiently integrate new Suppliers, new acquisitions, or new service offerings into our increasingly complex systems </li></ul><ul><li>Cannot provide the breadth of information required for full operational effectiveness </li></ul><ul><li>Cannot leverage our dispersed information to more effectively ‘Capture the Customer’ </li></ul><ul><li>80% of the system interfaces to/from ERP rely on file transfer techniques no ‘real-time’ processing </li></ul>
    8. 8. The Application Integration Problem <ul><li>Applications need to integrate with each other </li></ul><ul><ul><li>Data Issues </li></ul></ul><ul><ul><ul><li>No single enterprise view of data </li></ul></ul></ul><ul><ul><ul><li>No common data “dictionary” across the enterprise </li></ul></ul></ul><ul><ul><ul><li>Each application has a different data format </li></ul></ul></ul><ul><ul><ul><li>Applications talk to each other via point-to-point </li></ul></ul></ul><ul><ul><ul><li>Knowing about each other’s data format leads to tight coupling and inflexibility Inability to consolidate data from multiple diverse sources </li></ul></ul></ul><ul><ul><li>Interoperability issues </li></ul></ul><ul><ul><ul><li>Applications run in a different environment (Java, .Net, Mainframe) </li></ul></ul></ul>
    9. 9. Paradigm Shift <ul><li>The Goal is to build a flexible scalable platform for service execution, customized for your needs to enable the constant changes in the business environment </li></ul><ul><li>Integration becomes the centerpiece! </li></ul><ul><li>Standards and interoperability are key enablers </li></ul><ul><li>IT drives the business </li></ul>Traditionally = application-centric New = integration-centric, innovation = plug-in business functionality
    10. 10. The Adaptive Business Process Platform <ul><li>Foundation : this process portfolio contains stable business processes (i.e., packaged business applications): </li></ul><ul><ul><li>They provide reports, transactions and analysis that are necessary for everyday business needs </li></ul></ul><ul><ul><li>Remain untouchable, unless there is a need to pull information to another business process </li></ul></ul><ul><li>Innovation : this process portfolio contains processes that differentiate the business ( composite applications ) </li></ul><ul><ul><ul><li>Flexible, scalable, and open to change – dynamic </li></ul></ul></ul>
    11. 11. Service Oriented Architecture (SOA) – What is it? <ul><li>An approach for designing, and implementing business applications and infrastructure. It incorporates centralized assembly and management of reusable distributed autonomous business functions (“services”) in a loosely coupled manner </li></ul><ul><li>Characteristics: </li></ul><ul><ul><li>Represents business functions as a services </li></ul></ul><ul><ul><li>Primary focus shifts toward process definition, process assembly, re-use, process visibility and control </li></ul></ul><ul><ul><li>Allows individual software assets (business logic + data) to become building blocks to develop business processes </li></ul></ul><ul><ul><li>Leverages open standards to represent software assets </li></ul></ul><ul><ul><li>Requires underlying enterprise data architecture that provides consistent, timely accurate data </li></ul></ul>
    12. 12. SOA Benefits and Obstacles <ul><li>Challenges </li></ul><ul><li>Cultural Shift </li></ul><ul><li>Actual migration to SOA </li></ul><ul><li>Tighter governance </li></ul><ul><li>Change of attitude and learning new skills (process knowledge) </li></ul><ul><li>Benefits Leave-and-Layer </li></ul><ul><li>Lower total cost of ownership </li></ul><ul><li>Process visibility </li></ul><ul><li>Iterative implementation </li></ul><ul><li>Re-use </li></ul><ul><li>Better maintainability </li></ul>
    13. 13. SOA Capability and Benefits <ul><li>Lower workload : </li></ul><ul><ul><li>Pre-configured business content </li></ul></ul><ul><ul><li>Lower integration effort (apps + partners) </li></ul></ul><ul><ul><li>Outsourcing of standard processes/services </li></ul></ul><ul><li>Lower costs : </li></ul><ul><ul><li>Infrastructure </li></ul></ul><ul><ul><li>Integration </li></ul></ul><ul><ul><li>Reused assets </li></ul></ul><ul><li>Flexibility : </li></ul><ul><ul><li>Less complex applications (less code/bugs) </li></ul></ul><ul><ul><li>New services easy to develop/integrate </li></ul></ul><ul><ul><li>Services easy to adapt to business process change </li></ul></ul><ul><li>Process Automation : </li></ul><ul><ul><li>Workflows across applications </li></ul></ul><ul><ul><li>Automation of manual processes </li></ul></ul><ul><ul><li>Process integration with business partner </li></ul></ul><ul><li>Best Integration </li></ul><ul><li>Manageable, consolidated SAP platform </li></ul><ul><li>Reduce IT costs </li></ul><ul><li>Manage IT outsourcing </li></ul><ul><li>Manage Supply Chain </li></ul><ul><li>Support divisional business models </li></ul><ul><li>Support business agility and growth </li></ul>How can SOA help doing that? Key Drivers for IT
    14. 14. Lessons Learned
    15. 15. SOA Is a Strategic Evolution In IT; It Will Take Time… <ul><li>Building the business case </li></ul><ul><ul><li>Priorities should be weighted </li></ul></ul><ul><li>Ensure organizational readiness </li></ul><ul><ul><li>Senior management buy-in </li></ul></ul><ul><ul><li>Internal communication of benefits to end users </li></ul></ul><ul><li>Execute, manage, and govern iteratively </li></ul><ul><li>Please do not: </li></ul><ul><ul><li>Rush to deploy technology solutions </li></ul></ul><ul><ul><li>Ignore master data issues, data architecture </li></ul></ul><ul><li>Do not underestimate the cultural issues!!! </li></ul>
    16. 16. Few Best Practices To Consider
    17. 17. Best Practices For Building a SOA <ul><li>Understand what is needed to support the business – upfront </li></ul><ul><li>Invest in building and developing your enterprise architecture strategy: </li></ul><ul><ul><li>Build a process for prioritizing IT projects across the enterprise </li></ul></ul><ul><ul><li>Consider your architectural expertise and development skills, best practices, guidelines and standards </li></ul></ul><ul><ul><li>Consider model-driven development tools </li></ul></ul><ul><ul><li>Document your business processes </li></ul></ul><ul><ul><li>Document your data exchange formats (canonical data and message formats) </li></ul></ul><ul><ul><li>Consider service management and middleware expertise </li></ul></ul>
    18. 18. Best Practices For Building a SOA - continued <ul><li>Build your SOA adoption roadmap </li></ul><ul><li>Understand the different integration behaviors within your enterprise </li></ul><ul><li>Understand the tradeoffs of going w/ best of breed or stacks vs. vendor suites </li></ul><ul><li>Plan for multiyear incremental steps ; iterative implementation (3-5 years minimum) </li></ul>
    19. 19. Key Message – Evolutionary Approach towards Implementing SOA <ul><li>Service-oriented architecture is fundamentally about the abstraction of business events, modeled as enterprise services, from the actual underlying of applications and data </li></ul><ul><li>SOA is part of your strategic blueprint (need EA roadmap) </li></ul><ul><li>Long term cultural shift </li></ul><ul><li>Implementing tools and technologies will not automatically give you SOA </li></ul><ul><li>A full-blown implementation of enabling technologies is no prerequisite for an SOA </li></ul><ul><li>SOA without good data is doomed to failure </li></ul><ul><li>SOA without governance will not realize full value </li></ul>