SOA Governance Explored
Comprehensive information from expert users, analysts, implementers and the media about all aspects of SOA Governance including rich presentations, research, analysis and guidance on SOA Governance
| SOA Governance: Applying Governance to Ensure the Long-term Benefits of SOA |
| A comprehensive look at SOA Governance's value to the enterprise. This exceptional report covers SOA Governance-specific business, technology and market issues. Highly recommended. From the Resource: "Most importantly, SOA Governance includes the initial considerations of establishing an appropriate corporate structure and placing the right individuals in the right roles to ensure that the governance effort is implemented and enforced in a cost effective manner." |
| Butler Group |
| To Manage or not to Manage? A Journey Through SOA Governance |
| One of our favorite looks into SOA Governance. This is a colorful, fast-moving presentation which covers SOA Governance's definition and role, design-time vs. runtime governance, best practices and much more. Highly recommended. From the Resource: "SOA Governance is: 1) Knowing what you have and how it's being used. 2) Organization, clearly defined roles, processes, and policies. 3) Shaping behavior to insure compliance with architectural guidelines and business objectives. 4) Assuring we avoid repeating the spaghetti [code] syndrome." |
| Roi Agababa, SRL Group |
| Governance is Key to SOA Success |
| A valuable look at the role of Governance in a successful SOA implementation. From the Resource: "Ironically, not having governance in a service-oriented architecture (SOA) helps to underscore the actual need for such a policy. Without the presence of governance, you will, quite simply, miss some of the key tenets of what you're attempting to do with SOA in the first place. You'll find that you don't have reusability of applications. You won't have a sufficient adoption of services, and you certainly will not have reusability of services. You will be saddled with a fragmented approach to your IT infrastructure that doesn't allow the interoperability you were looking for at the outset." |
| Richard Tews, Software Magazine |
« 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | next »
