Structure Rule Language

To aid in the ease of rule authoring, Blaze Software, now Fair Isaac, created the proprietary Structure Rule Language (SRL), an object-oriented programming language designed to enable those with little or no background in software development to pen rules. Although the capabilities of this language are far too extensive to detail in this article, we can examine the basic rule syntax.

Teaching You Tools to Become Empowered

To build a successful business and career, you must always keep up with changes in the IT Marketplace. AWS, Office 365, LinkedIn, Sales Force, SEO, Social Media are just a few examples of where knowledge is a huge factor for success.

Training with HSG addresses your knowledge gaps and provides you with the requisite tools to outpace the competition.

Rules in the SRL take the following form:

rule RuleName [at | priority M] is

                                                   if conditions [and/or]

                                                   then actions

                                                   else actions

whereby

                                                  else conditions are optional, time of invocation refers to a period of time this rule is available or will be run i.e. January 1^st thru March 2^nd every year and priority refers to rule precedence where the rule engine will favor or handle that rule having a higher priority number

Rules may be written in any one of three styles:  English-like, possessive or programmer-dot notation syntax.   Here is an example of each:

English-like Syntax:

                                   The property of the subobject of object.

 the cost of the house of Sandy

Apostrophe or possessive syntax:

                                 Object's subobject's property

Sandy's house's cost

Programmer dot-notation Syntax:

                                 object.subobject.property

Sandy.house.cost

Additional features of this language include the invocation of a number of entities such as Rule Sets, Rule Flows, Decision Tables, Decision Trees and Score Cards.  Loops, conditional statements, functions, class and object creation, integration with Java, database access, primitive type declaration that address business practices such as money, and more offered.  All this is provided to enable the rule developer, business analyst and software engineer alike to quickly and effectively develop a rule base as part of an application.