TADESSE TAREKE.pdf - Addis Ababa University

2.1 BUSINESS RULES APPROACH
CHAPTER 2
BACKGROUND
Business Rules Approach is a formal way of managing and automating the
business rules of a business rules system so that the business behaves and
evolves as its leaders intend [22, 49].
According to [22, 31, 49, 58], business rules approach proponents such as Ross
[49] and Halle [22] propose the basic steps towards developing a maintainable and
understandable business rules systems. These steps focus on separating the
business rules from any code of an application or active database management
system (DBMS) constructs such as triggers, which are standardized in Structured
Query Language-3 (SQL-3) [27]. In other words, the business rules are treated like
data of a system in a DBMS. Besides, these proponents comment that the current
object-oriented methods do not support this separation of business rules [22].
2.2 OBJECT-ORIENTED APPROACH
The main goal of object-oriented approach is reusability and flexibility for
developing object-oriented software systems [10, 47]. However, reusability and
flexibility issues directly focus on the programmers’ productivity. Moreover, the
arguments for object-oriented approach and separation of business rules from the
procedural codes can be twofold: First, the current modeling tools such as the
Unified Modeling Language (UML) do not support modeling of a class containing a
set of business rules that are separated from the procedural codes and stored in a
repository system like a DBMS. Second, object-oriented programming languages
do not adequately address separation of rules from the procedural codes [22].
7