AU - Application Understanding
This procedure helps you to identify the functions of your systems.
Application Understanding (AU) is a tool that extracts business logic and other relevant information from source code. But it is also the method we use to analyze your systems.
The Application Understanding procedure can be used independently of the Business Flow Suite, our modernization tool. This procedure helps you to identify the functions of your systems.
The source code is the truth!
Whatever you are planning to do with the source code - development according to brownfield, rewrite the code or development in a different procedure - you have to know the business logic of your application
For this reason, we work according to our concept: "The source code is the truth".
The Application Understanding method scans your application and extracts the business logic without considering other irrelevant parts, such as logging or management parts.
Code analysis is classically a top-down process. The risk here is that the complexity grows in this direction.
Application Understanding detects the output endpoints in the code.
Our Application Understanding method has the opposite approach: it detects the output endpoints in the code. From here, it goes back and collects all the code fragments that lead to that data point.
The Application Understanding method can be used for different languages. Please feel free to contact us if you are interested.
Due to the constantly growing number of cloud architectures and the resulting transformations, application requirements and program structures are also changing. Often, transformed applications are not optimally designed for these architectures. Many currently existing Java applications are not exempt from this. Therefore, we have made it our goal to perfectly adapt our existing application understanding to Java.
This tool analyzes and improves the cloud capability of your existing Java code
This resulted in our web-based AU4J (Application Understanding for Java). This tool analyzes and improves the cloud capability of your existing Java code so that you are prepared for the future.
Our AU4J integrates easily with IDE (a JetBrains IntelliJ IDEA plugin is also available). Moreover, it provides several other features besides business logic extraction to support your application maintenance and brownfield development.
Scan & Analysis
Scan, comparative study and analysis of the application based on the program / source code.
After the analysis, the hierarchy of application modules is displayed.
Dead Code Analysis
Unused parts of the program code in the application are identified. The recursive algorithm also identifies code elements that are not called.
A list of application entities is displayed. The structure of these entities can be arranged in a list side by side.
All named and in-line queries of the application are enumerated. JPQL and SQL generations are displayed.
For various reasons, it is often necessary to find the source of an SQL query. Based on a specific SQL query, this function identifies the command in the code and returns it. With one click, the complete code of the query is thus displayed.
An innovative "business rule extraction" technology based on new procedures.
This function got its name from the medical field, angiography. It displays the connected source code parts with endpoints. If an output endpoint is found and displayed, the function colors, in a chosen color, the part of the code that led to this endpoint. The same happens with the input endpoints. Here, the source code sections that lead out of and process this point are colored.
The Application Understanding (AU) is connected to the version management system in which the source code is located. If there are changes in the source code, the software uses the commit identifier to indicate which functions (user cases) need to be tested. This avoids a complete, time-consuming regression test. This feature saves enormous operational and development efforts.
The AU provides important answers to security-related questions. Security experts and hackers look for and exploit vulnerabilities in systems.
They evaluate them according to their financial value. But often you don't see the value of a system before information is extracted. Here, the damage is often higher than the actual value. This function got its name from the medical field, angiography. It uses endpoints to display the connected source code parts. If an output endpoint is found and displayed, the function colors, in a chosen color, the part of the code that led to this endpoint. The same happens with the input endpoints. Here, the source code sections that lead out of and process this point are colored.
Collects all terms as names that are used in the application. Guides the user through the context in which different expressions and words are used. This helps standardize the system and develop a common language base for the users and developers. Also allows the developer to mix expressions if the system is not developed in only one programming language.
Shows the average complexity of the elements in the module - class - methods - hierarchy. With this, test efforts can be estimated and it shows methods that can only be maintained in the source code with effort.
You have questions?
Our experts support you and are here to help you with any questions you may have.