Book Image

Drools JBoss Rules 5.X Developer's Guide

By : Michal Bali
Book Image

Drools JBoss Rules 5.X Developer's Guide

By: Michal Bali

Overview of this book

<p>Writing business rules has always been a challenging task. Business rules tend to change often leading to a maintenance nightmare. This book shows you various ways to code your business rules using Drools, the open source Business Rules Management System.<br /><br />Drools JBoss Rules 5.X Developer's Guide shows various features of the Drools platform by walking the reader through several real-world examples. Each chapter elaborates on different aspects of the Drools platform. The reader will also learn about the inner workings of Drools and its implementation of the Rete algorithm.<br /><br />The book starts with explaining rule basics, then builds on this information by going through various areas like human readable rules, rules for validation, and stateful rules, using examples from the banking domain. A loan approval process example shows the use of the jBPM module. Parts of a banking fraud detection system are implemented with the Drools Fusion module which is the complex event processing part of Drools. Finally, more technical details are shown detailing the inner workings of Drools, the implementation of the ReteOO algorithm, indexing, node sharing, and partitioning.</p>
Table of Contents (22 chapters)
Drools JBoss Rules 5.X Developer's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Setting Up the Development Environment
Creating Custom Operators
Dependencies of Sample Application
Index

Banking domain model


The UML diagram of this model is shown in the next screenshot. It defines four entities: Customer, Address, Account, and Transaction.

Figure 1: UML diagram of a simple banking system

Customers are pivotal for every bank. The customer information that is stored are name, date of birth, and address. For every address the model stores two address lines, postal code, city, and a country. The customer can have zero or many accounts. Each account has a number, name, actual balance, and currency. An account can be of a specific type; the following types are considered:

  • Transactional: This is used for day-to-day banking and usually with very little interest rate.

  • Savings: This is used as an account for saving money. Start date represents the date when the money was lodged into this account and end date represents the date when they were taken out.

  • Student: This is designed specifically for younger customers who are price sensitive; however, they don't need more advanced services...