SOA Building for the Future

980 views
897 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
980
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
85
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

SOA Building for the Future

  1. 1. SOA Building for the Future XML In Practice Washington, DC 20008 Presented by Saeed Abu Elnaj
  2. 2. Agenda Few Introductory words on SOA The Trouble with SOA The varying views of SOA Two fundamentally different definitions and views of SOA The developers’ view of SOA The vendors’ view of SOA The Literature on SOA Lack of sufficiently trained and experienced resources Developer with expertise Enterprise Architects SOA Standards and XML being the core of such standards The “A” in SOA and the architects view of SOA A Roadmap to SOA: Building for the future 12/9/2008 SOA: Building for the Future 2
  3. 3. Few Introductory Words on SOA and Services Service-Oriented Architecture is an architectural approach to designing, building, and deploying information systems such that the system is created from simpler manageable building blocks, called “services” Each service implements a discrete piece of business functionality. These services can then be mixed and matched to create entirely new applications or to deliver new business capabilities. * Using Definition provided by The SOA Monitor 12/9/2008 SOA: Building for the Future 3
  4. 4. Services Design Principles Service encapsulation Abstraction Loose-coupling Reusable Well-defined service contracts Discoverable “Composeable” Autonomous Granularity Interoperable Business aligned Durable 12/9/2008 SOA: Building for the Future 4
  5. 5. Business and IT benefits of SOA Increased IT asset reuse Reusable services eliminate the need to code from scratch Reuse of legacy systems extend legacy investment Faster and higher quality application development Increased business flexibility or agility Services can be mixed and matched to create new capabilities New capabilities can be delivered faster and cheaper Improved IT flexibility and reduced IT complexity Improved interoperability and internal and external integration Reduced redundancy and maintenance costs 12/9/2008 SOA: Building for the Future 5
  6. 6. Multi-Layered SOA Architecture and Views Governance & Management 12/9/2008 SOA: Building for the Future 6
  7. 7. Gartner Key Findings on SOA SOA was used in more than 50% of large, new applications and business processes designed in 2007 By 2010 Gartner expects that more than 80% of large new systems will use SOA for at least some aspect of their design However, in 2008 the number of organizations that are planning to adopt SOA for the first time was cut by more than one-half, down to 25 percent from 53 percent in 2007 The number of organizations with no plans to adopt SOA more than doubled from 6 percent in 2007 to 16 percent in 2008 Some companies have been disappointed by the low level of service-sharing ("reuse") that they have achieved, and some SOA projects have failed for a variety of reasons SOA face challenges in governance, testing, configuration, version control, metadata management, service-level monitoring, security and interoperability One of the greatest challenges is managing application logic and data in SOA service components that are spread out over multiple business units 12/9/2008 SOA: Building for the Future 7
  8. 8. The Trouble with SOA The varying views and understanding of SOA There are two fundamentally different definitions /views of SOA Management view of SOA The developers’ view of SOA The vendors’ view of SOA The architect’s view of SOA The lack of business case/justification for SOA The lack of sufficiently skilled resources on SOA The complex web of SOA Standards: Over 115 The Literature on SOA 12/9/2008 SOA: Building for the Future 8
  9. 9. The SOA Puzzle and The Two Fundamentally Different Definitions and Views SOA is a business initiative and is about achieving business modularity and agility through customizable, composable and reusable IT-enabled business processes Is it a Top-bottom approach where the business leads in the SOA services analysis SOA is an IT initiative where SOA is viewed as an architectural style whose goal is to achieve loose coupling among interacting software modules Is it a bottom-up approach where IT leads in analysis and identification of services 12/9/2008 SOA: Building for the Future 9
  10. 10. Management View of SOA Understanding and/or appreciation of SOA at CxO level The ever elusive ROI: Only 37% of enterprises have achieved a positive ROI from SOA deployments (Nucleus Research) Everything that can be counted does not necessarily count; everything that counts cannot necessarily be counted (Albert Einstein) 12/9/2008 SOA: Building for the Future 10
  11. 11. Developers View of SOA SOA = Web Services WSDL SOAP UDDI REST 12/9/2008 SOA: Building for the Future 11
  12. 12. Vendors’ View of SOA 12/9/2008 SOA: Building for the Future 12
  13. 13. The Architects’ View of SOA 12/9/2008 SOA: Building for the Future 13
  14. 14. Lack of Resources According to a survey of 106 enterprises conducted by Nucleus Research and KnowledgeStorm, fewer than four in 10 developers use SOA Companies using SOA experienced an improvement in developer productivity by of 28%, however, the productivity savings do not warrant broad SOA deployment Evans Data Corp: About 25% of enterprise developers already have an SOA in place and approximately 28 % more plan on following suit over the course of the next two years. Gartner: Overall, the two major reasons that organizations choose for not pursuing SOA are a lack of skills and expertise, and no viable business case 12/9/2008 SOA: Building for the Future 14
  15. 15. SOA Standards and Specifications the Full View (innoQ Standards Poster) 12/9/2008 SOA: Building for the Future 15
  16. 16. Simplified View of SOA Standards 12/9/2008 SOA: Building for the Future 16
  17. 17. SOA Literature There is little empirical and/or good methodology based literature What we lack a book like “Enterprise Architecture as Strategy” by Jeanne Ross, Peter Weill and David Robertson Mostly anecdotal and project based experiences Some Literature examples: Service Oriented Architecture by Thomas Erl (760 pages!) Service Oriented Modeling by Michael Bell (Don’t buy!) Web Services and Service Oriented Architecture by Douglas Barry (Save your money) Understanding SOA with Web Services by Eric Newcomer and Greg Lomow (Useful if using Web services) Enterprise SOA by Dirk Krafig At Al (Save your money) Enterprise Service Bus by David Chappell (Useful if using an ESB) 12/9/2008 SOA: Building for the Future 17
  18. 18. The “A” in SOA; The Architect’s View Enterprise Modeling Business Context Analysis and Service Identification SOA Technical SOA Application Infrastructure Infrastructure Service Modeling and Development Service Service Build Deploy Run Manage Analysis Design 12/9/2008 SOA: Building for the Future 18
  19. 19. Building for the Future Through an architecture Roadmap to SOA Define Current Location: The “As-is” Architecture Define your destination: Future Architecture that meets business needs (architecture blueprint) Define your Itinerary: Create a priority list of projects and services to evolve the architecture 12/9/2008 SOA: Building for the Future 19
  20. 20. The architecture roadmap has well- defined objectives Identify the technical and capabilities required to address problems and opportunities in the current and planned business and technical environment Develop an SOA blueprint architecture as a framework to support the SOA enabled business vision Develop an SOA architecture evolution plan to incrementally achieve the SOA blueprint architecture Understand the technical components and competencies needed to build a strong service foundation 12/9/2008 SOA: Building for the Future 20
  21. 21. Developing an SOA Roadmap ITERATIVE 12/9/2008 SOA: Building for the Future 21
  22. 22. SOA Architecture Roadmap Methodology Steps and Deliverables Secure buy- Develop Define Assess current in and define state 1 architecture 2 architectural 3 tactical next 4 blueprint evolution steps Gather strategy and Identify and prioritize required Analyze gap between Secure consensus and buy-in architecture documentation business and IT capabilities blueprint & current state of architecture roadmap Key Activities Discover & document system Determine scope of Prioritize architectural Determine scope and functions & data model architecture roadmap initiatives to address gaps objectives for Phase 1 projects Discover & document system Analyze and agree on SOA & Define architectural milestones Determine approach and infrastructure & interfaces other architectural principles for prioritized initiatives staffing requirements Analyze and agree on Analyze architectural Define success criteria & Finalize architectural evolution challenges & opportunities requirements & components performance measures Understand key technology & Model and evaluate various Identify skills sets and Secure funding for Phase 1 architectural constraints architectural scenarios resource requirements projects and initiate execution Deliverables Analysis of challenges, Required business and IT Artifacts to build consensus Gap analysis opportunities and constraints capabilities and secure buy-in Analysis of requirements & Rationale for SOA Architectural evolution plan Detailed Phase 1 project plan architectural components Skills and resource As-is architecture Architecture blueprint Phase 1 project descriptions requirements 12/9/2008 SOA: Building for the Future 22
  23. 23. Phase 1 – Assess current state Secure buy- Develop Define Assess current in and define state 1 architecture 2 architectural 3 tactical next 4 blueprint evolution steps Gather strategy and architecture documentation Key Activities Discover & document system functions & data model Discover & document system infrastructure & interfaces Analyze and agree on challenges & opportunities Understand key technology & architectural constraints Deliverables Analysis of challenges, opportunities and constraints Rationale for SOA As-is architecture 12/9/2008 SOA: Building for the Future 23
  24. 24. Phase 2 – Develop architecture blueprint Secure buy- Develop Define Assess current in and define state 1 architecture 2 architectural 3 tactical next 4 blueprint evolution steps Identify and prioritize required business and IT capabilities Key Activities Determine scope of architecture roadmap Analyze and agree on SOA & other architectural principles Analyze architectural requirements & components Model and evaluate various architectural scenarios Deliverables Required business and IT capabilities Analysis of requirements & architectural components Architecture blueprint 12/9/2008 SOA: Building for the Future 24
  25. 25. Phase 3 – Define architectural evolution Secure buy- Develop Define Assess current in and define state 1 architecture 2 architectural 3 tactical next 4 blueprint evolution steps Analyze gap between blueprint & current state Key Activities Prioritize architectural initiatives to address gaps Define architectural milestones for prioritized initiatives Finalize architectural evolution Identify skills sets and resource requirements Deliverables Gap analysis Architectural evolution plan Skills and resource requirements 12/9/2008 SOA: Building for the Future 25
  26. 26. Phase 4 – Secure buy-in and define tactical next steps Secure buy- Develop Define Assess current in and define state 1 architecture 2 architectural 3 tactical next 4 blueprint evolution steps Secure consensus and buy-in of architecture roadmap Key Activities Determine scope and objectives for Phase 1 projects Determine approach and staffing requirements Define success criteria & performance measures Secure funding for Phase 1 projects and initiate execution Deliverables Artifacts to build consensus and secure buy-in Detailed Phase 1 project plan Phase 1 project descriptions 12/9/2008 SOA: Building for the Future 26
  27. 27. The APA Blueprint 12/9/2008 SOA: Building for the Future 27
  28. 28. Questions & Answers

×