Definition

business rules engine (BRE)

A business rules engine (BRE) is a software component that allows non-programmers to add or change business logic in a business process management (BPM) system. A business rule is a statement that describes a business policy or procedure. Business logic describes the sequence of operations that is associated with data in a database to carry out the rule.

A business rules engine works by separating execution code for business rules from the rest of the business process management system. This allows the end user to change business rules without having to ask a programmer for help. When a change is made, the engine will evaluate the change's effect on other rules in the system and flag the user if there is a conflict.

According to authors Alex Berson and Larry Dubov, a complete business rules engine will include the following:

  • Business Rule Repository - A database for storing the business rules as defined by the business users.
  • Business Rule Editor - An intuitive user interface that allows business users to define, design, document and edit business rules.
  • Reporting Component - An intuitive user interface that allows business users to query and report existing rules.
  • Rules Engine Execution Core - The actual programming code that enforces the rules.

Learn more:

"Master Data Management and Customer Data Integration for a Global Enterprise," by Alex Berson and Larry Dubov, has a chapter called Overview of Business Rules Engines.

This was last updated in March 2010
Posted by: Margaret Rouse

Email Alerts

Register now to receive SearchSOA.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

More News and Tutorials

  • SOA, semantics and services combine in DoD intelligence sharing effort

    Using textual analytics and natural language processing, Modus Operandi developed a service that analyzes and parses unstructured data and pulls out events or information. Article includes tips on SOA and semantics, SOA and data models, and an SOA recipe for stone soup.Among highlights: Recognize that not everything can be or should be shared.

  • Q&A: Messaging middleware with Apache projects

    In this Q&A, Rob Davies discusses messaging middleware and the hurdles that many developers face as they first approach the subject. Davis is CTO of FuseSource and coauthor of the book "ActiveMQ in Action."

  • An SOA practices checklist for implementation roadmaps

    This article provides a master list of common practices, field proven by a number of SOA projects. Also supplied is a template that can be used as a checklist for developing SOA implementation roadmaps specific to an organization's transition project requirements.

Do you have something to add to this definition? Let us know.

Send your comments to techterms@whatis.com

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: