Discipline: Rule Governance
When a BRMS approach is introduced, the business rule management moves from IT team into the business unit team. Formal process needs to be developed.
Business rules are exposed, separated, stated in formal terms and managed for change against a formal governance processes that span among business and IT.
Relationships
Main Description

Developing or customizing the governance processes is an incremental activity. As the processes are deployed across departments, there are always tension between IT and Business teams. The idea is to start simple, and involve IT and Business stakeholders in the process design. After first implementation it is possible to fine tune the processes.



The architect is one of the main roles responsible for designing the governance processes.  He or she should follow the steps below:

·         Develop the organization map for all the departments involved in the rule approach.

·         Assign rule set responsibility and access control

·         Define the rule life cycle, rule set life cycle and domain object model changes

·         Develop each major processes to support rule management on top of the BRMS

·         Document those process to communicate to all stakeholders using BPMN or UML activity diagram

·         Design and build the tools to support those processes:

  • Implement the rule extensions model to support those processes by adding meta data on top of the rule artifacts.  
  • customize the behavior of the BRMS by implementing the controller interface, to trigger event on specific action like the changes on the rule life cycle.

For the business rule development and maintenance these processes are:

  • Rule change management process
  • Rule execution monitoring process
  • Rule authoring process
  • Rule execution process
  • Rule deployment process
  • Rule testing process
  • Rule retirement process
  • And the last process is about how to improve the current governance processes.


More Information