This column is the next in a series that provides the reader with best practices on using or choosing a rules engine. The target audience for this series is typically the user of a rule engine, i.e., a programmer or someone with programming skills. All coding examples should be read as pseudo-code and should be easily translated to a specific target syntax for a rule engine that supports backward and forward chaining in an object-oriented environment.
Read »Different Kinds of Rules and How to Write Them Properly
http://www.brcommunity.com –
Category: Business Rules General Tags:
Search
Login
Who's new
- NorikoCapilla
- stephanie
- lolamiller
- benjaminhiatt
- hasenchat
Who's online
There are currently 0 users and 1 guest online.
Syndicate
You are logged in as
Anonymous
Categories
- All
- Business Rules in Enterprise Architecture
- Business Rules in Business Process Management
- Business Rules in Workflow Management
- Business Rules Conferences & Symposiums
- Business Process Management
- Event Driven Architecture
- Business Rules Standards
- Rule Engine
- Business Rules News
- SBVR
- Business Rules Design & Architecture
- Business Rules Design Patterns
- Business Rules General
- Business Rules Performance
- BRMS
- Business Rules Whitepapers
- Rule Markup Languages
- Model Driven Architecture & Engineering
- Business Intelligence
- Model Transformations
- Rule Based Frameworks
- Knowledge Engineering
- Semantic Web
- Business Rule Validation
- Business Rule Verification
- Business IT Gap