Unified Executable Code for Business Application Debugging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy business application systems face difficulties due to the physical separation of business data and rules, making it challenging to understand, create, debug, and modify them without causing unintended effects, as the relationships between configuration data and rules are not clearly defined.
Innovation Solution
The system translates business application structures into user-friendly object-oriented programming (OOP) models, allowing for the organization and presentation of execution information, enabling easier understanding, manipulation, and modification of business applications by representing configuration data and rules as OOP objects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If business data and rules are stored in physically separate table data structures, then data storage and processing can be simplified, but understanding, debugging, and modification become difficult due to lack of clear relationships between configuration data and rules
Solution Approach 1:
The patent combines physically separate configuration data tables and rules tables into a unified executable code structure. The generation module creates executable code that integrates both data and rules, allowing them to be processed together while maintaining their functional separation. This resolves the contradiction by merging the physical storage separation with logical integration for easier debugging and modification.
Solution Approach 2:
The patent introduces an intermediate executable code layer that acts as a mediator between the separate configuration data and rules. This executable code contains both the configuration data and rules in a unified structure, serving as an intermediary representation that makes relationships explicit and accessible for debugging and modification without changing the underlying separate table storage.
2Ease of manufacture
If configuration data and rules are stored in separate tables, then data management becomes easier, but runtime interactions and relationships between data and rules are not statically determined
Solution Approach 1:
The patent performs preliminary action by generating executable code that explicitly encodes the relationships between configuration data and rules before runtime. The generation module creates a unified executable structure that pre-establishes all relationships, so that during runtime, the interactions are already determined and visible in the code structure, eliminating the loss of relationship information.
3Adaptability or versatility
If business application structures are maintained in traditional table-driven format, then legacy system compatibility is preserved, but understanding and manipulation become difficult without user-friendly representation
Solution Approach 1:
The patent creates a copy of the business application structure in the form of executable code that provides a user-friendly representation. The executable code is generated from the traditional table-driven format, preserving the original data and rules while creating an accessible executable version that is easier to understand and manipulate, without losing legacy system compatibility.
Data Source
AI summary
Embodiments of methods and systems consistent with the present invention enable data-focused analysis of an application by reorganizing execution information generated by an application into categories associated with the data objects used by the application, and displaying or otherwise using the reorganized information for analysis, debugging, execution tracing, etc. of the application. Thus, the application execution information is presented from the data standpoint instead of from the execution sequence standpoint.