• Save
SOA: A more pragmatic approach to IT
Upcoming SlideShare
Loading in...5
×
 

SOA: A more pragmatic approach to IT

on

  • 2,344 views

 

Statistics

Views

Total Views
2,344
Views on SlideShare
2,331
Embed Views
13

Actions

Likes
6
Downloads
0
Comments
0

4 Embeds 13

http://www.slideshare.net 5
http://www.linkedin.com 4
http://jisi.dreamblog.jp 3
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

SOA: A more pragmatic approach to IT SOA: A more pragmatic approach to IT Presentation Transcript

  • SOA: A more pragmatic approach to IT Peter Evans-Greenwood
  • Service-Oriented Architecture We can't solve problems by using the same kind of thinking we used when we created them!
  • Environmental changes enable a new approach to IT U.S. software sales in billions of dollars Source: INPUT SOAP 1.0 WS-I founded SAP WS J2ME Web Services ESB Apache SOAP MS SOAP IBM Web Services Apache Axis JAX-RPC Oracle WS Sun WS WS (J2EE & .NET) WS-* starts exploding WS-* OASIS SOA Reference Model OASIS SOA Blueprints SAP Netweaver Oracle Fusion JAX-WS MS Indigo BPEL BizTalk 2004 Oracle BPEL WBI-SF WS-Policy and WS-Security 2004 2005 2003 2002 2001 2000 1999 Yesterday Today Tomorrow
  • We’ve tried both ends of the planning spectrum
    • Bottom up action
      • Reacting to changes in the environment
      • No conscious plan
      • Solutions created to meet pressing needs
      • Only addressing needs as understood that time
    • Top-down planning
      • Days spent filling Zachman cells
      • Major transformation initiatives
      • Initiatives behind by people on the ground who need to get the job done
    Reactive Omniscient Both result in inflexible systems-of-systems
  • People use a more pragmatic planning process
    • Establish our goal
    • Understand where we are on the landscape
    • Consider the paths available to us
    • Choose one and head to the junction
    • Return to step 1
  • SOA enables a similar approach for IT Business Service Architecture IT Landscape Business goals and activities are reified in a service architecture The service architecture acts as a planning framework
  • We can use city planning as a metaphor
    • A long term plan
      • Work with the business landscape
      • Create stable infrastructure
    • Manage the process
      • Appoint a zoning board
      • Make the most of what you have
    City planners try to preserve viable old assets, to replace outmoded assets, and to add new assets—all in the context of an infrastructure linking them coherently. IT developers have a good deal to learn from that approach. Jürgen Laartz, Ernst Sonderegger, and Johan Vinckie, The Paris Guide to IT Architecture McKinsey Quarterly, 2000, Number 3,
  • Service architecture provides a planning framework Business Service Architecture IT Landscape
    • Optimize new product introduction
    • Reduce costs
    • Improve process efficiency
    • Manual processes
    • No support for product management
    • Multiple, redundant, applications
    • Capture business in service architecture
    • Identify scenarios by determining miss-match between current IT and service architecture
    • Make a tactical decision on which scenario to deliver, and execute
    • Return to 1 or 2
  • Scenarios deliver well defined business capabilities
    • Each scenario defines
    • Capability delivered
      • Optimize new product introduction
      • Support multi-channel delivery of services to customers
      • Streamline supplier interactions
      • Reduce maintenance costs by consolidating IT assets, freeing up cash for investment
    • Cost, and associated risk
      • Aligned with the business activities effected by the capability
    • Detailed business requirements
    • Technology footprint required
      • New and existing applications
      • New and existing business and technical services
      • Impact on legacy systems
      • Specific technologies required: SOA, BPM, rules engines, MDA, agents, etc.
  • SOA provides a more pragmatic approach to IT
    • Strategic
    • Differentation
    • ROI
    • Tactical
    • Flexability
    • Agility
    Balancing tactical and strategic concerns
  • www.capgemini.com