July 31, 2010

SOA Governance Policies & Policy Management

Learn how SOA Policy Management and SOA Governance relate and the important role playd by policies in SOA Governance success.


SOA Governance: An Enterprise View
As part of a deeply-technical and standards-focused look at the definition, role and need for SOA Governance, the author shares valuable information on the role of Policies in SOA Governance. Included are exceptional examples of SOA Governance policies, grouped by areas of applicability (Governance, Development and Production). Highly Recommended.
Michael Poulin, InfoQ

SOA Governance for the Organization: Best Practices for Getting Started
A helpful look at the definition and role of policies in SOA Governance. From the Resource: "SOA governance activities may differ from organization to organization, but SOA governance is always a process (and typically an iterative process), operating over the service lifecycle - from the cradle to the grave of all services. Policies defined in SOA governance typically drive the service lifecycle in the following phases: 1) Design-time activities, where SOA governance policies govern service identification, design and specification. 2) Deployment activities, where SOA governance policies govern checkpoint compliance testing and dictating run-time access policy standards. 3) Run-time activities, where run-time service policies developed by your governance team dictate service utilization, availability, service level agreements, and access policies. This also includes service retirement, where services are deprecated and removed. 4) Change-time activities, where SOA governance policies dictate the process for modifying, registering, and deploying new functionality. This is inherent in all phases of the SOA governance lifecycle."
Kevin T. Smith, ManTech International

The Value of SOA Policy
A clear and interesting look at the definition, value and examples of SOA Policies. From the Resource, "A SOA policy is a declarative electronic rule that defines correct behavior. Today these policies typically exist as paper-based rules that are buried in specifications authored by Architects, IT Administrators, and Business Analysts. Policies come in two flavors. Design Time policy and Run Time policy."
Keith Pijanowski, Microsoft

« 1 | 2 | 3 | next »