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