• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Anne  Thomas Manes    S O A  Fatigue
 

Anne Thomas Manes S O A Fatigue

on

  • 433 views

 

Statistics

Views

Total Views
433
Views on SlideShare
432
Embed Views
1

Actions

Likes
0
Downloads
3
Comments
0

1 Embed 1

http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

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

    Anne  Thomas Manes    S O A  Fatigue Anne Thomas Manes S O A Fatigue Document Transcript

    • 22-10-2008 This Presentation Courtesy of the International SOA Symposium October 7-8, 2008 Amsterdam Arena www.soasymposium.com info@soasymposium.com Founding Sponsors Platinum Sponsors Gold Sponsors Silver Sponsors FIGHTING SOA FATIGUE SOA SYMPOSIUM 8 OCTOBER 2008 Anne Thomas Manes VP & Research Director Burton Group amanes@burtongroup.com 2 1
    • 22-10-2008 Fighting SOA Fatigue Agenda • Opening statements • Evidence • Governance revisited • Engaging the business 3 4 2
    • 22-10-2008 “Most SOA efforts will fail spectacularly.” “SOA is a 20-year initiative” “Didn't we try this 20 years ago?” "In the beginning, we didn't have a clue what we were doing.” “We built a great SOA runtime, but a) none of our executives care b) no one is using it” “We can't use the term SOA with our executives any more.” 5 “Reusability is always overpromised.” “Is there such thing as a Complex Object Access Protocol?” “You mean, we're going to spend $X just to replicate existing functionality?” CFO to architect: “How much money is this going to save me?” “If no one is reaching maturity yet, why are we still trying?” 6 3
    • 22-10-2008 Thesis SOA fatigue is setting in because SOA success is tenuous. But… when it succeeds, it really succeeds! It succeeds when organizations have strong leaders And good governance. Now it’s time to connect SOA to higher-level objectives. 8 Fighting SOA Fatigue EVIDENCE OF THE TRIBAL YAWN 4
    • 22-10-2008 Vendor Messages • New branding of old stuff • “We're 100% SOA compatible!” • “We offer a complete SOA SOA solution!” 9 Technical Challenges • Perceived (and actual) complexity • SOA concepts don't always map 1:1 with topology or tools • Trying to do too much/wrong things with wrong tools 10 5
    • 22-10-2008 Design Challenges Partitioning design and Separation of Concerns • UI • Application • Data • Network • Dynamic data center 11 Project Challenges • SOA is a long-term strategic undertaking • Fixes and point releases trump strategic infrastructure work • Many projects are scoped on an annual basis 12 6
    • 22-10-2008 Cultural Challenges • Shared solutions require shared objectives • No incentive for collaboration • Business domain “normalization” is politically charged 13 Management Challenges People may be tasked with unreachable goals Advocacy (to management) is complicated Churn in executive leadership 14 7
    • 22-10-2008 Real Risks • The best “academic” technical solutions may not be “right” (context and fit) • If cultural problems are not addressed, outcome is SOA silos • Assumptions by IT staff about Business Value may be wrong 15 16 Fighting SOA Fatigue GOVERNANCE REVISITED 8
    • 22-10-2008 Good Governance Enables Multiple Perspectives 17 Good Enterprise Architecture Increases Influence Business Strategies Business Prescribe Supports Operational Model Formalizes Influences Enterprise Architecture Technology Guides Realizes IT Infrastructure 18 9
    • 22-10-2008 Systems Change. At Different Rates. space plan services stuff structure skin site From How Buildings Learn: Stewart Brand 19 This sounds really complex. :-( 20 10
    • 22-10-2008 Simplicity: Not as simple as it seems. Most technology goes through cycles of development and change in both internal and external complexity. As the technology matures… devices become easier to use, although usually by becoming more complex inside. Donald Norman, The Invisible Computer Simplicity = Managed Complexity 21 “The proper role of *governance+ …is to represent the interest of the future to the present.” Lester Thurow 11
    • 22-10-2008 . . . don’t ask—it’s forbidden to know— what end the gods will give me or you. Even as we speak, envious time is running away from us. Carpe diem, for in the future you can believe the minimum. Developerus Heroicus 23 Governance Top-down Restriction Overhead Control Taxing Limitation Standards Regulations Rules 24 12
    • 22-10-2008 Is EA Working? EA loses influence when… It is ignored It is undervalued It is disconnected from reality It is frozen It is inconsistent It is circumvented It inhibits 26 13
    • 22-10-2008 Empowered EA • Is outcome-oriented • Prescribes the shape of things • Fit (requirement) • Describes the place of things • Context (dependencies) • Makes good design easier • Runs interference • Takes advice “No one can use rehearsal time as well as Simon Rattle. He's absolutely disciplined, but also inspiring. He urges you to do things you hadn't thought you were capable of.” Musician, Berlin Philharmonic 27 governance 14
    • 22-10-2008 29 Fighting SOA Fatigue ENGAGING THE BUSINESS Enter the Conversation The evolution of IT from cost center to strategy driver started about five years ago. After living through the pain of shadow IT in the business units…Baird was not going to thrive unless IT had “relevant conversations with the business units about how IT could contribute to their success.” IT had to prove it could offer business solutions, “not toys and technology that we thought were cool.” Brian Brylow (CTO), Baird 30 15
    • 22-10-2008 Connect SOA to Business Priorities Compliance reporting Software as a Service (SaaS) Unified Communications Legacy modernization SOA? Outsourcing/Offshoring Provisioning and Role Management Business Process Management (BPM) Business Intelligence (BI) 31 SOA is Part of a Something Bigger Overemphasis on SOA in isolation distracts from enterprise goals SOA makes it easier to accomplish higher goals SOA must have business relevance SOA is not a thing SOA is an architectural style Technology implementation of SOA principles will change 32 16
    • 22-10-2008 Conclusion SOA is a valid architectural style • But may not be appropriate for all cases SOA can provide cost savings • But not without careful financial analysis SOA principles are fundamental to agility • But do not guarantee agility SOA promotes reuse • But does not guarantee reuse SOA fatigue is real • So, we have to raise the level of discussion 33 Fighting SOA Fatigue 34 References • Building the Business Case for SOA Investment • Addressing SOA Fatigue • Service-Oriented Architecture: Developing the Enterprise Roadmap • Enterprise Architects: Sowing the Seeds of SOA Success • Vantage Point 2008-2009: Think Big; Take Small Steps • Application Rationalization: Burning Fat and Building Muscle • A New Classicism • Service Oriented Architecture Implications • The Anatomy of Effective Enterprise Architecture • Enterprise Architecture is More than Engineering • Establishing and Maintaining Enterprise Architecture Momentum 17