Question

At work, we have optimization engines, and one of the inputs used by these engines are business rules, which we create and edit with a proprietary rule editor.

These rules are of our own proprietary format, because the existing rule engines were not capable of representing the business rules of the complexity we required.

Anyhow, we are more or less happy with the way that the rules engine currently works – it works really well with complex business rules, but are not happy with the user interface (rule editor). Basically this currently consists of a set of tables that are edited, literally, using a complex spreadsheet-like tabular GUI.

While this is functional, it is an atrocious interface to present to end users who are not developers but are the equivalent of business analysts. Before getting my hands dirty, I thought it would be a good idea to ask the StackOverflow community’s opinion on user interface design specific to this situation.

My Question

• What are some of the best user interfaces you have seen out in existing rule editors?
• What do you think are the best principles behind the design of user interfaces, in rule editors.

---

I use the terms rule engine and rule editor separately. For this question, I am concerned only with the rule editor

Other questions on StackOverflow that address rules-engines, but neither rule editors nor their user interface design:

• Criteria to Evaluate Business Rules Engines
• When should you NOT use a Rules Engine?
• What rule engine should I use?
• When is a Business Rules Engine used
• How to design a rule engine?
• Prefered methods for interacting with a rules engine

Answer 1

Note: This isn’t an answer to your specific question, but a suggestion.

I’m making two assumptions here, that

1. Your tool addresses an existing business workflow (i.e. you’re not adding a new process, just trying to simplify an existing process), and
2. Your tool improves on an existing tool

This being the case, your best source for UI inputs are your end users (in this case, the business analysts). For instance, if they are already comfortable using MS Excel for all their other tasks, a spreadsheet-like interface may not be as bad an idea as you think.

You could take a look at Contextual Design methods to find out what your users’ mental model for the system is. You could also try low-fidelity prototypes with fast turnaround times (like paper prototypes or VB mockups) to see what works best.