TADESSE TAREKE.pdf - Addis Ababa University

Related Work Business Rules Object-Oriented Method
As indicated in the Repository Systems Section of this review, Java, XML and XSL
are used for developing a simple and lightweight rule engine enabling us to
separate business rules from the procedural code of an application [7]. XSL is
originally created for transforming XML document into a formatted output such as
HTML document [43]. Boglaev [7] does not use XSL as it was intended to be used
by its architects. Instead, it is used as a repository system for the business rules
separated from an application code.
Another possibility for having a lightweight rule engine is to use application
programming interface (API) specification for a Java based rule engine, which is
sometimes referred to as JSR-94 [6]. It is to be used for developers developing
their rule engines enabling them interoperate one another.
3.6.3 INTEGRATED SUPPORT TOOLS
The idea of integrating the support tools for our proposed method was borrowed
from work of Paige et al. [42]. Yet, BROOM differs for the following facts:
1. It focuses on business rules systems development by separating business rules
from the procedural codes and database constructs.
2. The integrated support tools that can be used for developing business rules
systems consist of the following:
a. Business Rules Management Tool
i. Metamodel Management Tool
ii. Data Management Tool
iii. Rule Management Tool
iv. Report Generation Tool
b. Reverse Engineering Tool. (For example, a tool that enables us to model the class
diagrams using the extended UML class diagrams based on the Metamodel
information stored in repository systems).
c. etc.
19