In case anyone's interested, I posted some more comments on SOA
governance on my blog (http://www.biske.com/blog/). It has a
somewhat humorous anecdote on the differences in the political
process in California and Missouri.
What is worth discussing here, however, is the point I was trying to
make about SOA governance. Essentially, a company needs to define
what SOA governance means to them and make it fit their culture.
This is no different in adopting SOA in general, as each company has
to define what SOA means to them and what their goals are. While
there are broad, general goals for SOA that apply at any company and
broad governance goals that equally apply, there are plenty of
details left for companies to define.
If you agree with this, the next question would be what are the
patterns? Can corporate cultures be grouped into a small set and be
paired with a particular governance style? What are those culture
and styles? Does the same thing hold true for SOA in general? Are
there common corporate strategies and goals that map to particular
application of SOA? (note to Miko, my hope is that this would be
information that would come out of the efforts of the SOA Adoption
Blueprints TC)
If anyone has done some analysis on this and has some content that
can be shared, I think it would make for an interesting discussion!
-tb
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
