Wiki Home

The Business Rules Manifesto

Namespace: WIN_COM_API


Principles of rule independence

This material is also available in PDF format

The Business Rules Manifesto*

1. Rules are a first-class citizen of the requirements world.
2. Rules are essential for, and a discrete part of, business models, system models, and implementation models.
3. Rules are not process and not procedure.  They should not be embedded in either of these.
4. Rules build on facts, and facts build on concepts as expressed by terms.
5. Terms express business concepts; facts make assertions about these concepts; rules constrain and support these facts.
6. Rules must be explicit.  No rule is ever assumed about any concept or fact unless a rule has been specified explicitly.
7. Rules are basic to what the business knows about itself -- that is, to basic business knowledge.  Rules need to be nurtured, protected, and managed.
8. Rules are about business practice and guidance; therefore, rules are motivated by business goals and objectives and are shaped by various influences.
9. Rules should be expressed declaratively for the business audience, in natural-language sentences.  If something cannot be expressed, then it is not a rule.
10. Rules are best implemented declaratively.  Rules are based on truth values.  How a rule ís truth value is determined or maintained is hidden from users.
11. Rules are explicit constraints on behavior and/or provide support to behavior.
12. Rules generally apply across processes and procedures.  There should be one cohesive body of rules, which should be enforced consistently across different areas of business activity.
13. The relationship between events and rules is generally many-to-many.
14. A rule statement is distinct from the enforcement level defined for it.  These are separate concerns.
15. Rules should be defined independently of responsibility for the who, where, when, or how of enforcement.
16. Rules often require special or selective handling of detected violations.  Such rule violation activity is activity like any other activity.
17. Rules define the boundary between acceptable and unacceptable business activity.
18. To ensure maximum consistency and reusability, the handling of unacceptable business activity should be separable from the handling of acceptable business activity.
19. Exceptions to rules are expressed by other rules.
20. Rules always cost the business something.  This cost must be balanced against business risks.
21. Rules should arise from knowledgeable business people.
22. Business people should have tools available to help them develop and manage rules.
23. In the long run, rules are more important to the business than hardware/software platforms.
24. Rules should be managed in such a way that they can be readily redeployed to new hardware/software platforms.
25. A business rule system is never really finished because it is intentionally built for continuous change.
26. Rules, and the ability to change them effectively, are key to improving business adaptability.

Copyright, 2003. Business Rules Group.
Permission is granted for unlimited reproduction and distribution of this document under the following conditions: (a) The copyright and this permission notice are clearly included. (b) The work is clearly credited to the Business Rules Group. (c)No part of the document, including title, content, copyright, and permission notice, is altered, abridged, or extended in any manner.

Category Business Rules
( Topic last updated: 2003.06.17 09:52:43 AM )