Why Use Business Rules?
Using the USoft TeamWork Business Rules repository instead of more conventional requirement checklists gives you many benefits.
You re-use the repository approach of USoft application development for requirements. You get multi-user, single-point-of-definition access to versioned and traceable requirements. This contrasts favorably with the confusion often caused when you use (versions of) requirement listings in documents. Such documents tend to multiply as they are sent back and forth between parties.
You can make reports of cross-sections of the rule repository by using the many ways in which rules can be classified. For example, it is easy to get a list of all the rules about a certain topic that were added after a certain date and that have high priority.
You can make cross-references between the rule repository and the implementation repository. If you do, it becomes very easy to trace implementations. For example, if a Business Rule is dropped it becomes very easy to drop the corresponding implementation(s) at the same time.
You benefit automatically from database facilities such as security and backup.
Changes to business rules are automatically logged by USoft TeamWork.
Even instructions that describe to the end user how to operate the system are ultimately business rules. Using USoft TeamWork You can re-use business rule definitions as a quick start for end user documentation.