OpenRules Explorer is a Graphical Integrated Decision Modeling Environment that includes automatically built Diagrams for business decision models such as in the above image.
Each OpenRules Decision Manager project includes the batch file “explorer.bat” that starts the Explorer. For example, the above Explorer’s view will be displayed when you double-click on this file from the standard decision project “PatientTherapy“. You can click on the icon in the title bar to select any other decision model project.
When you open OpenRules Explorer from the folder with an existing decision model for the first time, it will generate its diagram using only goals and sub-goals. This diagram reflects the Goal-Oriented Decision Modeling approach described in this book and in general follows the DMN (Decision Model and Notation) graphical convention for decision requirement diagrams. All goals are shown as yellow rounded rectangles and the main goals has a red border. The arrows between goals show the automatically (!) discovered knowledge relationships, e.g. the goal “Recommended Dose” depends on the sub-goal “Patient Creatinine Clearance”.
You don’t have to draw the diagram yourself as it’s being AUTOMATICALLY generated based on already defined glossary, goal/sub-goals, and tables that specify their logic.
The file structure of the rules repository has shown in the left panel:
A double-click on a file in this panel or on any node inside the diagram opens the corresponding Excel file. You can hide/show this panel by a click on in the top left corner.
You may create different diagrams of the same decision model by selecting different elements from the legend on the right. For example, if you select only “Goals” in the legend, the diagram may look as follows:
If you also select “Tables“, all related decision tables (and other business knowledge model elements such as “Decision”, “DecisionService”, “Code”, “Method”) will be shown as blue rectangles:
The dashed arrows from a blue table to a goals prompts you that this table contains the logic that specifies this goal.
You may also select “Input Data“, then all decision variables will be shown as white rounded rectangles with dashed lines to the goals that use them:
You may hide the “Input Data” and select “Concepts” to show the business concepts described in your glossary. They will be shown as pink rounded rectangles:
When you click on an concept or an input node all related dashed links will be highlighted.
You can easily adjust diagrams in many ways. You may drag any nodes around and all arrows will follow your changes.
You can use green navigation buttons in the bottom to move the image around, to zoom in/out, or click on to center the diagram.
You can click on the button “Export PDF” to export the diagram to the PDF format in the file of your choice.
Here is an example of the automatically generated diagram for a more complex decision model “Bureau Strategy” used in our sample decision model library for the Loan Origination domain:
In this example decision models “Bureau Strategy” and “Routing” are deployed as AWS Lambda decision services and them these two services are used by the decision model “Loan Origination Result” described at this diagram:
This decision model is not aware of the internal structure of these two decision services which are shown as green rectangles. However, we can see the decision table “LoanOriginationResult” that invokes these services and business concepts (pink rounded rectangles) used by these services.
When a decision model iterates over collections of objects and sorts some of them like in a quite complex decision model “Flight Rebooking“, the automatically generated diagram explains complex relationships by putting clarifying labels “Iterate”, “Execute”, and “Sort” on the proper links: