New visual rule builder (Michael Neale) I have been beaving away on a new UI/rule modeller specifically for the web (well, at least the web initially, hopefully we will also do it stand alone in the plug in soon).
The famous golfer riddle - first published (as far as I know) by rule-celebrity Dr. Ernest Friedmann-Hill (creator of the JESS rule engine) in this online-article.
Having just wrapped up the European Business Rules Conference (see my previous posts), I noticed that some misinformation was provided at EBRC around sequential and inferencing execution of business rules. Sadly the misinformation was provided by a vendor
Rules in (and for) the Web have become a mainstream topic since inference rules were marked up for E-Commerce and were identified as a Design Issue of the Semantic Web, and since transformation rules were put to practice for document generation from a cen
Drools is an enhanced Rules Engine implementation based on the ReteOO algorithm, an algorithm adapted from the one originally devised by Charles Forgy. Drools has become quite popular due to performance characteristics and it’s natural language semantic
One consistent question we get from outside the CEP market is: what is the difference between a “standard” Business Rules Engine (or BRE) and a (rule-driven) Complex Event Processing engine? This is particularly interesting because a rule-based CEP en
Using a rule engine provides a framework that allows a way to externalize business logic in a common place. This will in turn empower business users and subject matter experts of the business to easily change and manage the rules. Coding such rules directly into the application makes application maintenance difficult and expensive because the rules change so often. This article goes into detail on how to architect and build a service that uses Drools to provide business decisions. This service can be part of the overall enterprise SOA infrastructure. As such, it can either be a standalone service that is consumed in a one-to-many model by all contracted consumers, or part of a composite service that provides a complex business functionality. To illustrate this point, the article shows how a service using the Drools rule engine can hide the complexity of automating mortgage underwriting decisions that a mortgage company needs to make on a daily basis.
Business Process Management (BPM) und Business Rules Management (BRM) zusammen in einer service-orientierten Architektur (SOA) sind die methodischen und technischen Voraussetzungen, um Geschäftsprozesse zu industrialisieren und agil zu sein. BPM schafft die Automatisierung und Standardisierung von Geschäftsprozessen, BRM die Standardisierung und Transparenz von Management-Politiken und -Prinzipien. Und eine SOA bringt die Service-Orientierung, die uns erlaubt zwischen spezifischen Logiken einzelner Prozesse und prozessübergreifenden Logiken gebündelter Kompetenzen und Dienstleistungen sauber zu trennen. Das schafft Agilität zusammen mit Industrialisierung.