Business Rules Engine overview-Business Rule Engine overview write by Mark kamoski

This is what Mark kamoski wrote about business rules. Article , Introduces business rules at a high-level level,

Purpose of this Article:
1. Make a statement on some technical analysis including business rules at a high-level level
2. Introduce a simple design method that can solve some problems
3. demonstrate a solution for Business Rules

You can download all the content of an article at the following address:
/Files/carlwave/businessrulesengineoverview.rar

Document directory
Business Rules Engine Overview
Top
1 Table of Contents
1 Table of Contents .................................... ........................................ ........................................ ............................ 1
2 purpose ...................................... ........................................ ........................................ ........................................ .......... 2
3 audience ...................................... ........................................ ........................................ ........................................ ....... 2
4 update ...................................... ........................................ ........................................ ........................................ ............ 2
5 problem ...................................... ........................................ ........................................ ........................................ ......... 2
5.1 background ...................................... ........................................ ........................................ .................................... 2
5.2 Business Rules into action .................................... ........................................ ........................................ ........... 3
5.3 business rules management .................................... ........................................ ........................................ .......... 4
5.4 static logic. dynamic logic ...................................... ........................................ ........................................ .... 5
6 design ...................................... ........................................ ........................................ ........................................ ............. 6
6.1 Overview ...................................... ........................................ ........................................ ........................................ .. 6
6.2 design goals ..................................... ........................................ ........................................ .................................... 7
6.3 object uniformity ..................................... ........................................ ........................................ ........................... 7
6.4 schema knowledge ..................................... ........................................ ........................................ ......................... 8
6.5 call site simplicity .................................... ........................................ ........................................ ......................... 9
6.6 logic wait action ..................................... ........................................ ........................................ .......................... 9
7 solution ...................................... ........................................ ........................................ ........................................ ........ 9
7.1 overview ...................................... ........................................ ........................................ ........................................ .. 9
7.2 or mapping ..................................... ........................................ ........................................ ....................................... 9
7.3 XML mapping file .................................... ........................................ ........................................ ........................... 10
7.4 Rules Engine administration console ................................... ........................................ ................................. 10
7.5 context specification ..................................... ........................................ ........................................ .................. 11
7.6 centralized rules engine .................................... ........................................ ........................................ ............ 11
8 Summary ...................................... ........................................ ........................................ ........................................ ..... 12
9 appendix ...................................... ........................................ ........................................ ........................................ ...... 12
9.1 Design Model ..................................... ........................................ ........................................ ................................. 13
9.2 Mapping File sample .................................... ........................................ ........................................ ...................... 14
9.3 abbreviations ...................................... ........................................ ........................................ ............................... 14
9.4 links and references .................................... ........................................ ........................................ .................... 14

Purpose
· The purpose of this document is as follows:
O to present a high-level technical analysis of some of the problems
Involved in business rules management;
O to describe a simple design that will solve some of these problems; and,
O to show one solution on how to implement a simple business rules engine
Via Microsoft visualstudio. net, wilsonormapper, and related
Technologies.

Audience
· The intended audience for this document contains des the following:
O business analysts
O Software Project Managers
O software system analysts
O software system release TS
O software system developers
· The intended audience will have a working knowledge of the basic concepts in
The field of software development.
· The intended audience will have a working knowledge of the basic concepts in
The field of business rules theory.