• slider2

    Generalized Enterprise Function Framework  (GEFF)

  • slider3

    A3 KAM - Triple A(Architectural, Actionable and  Augmented) Knowledge Assets Management

  • slide1

    Enterprise Architecture 3.0 (EA3.0) - the third wave in Enterprise Architecture approaches

  • slider4

    ABODE™ business transformation methodology  founded on EA3.0

Business RuleSet Management

Business RuleSet Management concerns management, development, and maintenance of the internal business logic of actionable Knowledge Functions that become App(lication)s when they have been enriched with Business RuleSets, Services and internal logic based on a (micro)flow conditioning these components.


Problems and Solutions


The contemporary approach seldom uses Business RuleSets and hardly any services or APIs. This results in much work when the app(lication) is developed and maintained in source code and the result is always legacy: in a few years hardware suppliers do not support product lines, software suppliers of the operating system and programming language implementations stop support, etc. Examples are Intel that stopped the Itanium chip product, forcing Hewlett-Packard to stop with their product-line of hardware and software for their OpenVMS lines to which the DEC platform was migrated.


With the use of hardware and OS independent business rulesets the majority of these problems. Business Rules are written in “structured natural language” so business people can understand the business rules and some are capable to write and test them. However, maintaining Business Rules is not easy and often very tiring. The Enterprise Architects solution provides the possibility to use native natural language as a BRL (Business Rule Language) and the possibility to directly test (DME or Direct Model Execution) complex business logic after defining it in Business RuleSets. Business Rules are often related to formal rules and regulations. It is therefore mandatory to refer to these sources of business rules (when available) on one side and where they are used on the other side.


Tools to support Business RuleSet Management


The following tools and solutions support Business RuleSet Management:

  •  ARM/RuleSet Management 
Defining the Business RuleSets including sources of rules and regulations (Source, Law, Capability, etc.)
  •  ARM/Rule Translation 
Semi-automatically translating legal texts into Business Rules, including the definition of Facts
  •  ARM/Rule Execution
Simulation of the Business RuleSet execution in a test environment
  •  ARM/RuleSet Management 
Maintaining and managing different Business RuleSets

Advantages of the Enterprise Architects approach


  1. Defining the Business RuleSet in native natural language
  2. Defining sources and maintaining them
  3. Use the sources in the ICA (Impact of Change Analysis)
  4. Support the translation of legal texts into Business RuleSets, including Facts, etc.
  5. Maintaining and optimizing Business RuleSets based on Source, Knwledge Function, Facts and Object Attributes
  6. The SAFe™ Core Values are safeguarded and improved as follows
    • Alignment
    • Built-in Quality
    • Transparency
    • Program Execution