The ultimate objective of Business Decision Modeling:
A business analyst (subject matter expert) defines a business problem, and a smart decision engine solves the problem by finding the best possible decision.
Declarative decision modeling assumes that a business user specifies WHAT TO DO and a decision engine figures out HOW TO DO it. This is quite opposite to the Procedural approach frequently used in traditional programming.
Continue readingThe recent LinkedIn discussion “What rules representation to choose for which audience?” came to the question about business analysts handing their business rules written in plain English over to IT for an implementation. Continue reading
DMN defines “aggregation” in the following way:
“Multiple hits must be aggregated into a single result. DMN 1.0 specifies six aggregation indicators, namely: collect, sum, min, max, average. Optionally, the aggregation indicator may be included in the table. The default is collect.”
Below is a list of my issues with this DMN 1.0 approach. Continue reading
This question was asked by Antonio Plais – see the LinkedIn discussion. Several practical variations of this question were mentioned: 1) Define if the same product appears more than once in the same sales order; 2) determine the uniqueness of records in a file to be loaded into a Data Warehouse. Obviously, the question deals with business rules defined on collections of objects – not the most popular topic among decision modelers. Continue reading
LinkedIn today is probably the most popular social network for professionals. Looking for one of my old posts, I noticed that it is not so simple to find it and many people have troubles to do it. However, when you click on your name inside any discussion you will receive links to everything you posted but only within one discussion group. Here are LinkedIn discussions that I’ve started in several groups: Continue reading
OpenRules - Decision Intelligence Software 