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 > Best Practices Back Next 
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

 

 
 

Rulebase Repository Design

Repository design is a crucial task. Some BRE vendors recommend designing the application repositories first, then later looking at designing and building the enterprise repositories.

Repository design tasks include:

Folder and hierarchy design

Folder, ruleset, and rule naming conventions

Identifying global rules that should be shared across enterprise applications

Identifying local rules that are only used by one application

Spend time up front designing the rule repository before writing the rules

Best Practice: Spend time up front designing the rule repository before writing the rules

Application business rules are often organized in a hierarchy:

Global rules that apply to all applications and processes would be at the top level.

Rules that apply only within an application would be stored at the application level.

Rules that apply to a specific business process would be stored at the business process level.

Local rules that only apply to a specific rule package would be stored at the lowest level, the rule package level.

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.