Management SOA actually solves a small part of a problem. Questions of management SAO Not the simple. It is necessary to have huge experience, what in it well to understand

Stating the obvious, the term "governance" is not newly created in the technology world and has a very broad connotation across the domains it is used in. While I generally agree with David's comments and Nick's observations, I think we are perhaps applying too broad a brush in what we mean by governance. For example, many of the activities and perspectives discussed above are really part of the discipline one would use as part of the management and control in each of the stages, e.g. analysis, design, development, etc. One could argue we've always had to apply a similar discipline in every major transformation and technology adoption initiative without getting wrapped around the term "governance". So, it's not just about SOA. The fact that we are trying to shrink-wrap such good practices as a "tool in a box" is causing all the confusion. IMHO we should separate what we mean by operational governance which is what many of the tools provide (or try to), vs. all the other aspects of applying proper control to the life cycle of the SOA initiative, which arguably is simply (or not so simply) about maturity in management and execution. Let's not bundle these under SOA governance. It might perhaps clarify the tool capability landscape, and allow us to focus on these other important activities in their proper light.

Stating the obvious, the term "governance" is not newly created in the technology world and has a very broad connotation across the domains it is used in. While I generally agree with David's comments and Nick's observations, I think we are perhaps applying too broad a brush in what we mean by governance. For example, many of the activities and perspectives discussed above are really part of the discipline one would use as part of the management and control best-practices in each of the stages, e.g. analysis, design, development, etc. One could argue we've always had to apply a similar discipline in every major transformation and technology adoption initiative without getting wrapped around the term "governance". So, it's not just about SOA.

The fact that we are trying to shrink-wrap such good practices as a "tool in a box" is causing all the confusion. IMHO we should separate what we mean by operational governance which is what many of the tools provide (or try to), vs. all other aspects of applying proper control to the life cycle of the SOA initiative, which arguably is simply (or not so simply) about maturity in management and execution. Let's not bundle these under SOA governance. It might perhaps clarify the tool capability landscape, and allow us to focus on these other important activities in their proper light.

Dear David,

This piece of information on SOA Governance was great. I have a couple of doubts though. Specifically, I would like to know what you (of Nick) wanted to say with "service level expectations" and "compensation definition" on the Activity "Event and Schema design" on the table presented.

Thanks in advance for your time and attention.

Best Regards,

Bruno