The Business Rule Framework has a fantastic simulation capability, but it can become quite overwhelming for those not familiar with the tool. When you want to test BRF+ functions with users, then your audience is not interested in the functionality you are using to solve complex decision making. Showing this tool to business users can distract from the objective to verify whether you understand their business requirements correctly.
Your objective is to have sessions with users where they provide the input for decision making and validate the result. This simulation process must be as straightforward as possible.
You can prototype the business requirements for preliminary acceptance testing. There is no need to take action on the returned result. You can develop an ABAP program that is a wrapper around the BRF+ function with the input parameters as selection criteria and a simple output to show the result.
When you have this program, then use variants to save all identified test scenarios and keep track on which passed or failed the criteria. Your prototype is then fit for purpose when all tests are successful.
If new test scenarios arise, then merely add new variants to the program and check if the prototype requires updates to pass the tests.
Creating these wrapper programs will be quick and easy. You can deploy them to the productive system because the database is never updated. These programs can even be useful to assist the support team to test specific scenarios.
You can always resort to the in-depth simulation tool output within the Business Rule Framework to look step-by-step what happens while making complex decisions.
Wrapper programs can have their dedicated transaction codes and listed in a specific custom menu. The IT support team can get the authorisation to execute these transactions in every environment.
Applying all these suggestion will make acceptance testing ahead of development a time-saving activity, pushing higher efficiency and productivity.
At the same time, you can demonstrate all tests performed to get the preliminary acceptance from the key users by listing all variants and recording which have passed the test. You can make this a prerequisite for documenting the final solution before a single line of code is written to execute BRF+ functions.