Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Transcript of SOA Governance
* tre Identified Candidate Defined Fading Retired The Service Lifecycle Dispensation Compliance Information SOA Governance The disensation process starts when a service does not conform to a checkpoint's policies, but the development must still continue.
The policy itself may in fact be incorrect, meaning that the policy must be changed. This invokes the Vitality method, which keeps the governance model relevant to the service development.
But most likely the service must be changed. This means that the service owner needs to plan for having the service conform to the policy at a later date. If the service conforms to a checkpoint's all policies,
the service is approved. At some checkpoints this means
that the service reaches a new state in its lifecycle. Governance is all about establishing and enforcing how people and solutions work together to achieve organisational objectives
SOA Governance is an extension of both IT Governance and Enterprise Architecture Governance. As such it cannot be understood and executed separately, but must be integrated with both. For the service to reach the Identified state it must conform to following policies (examples):
* it has an owner
* the scope is derived from multiple business processes (reuse)
* it is unique
* there is sufficient financing for the entire lifecycle
* it is documented according to the specified standard The policies describe good and bad behavior.
Exercising governance always requires balancing between them; what is good in short term usually means bad in the long term. Policies are derived from the basic principles of SOA governance. If we believe that a specific quality is good,
then we need to strive to achieve this. To reach a new state in a service's
lifecycle, it must pass a checkpoint in the compliance process. As an example, if we believe that pointy window arches are good, and round ones bad, we would approve the blueprint to one of these buildings, but not the other. The Nôtre Dame in Paris St Peter's cathedral in Rome Defined Candidate One of the most difficult questions to answer is:
* How big should a service be? Good size Too
specific This includes (among other things):
* having people understand the value of SOA and
* keeping a repository to discover and reuse services
* offer training of governance processes
* clear and easily understood policies Compliance is the first of three SOA governance processes. It ensures that all work and results conform to the policies, guidelines and standards that we have found useful and beneficial. Dispensation is the second SOA governance process. It allows a project or application team to appeal non-compliance to established processes, standards, policies, and guidelines. Communication is the third SOA governance process. It ensures that the governance is understood. It should also ensure access to and use of governance information. Can you see which one would be approved in a checkpoint? Business Governance SOA Governance IT Governance EA Governance Supports Supports Aligns Extends Extends Here is one basic princple:
* SOA Governance must promote the alignment
of business and IT.