The order I see is, from highest to lowest: B, E, D, C, A
C & D could be swapped, and B & E are pretty close too. A, the one that I personally think is most critical for successful long term adoption of SOA, is all too often the lowest priority, by far. -tb On Jul 24, 2008, at 10:47 PM, jeffrschneider wrote: > In what order do you think enterprises are currently prioritizing > these areas, example: (B, E, A, C, D)? > > > A. Plan Time Governance - Ensuring that business initiatives aligned > with key I.T. services, avoiding silos while gaining cross > organizational funding, etc. > > B. Design Time Governance - Utilizing registries, repositories, > validation frameworks, etc. to promote best practices in schema and > contract design enabling reuse, search, verify, etc. > > C. Pre-Release Governance - Validating solutions meet pre-production > needs (highly available, secure, fast response times, new version > doesn't break existing consumers, etc.) > > D. Run Time Governance - Ensuring that the services in production are > monitored, adhere to SLA's, leverage run time policies, etc. > > E. Infrastructure Governance - Verify that the infrastructure used > (ESB's, Registries, Mediation Devices, etc.) adhere to the corporate > standards. > > > > > > ------------------------------------ > > Yahoo! Groups Links > > >
