RuleXpress Overview

RuleXpress is a repository-based tool that can be used offline or in a multi-user environment. Within the tool the key organizing principle is that of a community; a group of people who share the same understanding about their vocabulary and rules. The key activities are to manage vocabulary and rules or, more specifically, terms, fact model, rules, decision tables and rule groups.

Editing Rules

A – Helper List Buttons
B – License Information
C – Navigation History
D – Multi Expression Editor
E – Current Community
F – Current User
G – Task Selection
H – Task Navigation Buttons
I – Helper List Tabs
J – Editor Tabs

RuleXpress displays a list of the defined terms and the user can see and manage the definition of each. All referenced terms in a definition are automatically hyperlinked as they are typed. A usage tab shows recursively where a term is used so, for instance, one can see the rules that use a term then explore the terms that are used by those rules and so on. Terms can be words or phrases and can be disambiguated using a suffix. Users can define synonyms and identify which terms are preferred.

Editing Terms

The tool really wants business people to use their own words. Quality rules exist and are applied to give each definition and rule a Quality Grade.

Quality Overview

Rules are managed in a similar style but instead of a definition there is a rule statement for each rule. Rules also have a different set of quality rules including such things as their use of preferred (rather than discouraged) synonyms. Decision tables are included as a very free form way to let users lay out a table or rules. The tool links terms but enforces few other restrictions on these tables. Similarly, Rule Groups are also free form and available just as an organizing layer for rules.

Rule Groups

Properties (metadata) for all objects are defined but can be extended by the user. For instance, the implementation details and document sources can be added. Properties can have pick lists and data types as well as multiplicity and nested properties so the user has complete control over the information being collected.

Reporting includes the option to produce an XML format (actually an intermediate step anyway) or go ahead and apply a style sheet to produce a finished report. The reporting framework gives some control over which classes to report, what relationships to include and a filter ? a where clause if you like. Reports (and filters) are manageable items so they are stored in the repository, can be created locally, promoted and shared etc.