Software Engineering for Smart Data Analytics & Smart Data Analytics for Software Engineering
The JT Control Center (CC) shows you all known analyses whose definition was loaded into a certain factbase. It can be opend via the JTransformer Menu –> Control Center.
All operations below work on a single factbase. Therefore, the first step in the CC view is to select a JTransformer factbase by using the drop-down list element at the top left of the CC Table:
The CC table shows the analyses loaded for the selected factbase. If you do not see anything make sure you have loaded ('consulted') a file that contains analysis declarations and implementations. If you switch to another factbase you have to load them again (once per factbase), since each factbase corresponds to a separate JTransformer process, with its own set of analyses and transformations.
In the CC table, the analyses are grouped into categories. In the example above, you can see five analyses in three categories: Correctness, Performance and Useless Code.
Each category has a name and may also have a description.
Analyses additionally have the following columns:
In the CC table, analyses can be activated by selecting the check-box on the left-hand-side of each row. When an analysis is shown for the first time (after having been loaded into the factbase), its default status is deactivated (unchecked).
All checked analyses that have 'on_save' status (see above) are run automatically on the entire factbase whenever a file is saved.
All analyses can be run manually at any time, either using the context menu or using the toolbar of the Control Center.
Whenever an analysis is run (no matter whether manually or automatically), all its old result markers will be deleted and new markers will be created for each found result.
The context menu of the table offers two operations. Both operations affect the currently selected analyses in the table. In the example above, these are nested_db_access and string_concatenation_in_loop.
The operations of the toolbar affect the active analyses. In the example above, these analyses are string_identity_comparison and string_concatenation_in_loop.