Business Objects and Business Rules
Business object facilities should be designed to enable businesses to implement distributed, object-oriented business applications that reflect the natural structure of the business. They should also provide structures that allow different views on the system to be faithfully captured in its design. For example, information technology experts and business experts have different but equally valid ways of looking at a business application system; both must be captured faithfully if the system is to be useful, flexible, and durable.
Among the many areas of design an application development team must deal with is business rules. This paper focuses on that area. It outlines a patterned extension to a commercially available component architecture that enables enterprise applications to systematically externalize business rules. The architecture, though still in the proof of concept phase, has been sufficiently implemented in several IBM engagements with business customers to demonstrate the feasibility of the approach.
Unable to display preview. Download preview PDF.
- [CB97]Component Broker homepage “http://www.sofiware.ibm.com/ad/cb/”Google Scholar
- [GHJV95]“Design Patterns” by E.Gamma, R. Helm, R. Johnson, and J. Vlissides. Addison Wesley.Google Scholar
- [KS97]“Business Rules: from business specification to design” by Haim Kilov and Ian Simmonds, Proceeding of the ECOOP’97 workshop on Precise Semantics of Object Oriented Modeling Techniques, May 1997.Google Scholar
- [RW94]“Constraint-based knowledge representation for configuration systems” by Rainer Weigel. Technical Report No. TR-94/59.Département d’Informatique. Laboratoire d’Intelligence Artificielle. Ecole Polytechnique Fédérale de Lausanne. IN-Ecublens, CH-1015 Lausanne (Switzerland) http://liawww.epfl.chl-weigellPapers/tr/trhtml.htmlGoogle Scholar
- [S94]“Business Objects” by Oliver Sims. McGraw-Hills.Google Scholar