TADESSE TAREKE.pdf - Addis Ababa University
TADESSE TAREKE.pdf - Addis Ababa University
TADESSE TAREKE.pdf - Addis Ababa University
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Development of BROOM Business Rules Object-Oriented Method<br />
No. Field Remark<br />
REMARKS<br />
2. «Persistence Operations» As listed above (in the extended UML Terms class<br />
diagram), this stereotype represents all the default<br />
operations (save, get, delete) that can be used for<br />
managing the terms constituents data in a repository<br />
system, as an entity class.<br />
1. The extended UML class diagram shown above is a template for the<br />
collection of terms in a business rules system.<br />
2. The extended UML class diagram for Terms (entities and attributes) and<br />
the values of the attributes are managed by two of the Business Rules<br />
Management Tools known as Metamodel Management Tool (MMT) and<br />
Data Management Tool (DMT) respectively.<br />
4.2.3.2 MODELING THE FACTS<br />
Facts are about relationships or associations among the other flavors of business<br />
rules. The relationships between the pairs (X, Y) of terms of the business rules are<br />
classified into the following categories: “X Related To Y” means two tables are<br />
Related To one another. “X Contains Y” means containment fact (i.e., an entity<br />
contains attribute(s)).<br />
Relationship/fact has been extensively addressed by the relational modeling<br />
technique with an extension (profile) of the standard UML [2] except that in the<br />
business rules approach the facts are stored in a repository system.<br />
31
Change language