OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm-ra message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [soa-rm-ra] governance musings over the weekend

On the diagram:

The name Management Body could be shortened to
Management and the name Metrics Collection could be
shortened to Metrics.  The longer versions of the
names do not add additional meaning for me.

>- You cannot govern what does not 
>  agree to be governed

Ideally the participants agree to the policy of a
governance domain but in many cases they may not.  I
see the ability to govern coming from having the
resources to enforce governance rules, not because of
agreement of the participants.

In the course of doing global business in a SOA
ecosystem, a company may interact with 20 or so
governance domains in a day.  It is doubtful the
company will agree with all the policies for each
governance domain or even be aware of all the policies
in each governance domain.  Some businesses may rely
on the enforcement mechanisms within the governance
domain to let them know if a policy is being violated.


--- Ken Laskey <klaskey@mitre.org> wrote:

> Another tweak to the governance model, this time
> adding a class for  
> Metrics Collection and new relationships.
> Given a model of Governance, the next question on my
> mind is how does  
> it affect architecture.  Some thoughts along those
> lines:
> Architecture implications
> - need mechanisms to create and catalog Policies,
> Rules, and Regulation
> - need reliable access to specifics of current
> Governance Framework  
> and Governance Processes
> - need mechanisms to collect metrics
> - need mechanisms for Participants to access metrics
> - need enforcement mechanisms for Management Body
> Assumptions
> - You cannot govern what you cannot measure
> - You cannot govern what does not agree to be
> governed
> - expectations on what can and will be governed must
> match the  
> reality of what is possible and what is the
> collective will to see done
> - need to manage (including configuration management
> and CRUD  
> processes) Governance Framework and Governance
> Processes, Policies,  
> Rules, and Regulations but not Goals
> - I don't care where the Goals originated beyond
> saying they come  
> from Participants
> - I don't care if they are "good" Goals or "bad"
> Goals because it is  
> up to Governance to come up with the set that serves
> those who want  
> to remain Participants, and the SOA machinery should
> be agnostic to  
> the quality of the Goals or the make-up of the
> Participants
> - There may be many parallel or interacting
> Governance environment  
> with which a given Participant must interact.
> Ken
> ------------------
> Ken Laskey
> MITRE Corporation, M/S H305     phone:  703-983-7934
> 7515 Colshire Drive                        fax:     
>   703-983-1379
> McLean VA 22102-7508

Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]