Business rules systems are automated systems in which the business rules are separatedrnfrom the procedural codes and database constructs. In addition, these business rules arernshared across data stores, user interfaces and applications. The formal way of developingrnsuch systems is known as Business Rules Approach (BRA). Any approach has its ownrntradeoffs. To that end, BRA and other approaches such as Object-Oriented Approachrn(OOA) have their own strengths and weaknesses in developing business rules systems.rnThis research is targeted to bring about a new, lightweight, and viable method known asrnBusiness Rules Object-Oriented Method (BROOM, for short) by taking the strengths ofrnboth approaches.rnPersistency of business rules is a prerequisite for separating business rules from thernprocedural codes and database constructs. This is, however, a less addressed issue byrnOOA although the concept of objects has been spread since 1967. Furthermore, thisrnseparation of business rules is a basic principle of BRA in which its proponents considerrnthat OOA and the Unified Modeling Languageï›› (UMLï›š) are incapable of addressing therndevelopment problem of a business rules system.rnIn this research, to alleviate the problems stated above, UML was extended withrnstereotype extension mechanism to model the business rules flavors (i.e., term, fact andrnrule). The support tools for the method were also prototyped. These support tools includernMetamodel Management Tool (MMT), Rules Management Tool (RMT), and DatarnManagement Tool (DMT). Moreover, a general architectural framework for the methodrnwas provided from which an extended version of the framework was drawn. This extendedrnframework utilized Java, eXtensible Markup Language (XML), and eXtensible StylesheetrnLanguage (XSL) in order to realize a design pattern for a lightweight Rule Engine.rnLast but not least, BROOM was demonstrated with a system and the extended frameworkrnas a case study. The system rigorously used the prototype tools after it was modeled withrnthe UML extensions made earlier. Finally, the results of the case study were analyzed.rnKeywords: Method, Business Rules, Business Rules System, Rule Engine, Support Tools