Service Oriented Architecture Field Guide for Executives E-Book

Kyle Gabhart

• Herausgeber: John Wiley & Sons
• Kategorie: Fachliteratur
• Sprache: Englisch

Seitenzahl: 268

Veröffentlichungsjahr: 2008

Beschreibung

Service Oriented Architecture Field Guide for Executives is a fundamental breakthrough in the business and technology perspectives of service oriented architecture (SOA). A valuable resource to help you understand and realize the benefits of SOA in today's companies, this guide will show you how to plan, implement, and achieve SOA value. Use a prescriptive approach to help you clearly understand SOA and to determine its applications for your business. Applicable to all industries, technology platforms, and operating environments, this innovative book will provide you with essential strategies.

Leseprobe

Table of Contents

Title Page

Copyright Page

Dedication

PREFACE

Acknowledgements

SECTION ONE : - WHAT IS SOA AND WHY SHOULD I CARE?

CHAPTER I - SOA PRIMER

FROM AD-HOC SOLUTIONS TO SERVICE ORIENTED CAPABILITIES

WHAT EXACTLY IS SOA?

DECONSTRUCTING SOA

IS SOA THE LATEST INDUSTRY FAD?

SUMMARY

SOA CASE STUDIES

CHAPTER 2 - BUSINESS PROCESS MANAGEMENT AND SOA

WHAT IS A BUSINESS PROCESS?

ARE YOU PROCESS ORIENTED?

BECOMING PROCESS ORIENTED

WHAT IS BUSINESS PROCESS MANAGEMENT?

BUSINESS PROCESS AND SOA

ALIGNING IT WITH THE BUSINESS

BECOMING SERVICE ORIENTED

FROM OBJECT TO SERVICE ORIENTATION

BUSINESS PROCESS MODELING

ESTABLISH THE BUSINESS PROCESS

MONITOR AND CONTROL THE PROCESS

IMPROVE OR ALTER THE BUSINESS PROCESS

SUMMARY

CHAPTER 3 - SOA VALUE PROPOSITION

SOA VALUE STORY

SOA VALUE, BEYOND THE CORE

SURGICAL ADOPTION OF SOA

CASE STUDY: SOA VALUE PROPOSITION

SUMMARY

NOTE

CHAPTER 4 - RISKS IN SOA ADOPTION

WHY DO WE USE TECHNOLOGY?

IT AS A TOOL

BARRIERS TO SOA’S PROMISES

OTHER RISKS

SUMMARY

NOTES

SECTION TWO : - IS SOA RIGHT FOR MY BUSINESS?

CHAPTER 5 - IS SOA RIGHT FOR YOU?

MEASURING THE APPROPRIATENESS OF SOA

TECHNOLOGY EVALUATION

SUMMARY

NOTE

CHAPTER 6 - APPLYING SOA TO VARIOUS INDUSTRIES

DEFENSE SECTOR

FINANCIAL SECTOR

MEDIA SECTOR

TECHNOLOGY SECTOR

TRAVEL SECTOR

APPLYING SOA TO OTHER SECTORS AND SPECIFIC INDUSTRIES

SUMMARY

NOTES

CHAPTER 7 - CALCULATING SOA ROI

QUANTIFYING SOA ROI

TACTICAL SOA ROI

OPERATIONAL SOA ROI

STRATEGIC SOA ROI

SCHEDULE AND RISK: THE HIDDEN FACTORS IN EVALUATING ROI

CASE STUDY: CALCULATING SOA ROI

SUMMARY

NOTES

SECTION THREE: - HOW SHOULD I GO ABOUT ADOPTING SOA?

CHAPTER 8 - SELECTING AN SOA MATURITY MODEL

GAUGING MATURITY

SOA MATURITY MODELS AT A GLANCE

WEB SERVICES MATURITY MODEL

SERVICE INTEGRATION MATURITY MODEL

SERVICE ORIENTED ARCHITECTURE MATURITY MODEL

SELECTING A MATURITY MODEL

SUMMARY

NOTES

CHAPTER 9 - HOW MUCH SOA DO I NEED?

SOA IS NOT A PANACEA

WHAT CHILDREN TEACH US ABOUT SOA

SELECTIVE SOA METHODOLOGY

APPLYING THE SELECTIVE SOA METHODOLOGY

SUMMARY

CHAPTER 10 - ACQUIRING THE SKILLS FOR SOA

MULTISTAGE TRAINING PROGRAM

ROLES AND RESPONSIBILITIES

SKILLS BY ROLE

CHAPTER 11 - RISK MITIGATION THROUGH PROPER GOVERNANCE

LIFE WITHOUT GOVERNANCE

UNDERSTANDING SOA GOVERNANCE

GOVERNANCE TIPS TO SUCCESS

SUMMARY

NOTES

CHAPTER 12 - CREATING YOUR SOA ADOPTION PLAN

READY ... FIRE ... AIM?

THE PLAN

EVALUATING SOA

ADOPTING SOA

SUMMARY

NEXT STEPS

APPENDIX - STANDARDS IN SOA

INDEX

This book is printed on acid-free paper.

Copyright © 2008 by Kyle Gabhart and Bibhas Bhattacharya. All rights reserved. Published by John Wiley & Sons, Inc., Hoboken, New Jersey.

Published simultaneously in Canada.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, 978-750-8400, fax [phone], or on the Web at www.copyright.com. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, 201-748-6011, fax [phone], or online at http://www.wiley.com/go/permissions.

Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created or extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Neither the publisher nor author shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages.

For general information on our other products and services, or technical support, please contact our Customer Care Department within the United States at 800-762-2974, outside the United States at 317-572-3993 or fax [phone].

Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books.

For more information about Wiley products, visit our Web site at http://www.wiley.com.

Library of Congress Cataloging-in-Publication Data:

Gabhart, Kyle, 1979- Service oriented architecture field guide for executives/ Kyle Gabhart, Bibhas Bhattacharya. p. cm. Includes index.

eISBN : 978-0-470-41956-4

1. Information technology-Management. 2. Computer architecture. I. Bhattacharya, Bibhas, 1967- II. Title. HD30.2.G33 2008 004.068-dc22 2008009614

To my son, Gabriel, my parents, and the entire Wheeler family—Bibhas To my best friend Elizabeth, daughter Kati, and two troublemakers, Alex and Drew—Kyle

PREFACE

This book began its journey in June 2005 when Web Age Solutions delivered its first customized service oriented architecture (SOA) education program. As the standard and custom curriculum developed and mentoring engagements ensued, best practices and enterprise-level implications for service orientation began to emerge. Executive-level overviews of SOA were offered in 2006, as well as architect and developer bootcamps. In 2007, Web Age produced several whitepapers around SOA and expanded its curriculum to include a broader set of roles, increased focus on enterprise strategy and executive decision making, and industry-centric solution offerings. This book builds on this body of work and incorporates frameworks, methodologies, best practices, and guidance that have been honed based on real-life experiences with clients of all shapes and sizes from a wide range of industries and market segments.

Throughout our client engagements and participation at various conferences, a very real gap between the business and technology communities made itself apparent. Massive resources are available to technologists who wish to pursue SOA. A smaller set of resources are available to senior analysts and managers who wish to pursue SOA. Virtually no resources exist to provide business leaders, technology executives, or other key innovators with guidance regarding what SOA is really about, when it makes sense, when it does not, and how to pragmatically go about evaluating and ultimately adopting it. We wrote this book to fill that void.

ACKNOWLEDGMENTS

Writing this book has been a journey and a labor of love for both of us. This text is the result of years of developing and supporting service oriented solutions, working with our clients on their service oriented strategies, and countless hours of research. The strategies, frameworks, models, and guidelines outlined in this book are not theoretical. They are applied daily by us and the entire Web Age team in classrooms, server rooms, and boardrooms throughout North America and around the world.

Of course, this book could not have been written without the support of an incredible team behind us. Thanks are due to several people who supported the book as advisors and reviewers: Jason Bloomberg, Lisa Bromwell, Paul Curtis, Ron Schmeltzer, and Chris White. We would like to thank the entire Web Age team for helping us by reviewing early drafts and providing us with valuable insight and critical feedback as this book came together. Special thanks to Tapas Banerjee, Greg Wagner, and Gary Bilodeau at Web Age for being flexible and supportive of our limited availability during the months that we spent writing this book.

Bibhas would like to extend special thanks to Tapas Banerjee and Stephen Wheeler. Both are thinkers in the areas of large-scale software development and IT management. Their feedback during lengthy and rather one-sided conversations with Bibhas provided valuable input for the book.

Kyle would like to thank Jason Gordon for introducing him to Java and XML, Chris White for helping him realize that there is more to life than Java (and for countless technical support calls at all hours of the night), and Kelly Johnson for taking a chance on a budding technologist so many years ago. Special thanks go out to Kyle’s supportive parents, beautiful children Kati, Alex, and Drew, faithful dog Ginger, and partner and soul mate, Elizabeth. This book couldn’t have happened without your love, support, and patience.

SECTION ONE :

WHAT IS SOA AND WHY SHOULD I CARE?

If you haven’t heard about service oriented architecture (SOA), then you have likely been living under a rock for the past several years (it is also very unlikely that you would purchase a book on the topic). There is a tremendous degree of hype, FUD (fear, uncertainty, and doubt), and misinformation floating around regarding SOA, service orientation in general, and what it really means for modern enterprises. This first part of the book is aimed at cutting through all of this and providing a solid foundation in SOA, its huge potential, and its inherent risks.

Chapter 1, “SOA Primer,” introduces and defines SOA, explains what it means to be service oriented, and describes how we evolved to this point. The chapter introduces the typical architectural layers that comprise an SOA enterprise solution and the key SOA infrastructure elements that are commonly found.

Chapter 2, “Business Process Management and SOA,” introduces and defines business process management (BPM), explains what it means to be process-centric, and describes how all of this relates to SOA. Alignment between IT and business through BPM is examined, along with the relationship between objects, services, and processes. Finally, process modeling is explored in great detail.

Chapter 3, “SOA Value Proposition,” identifies the four core SOA value propositions (reduced integration expense, increased asset reuse, business agility, reduced risk) as well as several emerging values (alignment, time to market, visibility, and modernization). These value propositions are then explored by looking at the two fictitious case studies used throughout this book.

Chapter 4, “Risks in SOA Adoption,” takes a raw and honest look at IT challenges and barriers to SOA success. Common SOA promises are examined, including business and IT alignment, process automation through SOA, service reuse, service composition like LEGO® blocks, smoother integration through open standards, and improved business responsiveness. SOA has potential, but this chapter provides a very real look at the risks inherent within SOA.

CHAPTER I

SOA PRIMER

You awake to the familiar buzz of your alarm clock and stumble out of bed and into the bathroom. With a flick of a light switch you are blinded by the bathroom light (unless you have one of those fancy bathroom lights that gradually brightens to allow your eyes to adjust). Later you plug in your coffee grinder, grind some fresh beans, and then brew a steaming pot of coffee. Throughout your morning routine, you use electricity. You use as much or as little of it as you need and you do so with little regard for how much electricity you have consumed that day, week, or month. Some weeks or months, travel and work schedule may dictate less time at home (and less electricity consumption); other days or weeks, you may consume much more. Electricity is a service. It is available on-demand based on a predetermined fee structure and is delivered consistently based on industry standards and regulated infrastructure. Electricity, like other utilities, is service oriented.