TADESSE TAREKE.pdf - Addis Ababa University
TADESSE TAREKE.pdf - Addis Ababa University
TADESSE TAREKE.pdf - Addis Ababa University
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Development of BROOM Business Rules Object-Oriented Method<br />
Table 6: Description of the Extensions used for FDM<br />
No. Field Remark<br />
REMARKS<br />
1. «Dynamic Attributes»<br />
2. «Persistence Operations»<br />
These are all the fields found in the above entity<br />
data models for the list of facts (Table 5), which<br />
can be changed by the user of the system.<br />
As an entity class (i.e., business rules should<br />
persist), it requires to have the following default<br />
methods such as Save (), Delete (), and Get ()<br />
operations for managing facts data in a business<br />
rules repository system.<br />
1. The «Dynamic Attributes» can be treated as built-in structures of the class<br />
for a business rules system.<br />
2. Metamodel Management Tool (MMT) handles the relationships/facts<br />
concept of a business rules system.<br />
4.2.3.3 MODELING RULES<br />
Rules are elements or flavors of business rules that can be expressed as<br />
calculations, constraints, or conditional logic. In other words, rules can:<br />
1. Produce the result of a Calculation,<br />
2. Test Conditions to produce a new fact, or<br />
3. Test a condition to initiate action.<br />
A similar but more formal classification of rules can be found in the next table<br />
(Table 7). As presented in the table, there are five types or categories of rules [22]:<br />
Constraints, Guidelines, Action Enablers, Computations and Inferences.<br />
35