Software Engineering for Smart Data Analytics & Smart Data Analytics for Software Engineering
Each instance of the Factbase Inspector contains the following components:
You can open a new Factbase Inspector from the
Select the part of the source code to inspect in the Factbase Inspector and choose Open in Factbase Inspector from the context menu.
The code selection does not need to be exact. The opened Factbase Inspector will show the PEF node which fully contains the selected code and which does not have a child PEF node fully containing the selected code.
If the currently selected Prolog process in the Prolog Console corresponds to a JTransformer factbase, it is possible to open a Factbase Inspector from there. Select an ID in the console (typically a natural number) and select Open In Factbase Inspector from the context menu. The most likely case for opening a Factbase Inspector this way is the execution of a query on the console returning one or multiple IDs which should be inspected.
Select a compilation unit in the Package Explorer and select Open in Factbase Inspector from the context menu.
The FBI shows PEFs in a tree representation. The root PEF of a FBI instance is determined when opening the instance.
For each PEF the FBI shows its term and an icon left to the term indicating its state.
The possible states are explained in the FBI help (see screenshot below). The most important information here is the distinction between PEFs which correspond to elements in source code (green) and PEFs which do not correspond to elements in source code (red).
For each PEF node the FBI also lists
These elements are shown as children in the tree presentation. They are either immediate children of the PEF in the tree or they are separated into groups. Possible groups are the arguments of the PEF containing references to child nodes, relations and unreferenced.
For each PEF shown in the tree the context menu offers several possible actions.
The options allow to customize the FBI behavior and appearance.