TADESSE TAREKE.pdf - Addis Ababa University

Development of BROOM Business Rules Object-Oriented Method
Traditionally, we can model Terms as Entities and Attributes [22, 49].
Consequently, object-oriented modeling of Terms is equivalent to building Entity
Classes for the Terms of the business rules (it follows from assumption 1 above).
This can be done by extending a class diagram to indicate the dynamicity of
business rules as shown in Figure 4 below.
Figure 4: Modeling a Term at First Glance
In the above figure, «Term» and «Persistence Operations» are Stereotypes.
Unfortunately, the above proposed model cannot serve for our purpose since it
violates the assumptions set forth in the beginning of this section (especially,
assumption 2 and 3).
Attributes
«Term»
Class Name
«Persistence Operations»
Operations ()
Note that the standard UML class diagram depicts the static structures and
behaviors of a system [8, 41, 47, 50]. Thus, they are not suitable for modeling the
dynamic structures and behaviors of the business rules – in our case, terms as they
stand. In other words, since terms are supposed to be managed by all users,
including the businesspeople of the system, the above model is incapable of
addressing the changes encountered in the terms of a business rule system.
27