SOA Audit Services and Assessment Overview
SOA Governance can be described as the policies and procedures that need to be in place for successful SOA implementation and ongoing maintenance. Governance acts as a bridge between the strategic and tactical layers to ensure proper alignment between SOA goals, their envisaged manner of implementation and the actual implementation.
Governance is implemented using a variety of mechanisms including Registries, Repositories, Enterprise Service Bus (ESB), Business Activity Monitoring (BAM), and BPEL Process Manager tools. Jaggy's SOA methodology incorporates Governance from the beginning phase of the project as well as part of an ongoing evaluation process to ensure SOA success for long term.
Jaggy's SOA Governance methodology incorporates both Design Time and Run Time Governance and Security Policies. Design Time Governance involves managing and coordinating your various SOA artifacts using a single repository. This repository should act as a central source of truth for your SOA implementation. Run Time Governance incorporates monitoring and ensures that the actual performance of the services and processes continue to meet all outlined SLAs.
To meet business, Enterprise Architecture and SOA goals, policies must be enacted across the different business areas: architecture, technology infrastructure, information, finance, portfolios, people, projects, and operations. This is the role of governance: policies, which need to be designed and enacted to ensure this alignment. The format and medium for policies may be different - some policies can be captured and enforced in technology, for example, a registry/ repository aids in enforcing service lifecycle governance, and a Web services management solution realizes the application of operational policies to services at runtime. Other policies, such as architectural policies, or funding policies need to be captured through policy documents that are distributed through the organization.
