Abstract
The declarative approach specifies what is to be done rather than how to do it. When adopted in information systems development, this implies that the system should be seen as a collection of business rules that can be enacted using a business rules engine. Business rules should be expressed in a form that is as close to the one in which business people perceive the rules. A business rules management system is needed to acquire, store, and allow modification of a business rules database. The rules are then handed over to a rules engine for enactment. The BRMS considered in this chapter uses an antecedent-consequent form for representing rules. These are based in a first order logic. Rules are formed with courses of actions and conditions in rules antecedents and courses of actions in rule consequents. It also introduces notions of state change in the business rule and temporal relation within rule and between different rules. Business rules are structured into atomic, complex, and abstract rules. The business rules are translated into enactment rules and converted to Java.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
