| Type | Score | Description | |
|---|---|---|---|
| Knowledge characteristics | User set or System set | System | An external rule is part of the truth maintenance mechanism and any result is system-set. |
| Parameters or complex model | Complex Model | On the external rule parameters can be defined which trigger the truth maintenance. In code you however access to the complete profile, and can use any attribute during the calculation. Although it is best practice only to use the truth maintenance parameters, we classify this as complex model. | |
| Enhanced by Blueriq Functionality |  | There are dependencies for the truth maintenance parameters, but there is no way of knowing what happens in the external rule or what attributes are actually needed. | |
Maintainability characteristics It should be possible to quickly make changes to business rules independent of other functionality. | Focus on Internal or External Use | Internal | External rules are only used by Blueriq. |
| Low Implementation complexity |  | There is a simple hook, and the code that needs to be written is simple. | |
| Internals invisible (encapsulation) | | The internal code is not visible | |
| Autonomous | | As the complete profile can be input to the external rule, changes in it may lead to side effects during the execution of the external rule. | |
| Highly Testable | | Unit tests can be written in code. | |
| Highly Reusable | | Once you have the external rule defined, then you can distribute the definition in a library and use it simply on any desired attribute. | |
| Out of the Box | | An external rule requires writing of code. | |
Deployment characteristics | Part of Application or Separate Deployment (=deployment) | Separate Deployment | The code has its own life-cycle and is deployed separately. |
Overview
Content Tools