Design principal for BRFplus application

[Former Member]

Hello BRFexperts,

I have designed a custom BRFplus application.It has more than 50 formulae , 5-6 decision tables , 7-8 decision trees etc.

I have created 1 function, 1 ruleset and multiple rules. Since the number of variables in the ruleset look a bit too many ( 45 - 50 ) now, I believe it is time to split.

Since I am new to BRFplus, what is the best design approach ?

Also, I need to be able to use trace( both techinal and lean ), & versioning so please suggest if I need to consider something.

Your response will be highly appreciated.

Regards,

Sonika

[carsten_ziegler]

You may combine elementary data objects that are related into structures (e.g. Customer ID, name, Age could be moved into a structure Customer).

[Jocelyn_Dart]

Hi Sonika,

Ok I have some that are easily double that size on all fronts, so you don't really need to split it up yet.  However if you do want to split, as a first step you might consider starting by using the expression type that lets you call another BRF+ function. That would let you start to split your main function into sub functions if you wish. You might also want to consider using Catalogs to help focus business experts and others on the most important decision tables and functions, if you aren't already using catalogs.

Regards,

Jocelyn