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.
4.1 INTRODUCTION<br />
CHAPTER 4<br />
DEVELOPMENT OF BROOM<br />
BROOM attempts to combine the strengths of the two approaches: Business Rules<br />
and Object-Oriented Approaches with a modeling language, an appropriate<br />
framework, and integrated support tools. It is supposed to be a lightweight<br />
software development method for building object-oriented business rules systems.<br />
Simply put, a business rules system is an automated system in which the "rules"<br />
are separated (logically, perhaps physically) and shared across data stores, user<br />
interfaces and applications [4, 22, 49].<br />
The next sections are devoted to the development of the different components of<br />
the proposed method – an extension of the UML, framework, and support tools &<br />
techniques.<br />
4.2 EXTENDING UML FOR BROOM<br />
To extend UML, data modeling techniques are used for the fact that persistency of<br />
the business rules is the main concern of the method under development. That is,<br />
our strategy in modeling business rules for the proposed method is first to look at<br />
the business rules repository system level so as to come up with an extended UML<br />
class diagrams that helps us model the artifacts of a business rules software<br />
system.<br />
4.2.1 EXTENDING UML<br />
This process of extending UML is done after proper analysis of UML class diagram<br />
for its necessity, sufficiency, and consistency is carried out. The technique uses<br />
stereotyping extensively for modeling business rule via its flavors: Terms, Facts<br />
21