SOA governance defines the set of policies, rules and enforcement mechanisms for developing, using, and evolving service oriented systems and for analyzing their business value

1. Service Oriented Architecture: 17
SOA Governance Reference
Architecture
Prof Neeraj Bhargava
Vaibhav Khanna
Department of Computer Science
School of Engineering and Systems Sciences
Maharshi Dayanand Saraswati University Ajmer

2. What is SGRM
• The SOA Governance Reference
Model (SGRM) is a generic model that is
utilized as a baseline SOA Governance Model
to expedite the process of tailoring an SOA
Governance Model for an organization.
• All aspects of the SGRM are reviewed and
considered for customization to the
organization’s environment

3. Constituent parts of SGRM
The SGRM defines a number of constituent parts,
including:
• SOA governance guiding principles
• SOA governing processes
• Governed SOA processes
• SOA governance process artifacts
• SOA governance roles and responsibilities
• SOA governance technology

4. SOA Governance Guiding Principles
• SOA Governance Guiding Principles assist in the
prioritization and decision-making for the design,
deployment, and execution of the SOA Governance. This
includes aspects of people/roles, processes, and technology.
• The organization’s SOA and governance maturity will affect
how these principles are selected and how strictly they are
applied.
• It is expected that a subset of these principles will be
selected and modified.

5. SOA Governance
“SOA governance defines the set of policies,
rules and enforcement mechanisms for
developing, using, and evolving service
oriented systems and for analyzing their
business value.”

6. SOA Governance
• Definition from IBM:
“SOA governance is an extension of IT
governance, which is an extension of corporate
governance.
SOA Governance exercises control of the lifecycle
of services and composite applications in an
organizations SOA”

7. SOA Governance: Key points
• SOA is about the sharing of services.
• Services must be created and used according to
rules that all of the stake holders can follow.
• Collections of rules are known as policies.
• SOA Governance is about the development and
management of policies.
• Collaborative processes produce and manage
policies.
• This collaborative process may be disruptive.

8. SOA Governance
• Is meant to resolve issues including:
- which services should be created?
- how should they be created?
- who should have access to these services?
- how will the services be provisioned?

10. Policies
• Classified into:
(1) Design time policies and
(2) Run time policies

11. Design Time Policies
• Rules for developers
- Interoperability framework
Require interoperable protocols be used by
services
- Provide incentives to developers
for building proper services and by actually
using existing services rather than ignoring
them.

13. Run Time Policies
• Lay out the details of service contracts:
Security
Expected Service Levels
Restrictions on service use – authorization
decisions
May be enforced by runtime components

15. Governance Software
• An SOA Registry – lists services and service
locations.
• An SOA Repository – points to the runtime and
design time policy information associate with
services.
• Oracle offers SOA Governance 11g
• Oracle Web Service Manager can be accessed via
the Enterprise Manager. These policies may be
created and deployed to the OSB.
• EM or OSB may also be used to monitor usage.

16. Ownership
• Every service has a clearly specified owner.
• Disputes will arise over what functionality the
service will provide.
• These disputes must be resolved.
• Part of SOA governance is to provide a forum
and a means for dispute resolution.

17. Assignment
• Explain the SOA Governance Reference Model
• Thank You