• slider3

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

  • slider4

    ABODE™ business transformation methodology  founded on EA3.0

  • slider2

    Generalized Enterprise Function Framework  (GEFF)

  • slide1

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

Testing Business Rules

Problems and Solutions

Nowadays most of the Information Systems and App(lication)s are designed and developed in a conventional way. This results in a tiresome design and development process with support of the expertise of many different specialists, amongst others the use of Source Code to define the What and How of the solutions. The Enterprise Architects approach only uses the How for the Business Logic through the use of business rules as translation of rules and regulations of law text, business conventions and agreements, etc. This results in a quick understanding of How the App(lication)s work for both specialists as well as business people, enabling change in a very fast way.

 

Tools to support Business RuleSet Testing

To test these Business Rules Enterprise Architects delivers the following tools:

  • ARM/RuleSet Management for                                         
    • Testing Business RuleSets interactively
    • Check the correct execution of the Business Rule Syntax and Semantics
    • Monitor the progress of the execution of Business RuleSets

The Rule Analyst can interactively define the contents of the different components like:

  • Input and Output Parameter attributes
 
  • Facts, or
 
  • Use the developed and tested
Services to automatically access the databases/data stores and use the contents for testing
  • ARM/RuleSet Source Management
Managing the content of the sources which the Business RuleSets are referring to
  • ARM/Technical execution 
Testing the Technical Services through protocols, etc.

Advantages of the Enterprise Architects approach

  1. Possibility to no only test the Business Rules themselves but also the relations with their sources
  2. Possibility to test the execution of the interaction with technical services
  3. The SAFe™ Core Values are safeguarded and improved as follows
    • Alignment
    • Built-in Quality
    • Transparency
    • Program Execution