SOA Governance

by Erl, Thomas; Bennett, Stephen G.; Carlyle, Benjamin; Gee, Clive; Laird, Robert; Manes, Anne Thomas; Moores, Robert; Tost, Andre

• ISBN13: 9780132478281
• ISBN10: 0132478285
• Edition: 1st
• Copyright: 2011-04-05
• Publisher: PEARSO

Summary

The Definitive Guide to Governing Shared Services and SOA Projects

 

SOA Governance: Governing Shared Services On-Premise and in the Cloud is the result of a multi-year project to collect proven industry practices for establishing IT governance controls specific to the adoption of SOA and service-orientation. Authored by world-renowned experts in the fields of SOA, IT governance, and cloud computing, this comprehensive book provides clear direction as to what does and does not constitute SOA governance and then steps the reader through the most important industry governance practices, as they pertain to individual SOA project lifecycle stages.

 

With a consistent, vendor-neutral focus, and with the help of case study examples, the authors demonstrate how to define and position precepts, organizational roles, processes, standards, and metrics. Readers benefit from thorough and visually depicted cross-references and mapping between roles, processes, precepts, and project stages, enabling them to fully explore dynamics and dependencies and thereby learn how to use these governance controls to create their own custom SOA governance systems.

 

This important title will be valuable to every practitioner concerned with making SOA work, including senior IT managers, project managers, architects, analysts, developers, administrators, QA professionals, security specialists, and cloud computing professionals.

 

Topic Areas

• Defining SOA governance
• Establishing an SOA governance office and program
• Working with proven SOA governance precepts and processes
• Identifying organizational roles and relating them to SOA governance
• Associating design-time and runtime SOA project stages with SOA governance controls
• Governance considerations specific to shared services
• Roles, precepts, and factors specific to cloud-based services
• Understanding and categorizing SOA governance products and technologies
• Applying governance controls as early as the planning stages and measuring their success in subsequent stages
• Using vitality triggers to govern shared services on an on-going basis
• SOA governance controls that pertain to business information documents and policies

Author Biography

Stephen 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 profile 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 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 five 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 Certified Professional (SOACP) and Cloud Certified Professional (CCP) accreditation programs, which have established a series of formal, vendor-neutral industry certifications. 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.

 

After developing an interest in computers while studying for a Ph.D. in Theoretical Physics from the University of Stirling, Scotland, Clive Gee joined IBM United Kingdom in 1976 to pursue a career in the emerging IT industry. He worked initially in telecommunications and office automation, and then moved to the field 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 field 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 first IBM architects to work on SOA, Clive was involved with most of IBM’s flagship 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 Australia. Semi-retired in 2008, Clive has since returned to live in the UK’s Northern Isles. He is a co-author of the book SOA Governance: Achieving and Sustaining Business and IT Agility (IBM Press 2008).

 

Robert Laird is the lead architect of the IBM Software Group in areas of SOA governance and SOA policy; he currently leads the automation of the SOA Policy Lifecycle. Prior to that, Robert co-authored the SOA Governance and Management Method (SGMM) for usage of SOA governance capabilities and maturity assessment. Robert has several years of international consulting experience and was responsible for supporting and leading service-oriented architecture (SOA) governance and SOA architecture engagements for worldwide IBM customers.

 

With more than 20 years experience in the telecom industry at MCI and Verizon, Robert has been the MCI chief architect, leading the enterprise architecture group and has worked across the entire order-to-cash suite of applications. He led the development of the SOA based single stack strategy to simplify the multiple network and applications silos; he has driven the strategy, planning, and execution of MCI’s product development in the area of contact centers, IP/VPN, VOIP, IMS, and managed services; and, for OSS, he has led successful implementations to automate network provisioning, network restoration, and network management.

 

Prior to joining MCI, Robert worked as a consultant for American Management Systems (AMS) and Ideation, Inc. He has an MS and a BS degree in Computer Science from Purdue University and has been granted two patents in the area of telephony, with three patents pending in the area of computing. As well as speaking at various industry forums, Robert has written for The SOA Magazine, been quoted in CIO Insight, Telecommunications, Infoworld, and Computerworld, and has co-authored two books including SOA Governance (IBM Press 2008) and Executing SOA (IBM Press 2008).

 

Anne Thomas Manes is the Vice President and Research Director for Burton Group Application Platform Strategies. Her expertise includes SOA, web services, XML, governance, Java, application servers, super platforms, and application security. Prior to joining Burton Group, Anne was the Chief Technology Officer at Systinet, an SOA governance vendor (now part of HP) and Director of Market Innovation in Sun Microsystems’s software group. With 28 years of experience, Anne was named one of the 50 most powerful people in networking 2002 by Network World and among the “Power 100 IT Leaders,” by Enterprise Systems Journal.

 

Anne has authored Web Services: A Manager ’ s Guide (Addison-Wesley, 2003) and contributed the foreword for the new book Next Generation SOA (Prentice Hall, 2011). Anne has also participated in Web services standards development efforts at the W3C, OASIS, WS-I, and JCP.

 

Robert Schneider is a Partner at WiseClouds, LLC. WiseClouds offers vendor-neutral, unbiased consulting and training services that help customers understand and manage cloud computing business concerns, select the right mixture of enabling technologies, and identify and deploy the ideal configuration required.

 

Robert has provided database optimization, distributed computing, and other technical expertise to a wide variety of enterprises in the financial, technology, and public sectors. Clients have included Amazon, JP Morgan Chase & Co, VISA, HP, S.W.I.F.T., and numerous governments such as the United States, Brazil, Malaysia, Mexico, Australia, and the United Kingdom.

 

Robert has written six books and numerous articles on database technology and other complex topics such as cloud computing, and SOA. Robert is a frequent organizer and presenter at technology industry events, worldwide.

 

Leo Shuster is a seasoned IT professional. He has directed Enterprise Architecture and SOA strategy and execution for a number of organizations including Nationwide Insurance, National City Corporation, Ohio Savings Bank, and Progressive Insurance. Leo holds an MS in Computer Science and Engineering from Case Western Reserve University and an MBA from Cleveland State University. Thus far, in his 15 year IT career, Leo has held a variety of roles including Director, Manager, Team Lead, Project Manager, Architect, and Developer. Leo has presented on Enterprise Architecture, SOA, and related topics for groups of all sizes at a variety of industry events and conferences. He is passionate about technology and regularly blogs about advanced software architecture issues at leoshuster.blogspot.com.

 

Andre Tost works as a Senior Technical Staff Member in the IBM Software Group where he assists IBM’s customers in establishing service-oriented architectures. His special focus is on Web services, Enterprise Service Bus technology, and SOA governance. Before his current assignment, Andre spent ten years in various partner enablement, development, and architectural roles in IBM software development. Andre has spoken at industry conferences worldwide on topics related to SOA and is a frequent publisher of articles and papers. He is also a co-author of several books on Web services and related technologies including Web Service Contract Design and Versioning for SOA (Prentice Hall 2008). Originally from Germany, he now lives and works in Rochester, Minnesota.

 

Chris Venable is an architect and member of the SOA Center of Competency at Wal-Mart Stores, Inc. He has 16 years of experience in the IT industry with the past nine focused on SOA, data integration, and other modern software engineering practices.

 

Current areas of interest include business architecture, event processing, variation analysis, and conceptual modeling.

Table of Contents

Foreword by Massimo Pezzini     xxxi

Foreword by Roberto Medrano     xxxiii

Acknowledgments     xxxv

C HAPTER 1: Introduction     1

1.1 About this Book     3

Who this Book is For     3

What this Book Does Not Cover      4

This is Not a Book About SOA Management      4

This is Not a Book About Cloud Computing Governance       4

1.2 Recommended Reading     5

1.3 How this Book is Organized     6

Part I: Fundamentals     6

Part II: Project Governance     7

Part III: Strategic Governance     10

Part IV: Appendices     11

1.4 Symbols, Figures, and Style Conventions     12

Symbol Legend     12

Mapping Diagrams     12

SOA Principles & Patterns Sections     13

Capitalization     14

1.5 Additional Information     14

Updates, Errata, and Resources (www.soabooks.com)      14

Master Glossary (www.soaglossary.com)      15

Referenced Specifications (www.soaspecs.com)      15

SOASchool.com SOA Certified Professional (SOACP)      15

CloudSchool.com Cloud Certified Professional (CCP)      15

The SOA Magazine (www.soamag.com)      15

Notification Service     16

C HAPTER 2: Case Study Background     17

2.1 How Case Studies are Used     18

2.2 Raysmoore Corporation     18

History     18

IT Environment     18

Business Goals and Obstacles     19

2.3 Case Study Continuation     20

PART I: FUNDAMENTALS

C HAPTER 3: Service-Oriented Computing Fundamentals     23

3.1 Basic Terminology     24

Service-Oriented Computing     25

Service-Orientation     26

Service-Oriented Architecture (SOA)      29

Services     31

Services as Components      32

Services as Web Services      32

Services as REST Services      34

SOA Manifesto     34

Cloud Computing     35

IT Resources     35

Cloud     36

On-Premise     37

Cloud Deployment Models     37

Cloud Consumers and Cloud Providers     38

Cloud Delivery Models      38

Service Models     38

Agnostic Logic and Non-Agnostic Logic      39

Service Composition     40

Service Inventory     41

Service Portfolio     41

Service Candidate      42

Service Contract     43

Service-Related Granularity     44

SOA Design Patterns     46

3.2 Further Reading     47

C HAPTER 4: SOA Planning Fundamentals     49

4.1 The Four Pillars of Service-Orientation     51

Teamwork     52

Education      52

Discipline     52

Balanced Scope     53

4.2 Levels of Organizational Maturity     56

Service Neutral Level      .57

Service Aware Level     57

Service Capable Level     57

Business Aligned Level     58

Business Driven Level     58

Service Ineffectual Level     58

Service Aggressive Level     59

4.3 SOA Funding Models     60

Platform (Service Inventory) Funding     60

Project Funding Model (Platform)       61

Central Funding Model (Platform)       64

Usage Based Funding Model (Platform)       66

Service Funding     69

Project Funding Model (Service)       69

Central Funding Model (Service)       71

Hybrid Funding Model (Service)       72

Usage Based Funding Model (Service)       74

C HAPTER 5: SOA Project Fundamentals     79

5.1 Project and Lifecycle Stages     81

SOA Adoption Planning     82

Service Inventory Analysis     82

Service-Oriented Analysis (Service Modeling)      84

Service-Oriented Design (Service Contract)      85

Service Logic Design     87

Service Development     87

Service Testing     88

Service Deployment and Maintenance     89

Service Usage and Monitoring      90

Service Discovery     90

Service Versioning and Retirement      91

5.2 Organizational Roles     92

Service Analyst     96

Service Architect     96

Service Developer     97

Service Custodian     98

Cloud Service Owner      98

Service Administrator     100

Cloud Resource Administrator     100

Schema Custodian     102

Policy Custodian     104

Service Registry Custodian     105

Technical Communications Specialist      105

Enterprise Architect      106

Enterprise Design Standards Custodian (and Auditor)      107

SOA Quality Assurance Specialist      109

SOA Security Specialist     110

SOA Governance Specialist     111

Other Roles     112

Educator       112

Business Analyst       113

Data Architect      113

Technology Architect       113

Cloud Technology Professional       114

Cloud Architect       114

Cloud Security Specialist       114

Cloud Governance Specialist      114

IT Manager      115

5.3 Service Profiles     115

Service-Level Profile Structure     117

Capability Profile Structure     118

Additional Considerations     119

Customizing Service Profiles       119

Service Profiles and Service Registries       119

Service Profiles and Service Catalogs      119

Service Profiles and Service Architecture      120

C HAPTER 6: Understanding SOA Governance     121

6.1 Governance 101     122

The Scope of Governance     123

Governance and Methodology       124

Governance and Management      124

Methodology and Management      125

Comparisons      125

The Building Blocks of a Governance System     127

Precepts       128

People (Roles)       128

Processes      129

Metrics      129

Governance and SOA     130

6.2 The SOA Governance Program Office (SGPO)      131

6.3 SGPO Jurisdiction Models     133

Centralized Enterprise SGPO      133

Centralized Domain SGPO      134

Federated Domain SGPOs      135

Independent Domain SGPOs      136

6.4 The SOA Governance Program     137

Step 1: Assessing the Enterprise (or Domain)      137

Current Governance Practices and Management Styles      138

SOA Initiative Maturity      138

Current Organizational Model      139

Current and Planned Balance of On-Premise and Cloud-based IT Resources       139

Step 2: Planning and Building the SOA Governance Program     139

SOA Governance Precepts      139

SOA Governance Processes      141

SOA Governance Roles      143

Additional Components      146

Step 3: Running the SOA Governance Program (Best Practices and Common Pitfalls)      146

Collect the Right Metrics and Have the Right People Use Them       146

Provide Transparency and Foster Collaboration      147

Ensure Consistency and Reliability      147

Compliance and Incentives      147

Education and Communication      148

Common Pitfalls      148

PART II: PROJECT GOVERNANCE

C HAPTER 7: Governing SOA Projects     153

7.1 Overview     155

Precepts, Processes, and People (Roles) Sections     156

7.2 General Governance Controls     157

Precepts     157

Service Profile Standards      157

Service Information Precepts      158

Service Policy Precepts       158

Logical Domain Precepts       159

Security Control Precepts       160

SOA Governance Technology Standards      163

Metrics     164

Cost Metrics      164

Standards-related Precept Metrics       165

Threshold Metrics      165

Vitality Metrics      166

Case Study Example     167

7.3 Governing SOA Adoption Planning     169

Precepts     169

Preferred Adoption Scope Definition      169

Organizational Maturity Criteria Definition      171

Standardized Funding Model      172

Processes     173

Organizational Governance Maturity Assessment      173

Adoption Impact Analysis       176

Adoption Risk Assessment      178

People (Roles)      179

Enterprise Architect       179

SOA Governance Specialist      181

Case Study Example     182

C HAPTER 8: Governing Service Analysis Stages     187

8.1 Governing Service Inventory Analysis     192

Precepts     193

Service Inventory Scope Definition       193

Processes     195

Business Requirements Prioritization      195

People (Roles)      197

Service Analyst      197

Enterprise Design Standards Custodian      198

Enterprise Architect       199

SOA Governance Specialist      200

Case Study Example     201

8.2 Governing Service-Oriented Analysis (Service Modeling)      206

Precepts     206

Service and Capability Candidate Naming Standards      206

Service Normalization      207

Service Candidate Versioning Standards      209

Processes     210

Service Candidate Review      210

People (Roles)      212

Service Analyst      212

Service Architect       213

Enterprise Design Standards Custodian      214

Enterprise Architect      215

SOA Governance Specialist      216

Case Study Example     217

C HAPTER 9: Governing Service Design and Development Stages     221

9.1 Governing Service-Oriented Design (Service Contract)      223

Precepts     223

Schema Design Standards      223

Service Contract Design Standards      225

Service-Orientation Contract Design Standards      228

SLA Template       229

Processes     231

Service Contract Design Review      231

Service Contract Registration      234

People (Roles)      236

Service Architect       236

Schema Custodian      237

Policy Custodian      238

Technical Communications Specialist      239

Enterprise Design Standards Custodian      241

Enterprise Architect       242

SOA Security Specialist      243

SOA Governance Specialist       245

Case Study Example     246

9.2 Governing Service Logic Design     249

Precepts     249

Service Logic Design Standards      249

Service-Orientation Architecture Design Standards      252

Processes     253

Service Access Control       253

Service Logic Design Review       255

Legal Data Audit      257

People (Roles)      259

Service Architect       259

Enterprise Design Standards Custodian      260

Enterprise Architect       261

SOA Security Specialist       262

SOA Governance Specialist       263

Case Study Example     265

9.3 Governing Service Development     267

Precepts     267

Service Logic Programming Standards       267

Custom Development Technology Standards      268

Processes     270

Service Logic Code Review      270

People (Roles)      272

Service Developer      272

Enterprise Design Standards Custodian      273

Enterprise Architect      274

SOA Governance Specialist      275

Case Study Example     276

C HAPTER 10: Governing Service Testing and Deployment Stages     277

10.1 Governing Service Testing     278

Precepts     279

Testing Tool Standards      279

Testing Parameter Standards      280

Service Testing Standards      281

Cloud Integration Testing Standards      283

Test Data Usage Guidelines      285

Processes     286

Service Test Results Review       286

People (Roles)      287

Service Administrator      287

Cloud Resource Administrator      288

Enterprise Architect       289

SOA Quality Assurance Specialist      290

SOA Security Specialist      291

SOA Governance Specialist       292

Case Study Example     294

10.2 Governing Service Deployment and Maintenance     298

Precepts     298

Production Deployment and Maintenance Standards      298

Processes     301

Service Certification Review      301

Service Maintenance Review      303

People (Roles)      304

Service Administrator       304

Cloud Resource Administrator      305

Service Custodian      307

Enterprise Architect       308

SOA Quality Assurance Specialist       309

SOA Security Specialist      310

SOA Governance Specialist      311

Case Study Example     312

Chapter 11: Governing Service Usage, Discovery, and Versioning Stages     315

11.1 Governing Service Usage and Monitoring     317

Precepts     317

Runtime Service Usage Thresholds      317

Service Vitality Triggers      320

Processes     323

Service Vitality Review      323

People (Roles)      325

Enterprise Architect       325

Service Architect       326

Service Administrator      327

Cloud Resource Administrator      328

Service Custodian      329

SOA Security Specialist       331

SOA Governance Specialist       332

Case Study Example     333

11.2 Governing Service Discovery     335

Precepts     335

Centralized Service Registry      335

Processes     337

Service Registry Access Control      337

Service Registry Record Review      339

Service Discovery      340

Shared Service Usage Request       342

Shared Service Modification Request      343

People (Roles)      345

Service Custodian      345

Service Registry Custodian      346

Technical Communications Specialist       348

SOA Governance Specialist       348

Case Study Example     350

11.3 Governing Service Versioning and Retirement     352

Precepts     352

Service Versioning Strategy      352

SLA Versioning Rules      354

Service Retirement Notification      356

Processes     357

Service Versioning      357

Service Retirement      359

People (Roles)      360

Enterprise Design Standards Custodian      60

Service Administrator       362

Cloud Resource Administrator      363

Schema Custodian       364

Policy Custodian      364

SOA Governance Specialist      365

PART III: STRATEGIC GOVERNANCE

C HAPTER 12: Service Information and Service Policy Governance     369

12.1 Overview     371

Service Data vs. Service Information     371

Policies 101     373

12.2 Governance Controls     375

Precepts     375

Enterprise Business Dictionary/Domain Business Dictionary      375

Service Metadata Standards      377

Enterprise Ontology/Domain Ontology       380

Business Policy Standards      382

Operational Policy Standards      384

Policy Centralization      386

Processes     389

Data Quality Review       389

Communications Quality Review      391

Information Alignment Audit       393

Policy Conflict Audit       395

People (Roles)      397

Business Analyst       397

Data Architect       399

Schema Custodian       399

Policy Custodian      401

Service Registry Custodian      402

Technical Communications Specialist       403

SOA Quality Assurance Specialist       405

SOA Governance Specialist      406

12.3 Guidelines for Establishing Enterprise Business Models     408

Establish a Service Information Governance Council     408

Assign Business Information Custodians     408

Assign Value to Business Information     409

Relate Service Information Governance to Master Data Management     409

C HAPTER 13: SOA Governance Vitality      411

13.1 Vitality Fundamentals     412

13.2 Vitality Triggers     414

Business vs. Technology Changes      415

Types of Vitality Triggers      416

Strategic Adjustments     416

Strategic Business Adjustment      416

Strategic IT Adjustment      417

Industry Shifts     417

Business Shift       417

Technology Shift       418

Metrics     418

Performance Metrics      419

Compliance Metrics      419

Organizational Shifts     419

Periodic     420

Milestone      420

Time      420

13.3 SOA Governance Vitality Process     421

Identify Activity     421

Assess Activity     422

Refresh Activity     422

Approve Activity     423

Communicate Activity     423

C HAPTER 14: SOA Governance Technology     425

14.1 Understanding SOA Governance Technology     426

SOA Governance Task Types     427

Manual Governance       427

Automated Governance       427

Design-time Governance      428

Runtime Governance      428

On-Premise Governance      428

Cloud Governance      428

Passive Governance      428

Active Governance      429

SOA Governance Technology Types     429

Administrative      429

Monitoring       429

Reporting      430

Enforcement      430

14.2 Common SOA Governance Technology Products     431

Service Registries     431

Task Types       432

Technology Types       432

SOA Project Stages      433

Repositories     433

Task Types      434

Technology Types      434

SOA Project Stages      435

Service Agents     435

Task Types      436

Technology Types      437

SOA Project Stages      437

Policy Systems     437

Task Types      438

Technology Types      438

SOA Project Stages      439

Quality Assurance Tools     439

Task Types      440

Technology Types      440

SOA Project Stages      441

SOA Management Suites     441

Other Tools and Products     442

Technical Editors and Graphic Tools      442

Content Sharing and Publishing Tools      442

Configuration Management Tools      443

Custom SOA Governance Solutions      443

14.3 Guidelines for Acquiring SOA Governance Technology     444

Acquisition Strategies     444

Single Vendor      444

Multiple Vendors      445

Open Source      446

Leased from Cloud Vendor      447

Best Practices     448

Establish Criteria Based on Your Specific Requirements      448

Investigate Customizability      448

Investigate APIs       448

Understand Both Initial and Long-Term Costs      448

Understand Actual Governance Support      449

Take the Time to Create a Quality RFP      449

PART IV: APPENDICES

A PPENDIX A: Case Study Conclusion     453

A PPENDIX B: Master Reference Diagrams for Organizational Roles     457

Service Analyst     458

Service Architect     459

Service Developer      460

Service Custodian     460

Service Administrator     461

Cloud Resource Administrator     462

Schema Custodian     463

Policy Custodian     464

Service Registry Custodian     465

Technical Communications Specialist     466

Enterprise Architect     467

Enterprise Design Standards Custodian (and Auditor)      468

SOA Quality Assurance Specialist      469

SOA Security Specialist     470

SOA Governance Specialist (precepts)      471

SOA Governance Specialist (processes)      472

A PPENDIX C: Service-Orientation Principles Reference     473

A PPENDIX D: SOA Design Patterns Reference     489

A PPENDIX E: The Annotated SOA Manifesto     577

A PPENDIX F: Versioning Fundamentals for Web Services and REST Services     591

F.1 Versioning Basics     593

Versioning Web Services     593

Versioning REST Services     594

Fine and Coarse-Grained Constraints     595

F.2 Versioning and Compatibility     596

Backwards Compatibility     596

Backwards Compatibility in Web Services      596

Backwards Compatibility in REST Services       597

Forwards Compatibility     599

Compatible Changes     602

Incompatible Changes     604

F.3 REST Service Compatibility Considerations     605

F.4 Version Identifiers     608

F.5 Versioning Strategies     611

The Strict Strategy (New Change, New Contract)      611

Pros and Cons      612

The Flexible Strategy (Backwards Compatibility)      612

Pros and Cons      613

The Loose Strategy (Backwards and Forwards Compatibility)      613

Pros and Cons      614

Summary Table     614

F.6 REST Service Versioning Considerations     615

A PPENDIX G: Mapping Service-Orientation to RUP     617

Compatibility of RUP and SOA     618

Overview of RUP (and MSOAM)      619

The Pillars of Service-Orientation and the RUP Principles     620

Breadth and Depth Roles and Role Mapping     623

Enterprise and Governance Roles     624

Mapping Service Delivery Project Stages to Disciplines     625

Mapping MSOAM Analysis and Design Stages to RUP Disciplines     626

Service-Orientation and RUP: Gaps     628

Related Reading     628

Bibliography     629

A PPENDIX H: Additional Resources     631

About the Authors     635

About the Contributors     641

About the Foreword Contributors     643

Index     645