Service-oriented architecture (SOA) has become an important topic for financial services organizations, offering new levels of flexibility, adaptability and cost savings.
This book cuts through the confusion by clearly describing SAP's approach to SOA-the enterprise services architecture (ESA), shared with leading banks and insurance companies. By illustrating the principles and vision behind ESA, this invaluable guide shows you exactly how it can benefit your financial services firm. In a concise and easy-to-read format, the authors introduce you to ESA and explain exactly how it works. In addition, you'll get a detailed description of the key steps that financial services institutions need to take in order to successfully deploy ESA.
This book is written primarily for CIOs, CTOs, IT managers, and consultants.
Highlights include:
SOA and the benefits of the enterprise services architecture approach
Characteristics of ESA: Architectural concepts, deployment and model-driven design
Designing an application landscape: Business-driven design approach, types of services, architectural plan
SAP's approach to ESA: Layering, service design, process platform, clusters
Standards-based business applications: Semantic, technical, and portability standards
Transition to ESA: Critical success factors
ESA Checklist: Steps to successfully deploy ESA
Reihe
Sprache
Verlagsort
Editions-Typ
Maße
Höhe: 24 cm
Breite: 16.8 cm
ISBN-13
978-1-59229-095-6 (9781592290956)
Schweitzer Klassifikation
Autor*in
Bruno Bonati worked for Credit Suisse from 1986 to 2004. Since 1996, he was responsible for IT and Operations as a member of the Executive Board. Under his leadership, Credit Suisse became a pioneer in the banking industry because of its service-oriented architecture (SOA). Bruno Bonati's primary focus has been on responding to strategic and management questions via SOA solutions. Since 2005, he has worked as an independent strategic IT consultant for larger institutions-predominantly banks-and SAP.
Joachim Regutzki has worked at SAP since 1988, where he started as a developer in the areas of automated payment processing and electronic banking. In 1990, he became project manager for the development of a foreign currency management solution, and from 1993 onward, he also coordinated the development of the SAP modules for cash management and money market transactions. Between 1996 and 2000, Mr. Regutzki headed the development of SAP's Treasury solutions, the Corporate Finance Management (CFM) initiative, and from 2000 onward, he was in charge of the New Application development within SAP's IBU Financial Services. Since October 2002, he has focused on SAP's insurance solutions as Chief Solution Architect.
Martin Schroter is a Chief Solution Architect at SAP. After getting a degree in business administration, he worked as an auditor and consultant for banks for five years. In 1996, Mr. Schroter joined SAP, where he has been a member of SAP's Banking division since its inception eight years ago. As a solution architect, he works on integrating market trends and customer requirements into a product portfolio and defining the scope of individual solutions. His responsibilities include developing application landscapes and roadmaps for customers, and setting strategic guidelines for internal development areas. Currently, his primary interest is exploring the architectural principles of service-oriented architecture (SOA) and their practical use.
Foreword
1. Global Warming: Stormy Weather Lies Ahead for the Financial Services Industry ... 11
... 1.1 Things Fall Apart, and Yet the Center Holds ... 12
... 1.2 IT as Problem and Solution ... 13
... 1.3 Enter the Service ... 14
... 1.4 Giving Technology the Business ... 14
2. The Best of Times, the Worst of Times: A Ping-Pong Game between IT and Business ... 17
... 2.1 Reliability ... 17
... 2.2 Business Practices ... 19
... 2.3 Growth ... 21
... 2.4 Can SOA Make It Happen? ... 23
3. SOA: Hope, Hype, or Cold Coffee? 25
... 3.1 Getting Back to Basics ... 28
... 3.2 So, Is SOA the Answer to the Eternal Quest for Flexibility? ... 30
4. ESA Overview: Putting SOA to Work in the Enterprise ... 31
... 4.1 Transforming SOA into ESA ... 33
... 4.2 Putting Theory into Practice ... 35
... 4.3 The Changing Role of IT ... 39
5. Digging Deeper into Enterprise Services Architecture ... 41
... 5.1 The Enterprise Service as a Contract ... 42
... 5.2 Defining the Right Semantics ... 44
... 5.3 Little Drops of Water, Little Grains of Sand ... 45
... 5.4 Model-Driven Architecture ... 46
... 5.5 Communication Paradigms ... 53
... 5.6 Service Providers and Consumers ... 54
... 5.7 Service Implementation ... 56
... 5.8 Deployment ... 58
6. Designing an Application Landscape with Enterprise Services Architecture ... 59
... 6.1 A Top-Down Approach That Means (and Starts with) Business ... 59
... 6.2 Business-Driven Solution Design ... 60
... 6.3 A Step-by-Step Approach to Designing Enterprise Services ... 65
... 6.4 Systems of Related Enterprise Services ... 72
... 6.5 Enterprise Services in the Context of IT Landscapes ... 76
7. Turning ESA into Reality: SAP's Solution Approach ... 83
... 7.1 Transforming an Existing Software Application ... 83
... 7.2 Layering ... 84
... 7.3 Service Design ... 85
... 7.4 Service Implementation ... 86
... 7.5 Process Platform ... 86
... 7.6 Core Functionality for Financial Services Companies ... 88
... 7.7 Business-Oriented Clustering of Enterprise Services ... 88
... 7.8 Clusters in the Real World ... 89
... 7.9 Technical Perspective ... 91
... 7.10 Summing Up the Benefits of the Process Platform ... 91
... 7.11 ESA Ecosystem ... 92
8. ESA: A Framework to Build, Develop, and Run Standards-Based Business Applications ... 93
... 8.1 Categories of Standards ... 95
... 8.2 Standards in Enterprise Services Architecture ... 98
9. Making the Move: How to Handle the Transition to ESA ... 103
... 9.1 Success Factor No. 1: Decide Where You're Going and Why You're Going There ... 103
... 9.2 Success Factor No. 2: Do Not Try the "Great Leap Forward" Approach ... 105
... 9.3 Success Factor No. 3: Elevate the Status of Your IT Architecture ... 106
... 9.4 Success Factor No. 4: Change the Way You Manage Your Business Landscape Lifecycle ... 108
... 9.5 Success Factor No. 5: Don't Neglect Integration Architecture ... 109
... 9.6 Success Factor No. 6: Know Where You're Going, When You Get There, and How to Measure Whether the Trip Did You Any Good ... 110
10. ESA Checklist: The Steps to be Taken ... 113
... 10.1 Phase 1: Prepare ... 114
... 10.2 Phase 2: Plan ... 114
... 10.3 Phase 3: Execution ... 115
... 10.4 Phase 4: Organize ... 117
... 10.5 Breaking the Silo Stranglehold ... 118
Glossary ... 119
Index ... 123
