Ashraf, the interpretation of Governrnce you posted matches the interpretation of SOA Governance in OASIS RM for SOA and RAF for SOA standards as 1:1. However, according to OASIS, Governance doc is a set of policies, i.e. SLA is nor really right place for the Governance. On the contrary, Governance stipulates what should be in the SLA and in which case. Continuing this line of logic, I state that the current versino of TOGAF 9's ADM inproprly defines the role and porition of Governance in the EA development process. YOu can find my interpretation of the SOA related ADM at: http://www.infoq.com/articles/poulin-wonderland-soa-governance and http://www.ebizq.net/blogs/service_oriented/2009/02/togaf_90_is_short_on_soa.php - Michael
________________________________ From: Ashraf Galal <[email protected]> To: [email protected] Sent: Mon, June 14, 2010 7:53:15 PM Subject: Re: [service-orientated-architecture] Anne on SOA Governance Thank you Gervas for publishing such a great article. *Governance is more of a political problem than a technological or business one*. (IBM) Technology focuses on matching interfaces and invocation protocols. Business focuses on functionality for serving customers. Technology and business are focused on requirements. While governance gets involved in those aspects, *it focuses more on ensuring that everyone is working together and that separate efforts are not contradicting each other*. Governance does not determine what the results of decisions are, *but what decisions must be made and who will make them.* For example, the two parties, the consumers and the providers, have to agree on how they're going to work together. Much of this understanding can be captured in a *_service-level agreement (SLA),_* measurable goals that a service provider agrees to meet and that a service consumer agrees to live with. *This agreement is like a contract between the parties, and can, in fact, be a legal contract.* At the very least, the SLA articulates what the provider must do and what the consumer can expect. SOA governance is enacted by a *center of excellence (COE),* a board of knowledgeable SOA practitioners who establish and supervise policies to help ensure an enterprise's success with SOA. The *COE establishes policies for identification and development of services*, *establishment of SLAs*, *management of registries*, and other efforts that provide effective governance. COE members then put those policies into practice, mentoring and assisting teams with developing services and composite applications. This is a very important aspect that I noticed it is missing in practice. Once the governance COE works out the policies, technology can be used to manage those policies. Technology doesn't define an SLA, but it can be used to enforce and measure compliance. For example, technology can limit which consumers can invoke a service and when they can do so. It can warn a consumer that the service has been deprecated. It can measure the service's availability and response time. *_A good place for the technology to enforce governance policies_* is *through a combination of an enterprise service bus (ESB) and a service registry*. A service can be exposed so that only certain ESBs can invoke it. Then the ESB/registry combination can control the consumers' access, monitor and meter usage, measure SLA compliance, and so on. This way, the services focus on providing the business functionality, and the ESB/registry focuses on aspects of governance. In addition to achieve the separation of concern principle of SOA and practically have a SOA governance in place. All the best Ashraf Galal Gervas Douglas wrote: > > <<Introduction > > Effective governance is a critical element in fostering a successful > SOA initiative. SOA promises to deliver a number of important business > benefits, including faster time-to-market, lower costs, better > consistency, and increased agility. But with great benefits come high > risks. SOA requires fundamental changes to the planning, development, > and operation of application systems, and it requires new levels of > collaboration among project teams within the IT department and across > lines of business. In fact, current IT practices, which typically > focus on individual projects, time-to-market, and cost containment, > frequently discourage SOA adoption. > > SOA governance helps the organization succeed with SOA by mitigating > these risks through established rules, processes, and decision-making > authority. A SOA governance program helps people do things according > to the organization's goals and best practices. An effective > governance program empowers people to handle ambiguity, balance short- > and long-range goals, and reduce conflict within the organization. > > This following article (an excerpt from the upcoming book "SOA > Governance" [REF-1] as part of the Prentice Hall Service-Oriented > Computing Series from Thomas Erl) provides an introduction to > governance, explains how it works, and differentiates it from > management. You will find this content useful if you have not been > involved in establishing a governance program before or if you would > like to gain another perspective on the mechanics of governance. >> > * > You can read the article in full at: http://www.soamag.com/I40/0610-2.php > > Gervas > * > > ------------------------------------ Yahoo! Groups Links
