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 />
The question is then, how can we model facts/relationships of a business rules<br />
system in an object-oriented way using UML? Facts (Layer 2) in a business rules<br />
system (Layer 1) can be modeled by considering its component (Layer 3) - List of<br />
Facts/Relationships of a system along with the characteristics or properties of this<br />
component –Entity1, Attribute1, Entity2, and Attribute2. This handles containment<br />
of attributes by an entity as well as the relationships between two tables.<br />
FACTS DATA MODEL (FDM)<br />
Facts can be modeled as Relationships [22, 49] of the Entities and Attributes that<br />
are modeled for the terms. Thus, to model the facts of a business rule, we need to<br />
model its components shown in Figure 7 above. Table 5 below presents the data<br />
model for the collection of facts in business rules system.<br />
Table 5: List of Facts Data Model Design<br />
No. Field Remark<br />
1. FactID This is a Primary Key.<br />
2. Entity1 The first entity where a relation starts.<br />
3. Attribute1 For Related To: A key of the Entity1 by which it is related to the<br />
Entity2 with a key of Attribute2.<br />
For Containment: This may also represent that Attribute1 is<br />
contained in Entity1. In that case, both Entity2 and Attribute2 are<br />
empty string.<br />
4. Entity2 A second entity which is related to the Entity1.<br />
5. Attribute2 Similar to 3 above.<br />
6. IsUnique For containment relationship, an attribute (attribute1) of Entity1<br />
may be unique or repeating. If IsUnique is True, Attribute1 is<br />
unique in Entity1.<br />
33