From the developerWorks archives
Date archived: January 5, 2017 | First published: August 09, 2012
Organizations use policy to guide decisions that are important to both the business and IT. Many times, policy is reactive, and created as a result of something negative happening. The SOA Policy Reference Architecture shows how the practitioner can be proactive with policy creation and maintenance, including the ability to manage and automate that policy. This article and its more detailed attachment provides a framework for defining policy starting with business goals and objectives and then decomposing those into the business, architectural, and operational policies necessary to properly control the organization. An example of using the SOA Policy Reference Architecture to create the policy decomposition will be given to aid the reader in understanding the details.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.