BIZRULES | RuleMap | RedFlagRulez | Visible Knowledge | Knowledgebase | Blog | BRxG | Agility Alliance | Free Newsletter

Business Rules Knowledge Base
Trends
Strategies
Technologies
Methodologies
Frameworks
Vendors
Best Practices
Lessons Learned
Software Tools  
BRE Business Rule Engines
ESExpert Systems
Management Domains
BRM Business Rule Management
BPM Business Process Management
KM Knowledge Management
Knowledge Base > Lessons Learned Back 
Join BIZRULES Email List Email:
Rule Resources
Articles
Interviews
Social Networks & User Groups New
White Papers
Presentations
Case Studies
Reviews
Blogs
Risks and Costs of     Breaking the Rules
Examples of business mistakes caused by poor:
  Knowledge Management
  Rules Management
  Process Management
Locations of visitors to this page

 

 
 

Use Business Rule Analysts for Rule Engines; Use Business Analysts for Code

Companies learning to use the business rules approach often run into trouble when they try to use business analysts (i.e. systems analysts) instead of business rule analysts (i.e. knowledge engineers) to define their business rules.

That approach works for traditional IT-driven procedural hard-coded applications. But for leading-edge business-driven declarative rules-based applications, traditional business analysis and systems analysis techniques are probably not going to work.

Knowledge engineering techniques and business rules analysis techniques, however, will work.

NOTE: This is a summary of a blog posting. The full article is available as a blog.

For the rest of the story, see Use Business Rule Analysts for Rule Engines; Use Business Analysts for Code

Use Business Rule Analysts for rule harvesting not IT/Business Analysts or Systems Analysts

 

Home | Up | Feedback | Search | Contact Us

BIZRULES is a registered trademark of BizRules.com.  Copyright 2002-2008 BIZRULES. All rights reserved. For further information email or contact us. Revised: 1/18/2008.