本书是作者多年采用面向服务架构(SOA)和面向服务技术建立IT治理控制项目的工程实践经验总结,清晰地介绍了如何构建SOA治理,并通过具体步骤引导读者进行工业治理实践。通过研究实例,本书论述了如何定义和放置规则、组织角色、流程、标准和业务度量,、直观地描述了角色、流程、规则和项目阶段之间的交叉引用和映射。通过学习本书,读者能够用这些治理控制去创建自己的用户SOA 治理系统。
Stephen G.BennettStephen G.Bennett currently holds the role of Senior Enterprise Architect at Oracle,prior to which he worked with BEA where he was the Americas SOA Practice Lead within BEA`s consulting division.Stephen is a 25-year experienced manager and technologist,with a wide range of leadership,architecture,and implementation experience around SOA and Cloud Computing gained in high profi le environments.Before becoming a consultant,Stephen spent 12 years in the investment banking industry delivering global trading systems.
Alongside many white papers and magazine articles,Stephen`s previous literary efforts include the book Silver Clouds,Dark Linings: A Concise Guide to Cloud Computing(Prentice Hall 2010).Stephen is a regular speaker at executive events and conferences on topics such as SOA adoption,service engineering,SOA Governance,service-oriented architecture,and cloud computing.Stephen has been involved in multiple standards efforts around SOA and Enterprise Architecture.Stephen has co-chaired a number of working groups within the Open Group organization around SOA Governance and TOGAF/SOA.
Thomas ErlThomas Erl is the founder of SOASchool.com? and CloudSchool.com?,as part of Arcitura Education Inc.Thomas has been the world`s top-selling SOA author for more than fi ve years and is the series editor of the Prentice Hall Service-Oriented Computing Series from Thomas Erl,as well as the editor of the SOA Magazine.With more than 140,000 copies in print world-wide,his seven published books have become international bestsellers and have been formally endorsed by senior members of major IT organizations,such as IBM,Microsoft,Oracle,Intel,Accenture,IEEE,MITRE,SAP,CISCO,and HP.In cooperation with SOASchool.com? and CloudSchool.com?,Thomas has helped develop curricula for the internationally recognized SOA Certifi ed Professional(SOACP)and Cloud Certifi ed Professional(CCP)accreditation programs,which have established a series of formal,vendor-neutral industry certifi cations.
Thomas is the founding member of the SOA Manifesto Working Group(www.soamanifesto.org),founder of the APQC Service-Orientation Maturity Model(SOMM)initiative,co-chair of the SOA Education Committee,and he further oversees the SOAPatterns.org initiative,a community site dedicated to the on-going development of a master patterns catalog for service-oriented computing.
Thomas has toured more than 20 countries as a speaker and instructor for public and private events,and regularly participates in SOA Symposium(www.soasymposium.com)and Gartner conferences.More than 100 articles and interviews by Thomas have been published in numerous publications,including the Wall Street Journal and CIO Magazine.
Clive Gee,Ph.D.
After developing an interest in computers while studying for a Ph.D.in Theoretical Physics from the University of Stirling,Scotland,Clive joined IBM United Kingdom in 1976 to pursue a career in the emerging IT industry.He worked initially in telecommunications and offi ce automation,and then moved to the fi eld of application development in the 1980s where he spent the remainder of his career.
An early proponent of Object Orientation,he was one of the founders of IBM`s European Object Technology Practice,where he worked on major client application development projects and internal CASE tool development.In 1997 Clive moved to the United States,joining IBM`s North American Object Technology Practice as a consultant architect,working on major client projects in the Banking,Retail,Telecommunication,and Transportation Industries.During his tenure with IBM he worked on developing solutions that ranged from wireless telecommunications network infrastructure to mobile applications for the airline industry.
As well as being closely involved in the technical architecture and design of complex IT solutions,Clive developed an interest in the fi eld of software engineering,improving the IT application design and development process by adopting production management techniques such as those used by the engineering and manufacturing industries.One of the very fi rst IBM architects to work on SOA,Clive was involved with most of IBM`s fl agship SOA engagements,initially as a Solution or Lead Architect,then increasingly as a specialist in SOA governance,where he is considered to be one of IBM`s pre-eminent worldwide practitioners.Clive worked on numerous major client projects in the USA,Canada,Latin America,Europe,Japan,and Aus
Foreword by Massimo Pezzini
Foreword by Roberto Medrano
CHAPTER 1:Introduction
1.1 About this Book
Who this Book is For
What this Book Does Not Cover
This is Not a Book About SOA Management
This is Not a Book About Cloud Computing Governance
1.2 Recommended Reading
1.3 How this Book is Organized
Part I:Fundamentals
Chapter 3:Service-Oriented Computing Fundamentals
Chapter 4:SOA Planning Fundamentals
Chapter 5:SOA Project Fundamentals
Chapter 6:Understanding SOA Governance
Part II:Project Governance
Chapter 7:Governing SOA Projects
Chapter 8:Governing Service Analysis Stages
Chapter 9:Governing Service Design and Development Stages
Chapter 10:Governing Service Testing and Deployment Stages
Chapter 11:Governing Service Usage,Discovery,and Versioning Stages
Part III:Strategic Governance
Chapter 12:Service Information and Service Policy Governance
Chapter 13:SOA Governance Vitality
Chapter 14:SOA Governance Technology
Part IV:Appendices
Appendix A:Case Study Conclusion
Appendix B:Master Reference Diagrams for Organizational Roles
Appendix C:Service-Orientation Principles Reference
Appendix D:SOA Design Patterns Reference
Appendix E:The Annotated SOA Manifesto
Appendix F:Versioning Fundamentals for Web Services and REST Services
Appendix G:Mapping Service-Orientation to RUP
Appendix H:Additional Resources
1.4 Symbols,Figures,and Style Conventions
Symbol Legend
Mapping Diagrams
SOA Principles & Patterns Sections
Capitalization
1.5 Additional Information
Updates,Errata,and Resources(www.soabooks.com
Master Glossary(www.soaglossary.com
Referenced Specifications(www.soaspecs.com
SOASchool.com? SOA Certified Professional(SOACP
CloudSchool.com? Cloud Certified Professional(CCP
The SOA Magazine(www.soamag.com
Notification Service
CHAPTER 2:Case Study Background
2.1 How Case Studies are Used
2.2 Raysmoore Corporation
History
IT Environment
Business Goals and Obstacles
2.3 Case Study Continuation
PART I:FUNDAMENTALS
CHAPTER 3:Service-Oriented Computing Fundamentals
3.1 Basic Terminology
Service-Oriented Computing
Service-Orientation
Service-Oriented Architecture(SOA
Services
Services as Components
Services as Web Services
Services as REST Services
SOA Manifesto
Cloud Computing
IT Resources
Cloud
On-Premise
Cloud Deployment Models
Cloud Consumers and Cloud Providers
Cloud Delivery Models
Service Models
Agnostic Logic and Non-Agnostic Logic
Service Composition
Service Inventory
Service Portfolio
Service Candidate
Service Contract
Service-Related Granularity
SOA Design Patterns
3.2 Further Reading
CHAPTER 4:SOA Planning Fundamentals
4.1 The Four Pillars of Service-Orientation
Teamwork
Education
Discipline
Balanced Scope
4.2 Levels of Organizational Maturity
Service Neutral Level
Service Aware Level
Service Capable Level
Business Aligned Level
Business Driven Level
Service Ineffectual Level
Service Aggressive Level
4.3 SOA Funding Models
Platform(Service Inventory)Funding
Project Funding Model(Platform
Central Funding Model(Platform
Usage Based Funding Model(Platform
Service Funding
Project Funding Model(Service
Central Funding Model(Service
Hybrid Funding Model(Service
Usage Based Funding Model(Service
CHAPTER 5:SOA Project Fundamentals
5.1 Project and Lifecycle Stages
SOA Adoption Planning
Service Inventory Analysis
Service-Oriented Analysis(Service Modeling
Service-Oriented Design(Service Contract
Service Logic Design
Service Development
Service Testing
Service Deployment and Maintenance
Service Usage and Monitoring
Service Discovery
Service Versioning and Retirement
5.2 Organizational Roles
Service Analyst
Service Architect
Service Developer
Service Custodian
Cloud Service Owner
Service Administrator
Cloud Resource Administrator
Schema Custodian
Policy Custodian
Service Registry Custodian
Technical Communications Specialist
Enterprise Architect
Enterprise Design Standards Custodian(and Auditor
SOA Quality Assurance Specialist
SOA Security Specialist
SOA Governance Specialist
Other Roles
Educator
Business Analyst
Data Architect
Technology Architect
Cloud Technology Professional
Cloud Architect
Cloud Security Specialist
Cloud Governance Specialist
IT Manager
5.3 Service Profiles
Service-Level Profile Structure
Capability Profile Structure
Additional Considerations
Customizing Service Profiles
Service Profiles and Service Registries
Service Profiles and Service Catalogs
Service Profiles and Service Architecture
CHAPTER 6:Understanding SOA Governance
6.1 Governance 101
The Scope of Governance
Governance and Methodology
Governance and Management
Methodology and Management
Comparisons
The Building Blocks of a Governance System
Precepts
People(Roles
Processes
Metrics
Governance and SOA
6.2 The SOA Governance Program Office(SGPO
6.3 SGPO Jurisdiction Models
Centralized Enterprise SGPO
Centralized Domain SGPO
Federated Domain SGPOs
Independent Domain SGPOs
6.4 The SOA Governance Program
Step 1:Assessing the Enterprise(or Domain
Current Governance Practices and Management Styles
SOA Initiative Maturity
Current Organizational Model
Current and Planned Balance of On-Premise and Cloud-based IT Resources
Step 2:Planning and Building the SOA Governance Program
SOA Governance Precepts
SOA Governance Processes
SOA Governance Roles
Additional Components
Step 3:Running the SOA Governance Program(Best Practices and Common Pitfalls
Collect the Right Metrics and Have the Right People Use Them
Provide Transparency and Foster Collaboration
Ensure Consistency and Reliability
Compliance and Incentives
Education and Communication
Common Pitfalls
PART II:PROJECT GOVERNANCE
CHAPTER 7:Governing SOA Projects
7.1 Overview
Precepts,Processes,and People(Roles)Sections
7.2 General Governance Controls
Precepts
Service Profile Standards
Service Information Precepts
Service Policy Precepts
Logical Domain Precepts
Security Control Precepts
SOA Governance Technology Standards
Metrics
Cost Metrics
Standards-related Precept Metrics
Threshold Metrics
Vitality Metrics
Case Study Example
7.3 Governing SOA Adoption Planning
Precepts
Preferred Adoption Scope Definition
Organizational Maturity Criteria Definition
Standardized Funding Model
Processes
Organizational Governance Maturity Assessment
Adoption Impact Analysis
Adoption Risk Assessment
People(Roles
Enterprise Architect
SOA Governance Specialist
Case Study Example
CHAPTER 8:Governing Service Analysis Stages
8.1 Governing Service Inventory Analysis
Precepts
Service Inventory Scope Definition
Processes
Business Requirements Prioritization
People(Roles
Service Analyst
Enterprise Design Standards Custodian
Enterprise Architect
SOA Governance Specialist
Case Study Example
8.2 Governing Service-Oriented Analysis(Service Modeling
Precepts
Service and Capability Candidate Naming Standards
Service Normalization
Service Candidate Versioning Standards
Processes
Service Candidate Review
People(Roles
Service Analyst
Service Architect
Enterprise Design Standards Custodian
Enterprise Architect
SOA Governance Specialist
Case Study Example
CHAPTER 9:Governing Service Design and Development Stages
9.1 Governing Service-Oriented Design(Service Contract
Precepts
Schema Design Standards
Service Contract Design Standards
Service-Orientation Contract Design Standards
SLA Template
Processes
Service Contract Design Review
Service Contract Registration
People(Roles
Service Architect
Schema Custodian
Policy Custodian
Technical Communications Specialist
Enterprise Design Standards Custodian
Enterprise Architect
SOA Security Specialist
SOA Governance Specialist
Case Study Example
9.2 Governing Service Logic Design
Precepts
Service Logic Design Standards
Service-Orientation Architecture Design Standards
Processes
Service Access Control
Service Logic Design Review
Legal Data Audit
People(Roles
Service Architect
Enterprise Design Standards Custodian
Enterprise Architect
SOA Security Specialist
SOA Governance Specialist
Case Study Example
9.3 Governing Service Development
Precepts
Service Logic Programming Standards
Custom Development Technology Standards
Processes
Service Logic Code Review
People(Roles
Service Developer
Enterprise Design Standards Custodian
Enterprise Architect
SOA Governance Specialist
Case Study Example
CHAPTER 10:Governing Service T
I
magine driving along a winding road. On the one side you have sheets of blasted rock that lead up into a mountain range, on the other side you have a steep cliff, with a freefall of several hundred feet, leading into a deep ocean. The faster you drive, the sooner you will reach your destination, but the more risky the drive. For example, you may need to swerve to avoid obstacles or adjust quickly to volatile weather conditions— risk factors that are elevated when moving at higher speeds. But, it`s still tempting, because the sooner you reach that destination, the more successful your drive will be considered, by everyone.
When we design a roadmap for our SOA initiative, we lay out a direction that determines our route and a schedule that determines our rate of speed. We try to anticipate and plan for obstacles, but we know to expect the unexpected. With the necessary stakeholder support and .nancing in place (let`s call it our "fuel in the tank"), we determine it`s time to hit the road.
But before we do, let`s go back to that decision point about choosing our route. A winding road with an open cliff constantly at our side represents the continuous risk of plunging over the edge, especially when maneuvering to avoid unanticipated obstacles. Such a road requires minimal work to put together and therefore a perceived opportunity to reach our goals in less time and with less expense. But, there`s that risk factor we need to consider, especially of concern after we take a preliminary look over the edge to see the accumulated wreckage of the many vehicles that previously, unsuccessfully attempted this drive. We therefore reconsider.
The best analogy of IT governance I encountered was by Leo Shuster who, in his pod-cast interview for the International SOA + Cloud Symposium, stated that governance is like guardrails along a road. A governed roadmap is one that has, from beginning to end, controls that establish rules that we must comply with and parameters that we must function within, as we progress throughout SOA project stages.
In other words, we need to build a road with solid guardrails that keep our initiative from veering off its path. For many organizations, this realization was the result of losing signi.cant investments to the heaps of wreckage already .oating in the ocean below the cliffs of unregulated project plans. It has been a painful lesson that has, for some,
1.1 About this Book
shaken their very con.dence in SOA. Fortunately, out of the numerous projects and efforts that have gone into establishing SOA governance as its own .eld of expertise, we now have a set of proven rules and parameters that provide a stable and healthy starting point for organizations to create successful SOA governance systems.
This book is the accumulated result of many years of practice and insight provided by SOA experts, IT governance experts, and technology innovation experts. It`s about the nuts and bolts of guardrail construction, maintenance, and enforcement. It`s also about helping us understand that establishing a sound system of governance requires an investment and an expected return on that investment. What we put into creating those guardrails will protect the greater investment we put into the overall SOA projects that will venture down that road.
Finally, this book is about highlighting the fact that once those guardrails are in place, that governed road we built can be used over and over again, each time allowing us to drive faster, without compromising our safety. Establishing a mature system of SOA governance within our IT enterprise gives us a form of regulated agility—a robust state whereby we can rapidly respond to on-going business change without assuming unnecessary risk.
—Thomas Erl
1.1 About this Book
This book has a very simple objective. Its focus is solely on IT governance as it applies to the adoption of SOA and service-orientation. To that effect, it makes a clear distinction between governance and management and methodology, and then proceeds to establish a generic governance system, comprised of a series of common precepts, processes, and associated organizational roles. It further addresses governance topics that pertain to speci.c forms of service technology innovation, including cloud computing.
The purpose of this book is to give SOA practitioners a concrete framework that can be further augmented and extended into custom SOA governance systems and programs.
Who this Book is For
There is much discussion about the role of the SOA Governance Specialist in the upcoming chapters. While this type of IT professional will need to become an expert at everything covered in this book, the actual intended audience is much broader.
Speci.cally, this book will be useful to:
.
IT managers and project managers that need to understand how a governance system can and should be incorporated into an SOA initiative, its impacts, requirements, and bene. ts. .
Architects and analysts who will be in the midst of SOA governance activities, including contribution to governance precepts and standards, as well as participation in review and audit processes.
.
Enterprise architects and those involved with the authoring and maintenance of custom design standards. These individuals will be part of governance activity in almost every SOA project stage.
.
Business analysts that are part of analysis teams for service modeling and for the de.nition of enterprise business models, such as business dictionaries, ontologies, and business processes.
.
Developers, administrators, quality assurance professionals, and security specialists, who all will .nd themselves participating in or being affected by various SOA governance controls.
.
Cloud computing professionals interested in learning about IT governance considerations speci.c to SOA and service-oriented solutions that encompass one or more cloud-based services or resources.
What this Book Does Not Cover
This is Not a Book About SOA Management
SOA governance has historically often been mistaken or confused with SOA management. This is a book about SOA governance only, although related management requirements and project stages are occasionally referenced. See Chapter 6 for an explanation that helps clarify the difference between governance, management, and methodology.
This is Not a Book About Cloud Computing Governance
Wherever appropriate, this book references SOA governance considerations that can pertain to cloud computing. However, it is important to note that this is not a general book about cloud computing governance—only considerations speci.c to applying service-orientation within cloud-based environments are mentioned. General cloud computing governance is a much broader topic that delves beyond the service level, into the various mechanisms and IT resources that can comprise cloud environments.
1.2 Recommended Reading
1.2 Recommended Reading
To further ensure that you have a clear understanding of key terms used and referenced in the upcoming chapters, you can visit the online master glossary for this book series at www.soaglossary.com to look up de.nitions for terms that may not be fully described in this book.
Even if you are an experienced SOA practitioner, we suggest you take the time to have a look at this online resource. A great deal of ambiguity has surrounded SOA and service-oriented computing and these explanations and de.nitions will ensure that you fully understand key terms and concepts in relation to this book and the book series as a whole.
Here are some recommendations for additional books that elaborate on some of the topics covered by this title:
.
SOA Principles of Service Design – A comprehensive documentation of the service-orientation design paradigm with full descriptions of all of the principles referenced in this book.
.
SOA Design Patterns – This is the of.cial SOA design patterns catalog containing descriptions and examples for most of the patterns referenced in this book. You can also look up concise descriptions for these patterns at www.soapatterns.org and in Appendix D.
.
Service-Oriented Architecture: Concepts, Technology, and Design – The coverage of service-oriented analysis and design processes in this title supplements this book with more detailed methodology-related topics.
.
The title Web Service Contract Design & Versioning for SOA provides a great deal of technical content that may not be relevant to governance topics, except for those that aim to establish technical design and development standards. However, this book does include four chapters dedicated to Web service contract versioning topics that will be useful when dealing with governance precepts associated with the Service Versioning and Retirement project stage (see Chapter 11 and Appendix F).
.
SOA with REST – This book documents the convergence of REST and SOA by establishing how REST services can be realized in support of service-orientation. Salient topics are reinforced with comprehensive case studies using modern REST frameworks in combination with contemporary SOA models, patterns, practices, and concepts.
For the latest information regarding these and other titles in the Prentice Hall Service-Oriented Computing Series from Thomas Erl, visit www.soabooks.com.
1.3 How this Book is Organized
This book begins with Chapters 1 and 2 providing introductory content and case study background information respectively. All subsequent chapters are grouped into the following parts:
.
Part I: Fundamentals
.
Part II: Project Governance
.
Part III: Strategic Governance
.
Part IV: Appendices
Part I: Fundamentals
The .rst four chapters cover various introductory topics in preparation for the chapters in Parts II and III.
Chapter 3: Service-Oriented Computing Fundamentals
This chap
很有用的资料
资料很好,速度也快,学习技术很英文的好东西
收藏起来,慢慢看
好