14 of 14 people found the following review helpful:
5.0 out of 5 stars
SOA book for the business analyst, March 24, 2006
This review is from: Service Orientation: Winning Strategies and Best Practices (Hardcover)
Most SOA books on the market are technical books for purely technical audiences. SOA is architecture, after all, and software architecture can be a complex, technically difficult subject. Recently, though, several business-oriented books on SOA have hit the shelves. These books typically attempt to explain the intricacies of SOA and the underlying alphabet soup of technologies and standards in a non-technical fashion for an audience that would like a high-level view of what SOA is all about, but who doesn't really want to know either the technical details or how to roll up their sleeves and work with SOA themselves.
This book falls into neither of these categories. "Service-Orientation: Winning Strategies And Best Practices" is an exceptional example of a book written for a technically savvy business reader who doesn't want merely a high-level explanation of SOA, but rather wants to understand the critical SOA concepts, strategies, and best practices that they need to do their job. This choice of audience is no accident. In fact, part of the fundamental transformative nature of SOA involves new roles for the individuals at the companies that implement the architecture. Understanding the proper audience for this book, therefore, is an important step on the road to understanding SOA.
SOA is basically an approach -- or discipline, if you will -- for organizing IT resources as business-oriented Services that users can find, use, and incorporate into business processes. Core to SOA is the notion of the Services abstraction layer -- the representation of IT functionality that business users interact with. Beneath this abstraction layer are applications, servers, networks, and the rest of the heterogeneous collection of technology that IT shops maintain today. From the business user's perspective, however, this complex mishmash of technologies fade from view. What remains are the Services and the business processes that orchestrate them.
As a result, the challenges that businesses face as they leverage the power of SOA fall into two general areas: management and process. Management is the first challenge, because the business must be able to rely upon their IT infrastructure without having to pierce the Services abstraction to control the nuts and bolts of the implementation beneath. The core management issues that this book's audience must focus on include Service execution management, Service level management, as well as the management of the business process that constitute the second set of challenges for businesses that implement SOA. Among those challenges are building business Services and composing them into business processes that are themselves Services. Such Service-oriented processes enable the broad redesign of the older, inflexible processes that are typically in place today at most organizations.
The level of detail this book provides, therefore, is for a new kind of audience that must understand the intricacies of Service-oriented management and process. The average business reader will not typically need or want this level of detail, and the typical technical reader will require more information about the technical details underneath the Services abstraction than this book intends to provide. The big question, therefore, is what sort of person is among the audience for this book, and are you that sort of person?
The most common title for this book's target audience member might be business analyst, and there's no question that many business analysts will find this book useful and understandable. However, the business analyst title is poorly defined, and two people with this title at different organizations might find their jobs to be vastly different. As companies implement SOA, though, it is likely that many business analysts will find their roles coalescing onto a more specific set of responsibilities centering on process and management as explained above.
Other roles that may either fall into the broader business analyst category or be separate titles in their own right are that of the Service architect and business process architect. As explained in Chapter 13, people in these roles focus on building business Services, composing them into processes, and then managing those processes as they meet changing business requirements. Such people are business-oriented yet technically savvy, understand SOA from a business perspective, and often act as liaisons between business management and IT. Regardless of whether your title is business analyst, Service architect, or process architect, if you are a roll-up-the-sleeves business reader and you find yourself in this bridge role between business and IT as your company implements SOA, then this book is for you.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
2 of 2 people found the following review helpful:
4.0 out of 5 stars
high level [non-technical] advice, September 23, 2006
This review is from: Service Orientation: Winning Strategies and Best Practices (Hardcover)
Service Oriented Architecture has gotten considerable attention recently. The book studies its potential in improving business processes. Both within a company and between companies. There is very little here at the technical level of programming. The book is pitched at a higher level, suitable for upper management interested in improving the corporate business value. Advice is furnished on how to devise measurable goals. So that any redesign does not take place in a vacuum.
It is also suggested that business agility can be enhanced. By letting a company redirect and modify existing services in an easy modular manner.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No