Model-Oriented Debugging View for Business Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current debuggers are limited to debugging application code binary or source classes and cannot effectively debug business applications using models and meta-models on which they are based.
Innovation Solution
A model-oriented debugging system and method that generates a debugging view based on models and meta-models, allowing for the detection of problems and the association of debugging data to create breakpoints within the model-oriented debugging view, enabling debugging of executing business applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If current debuggers are used to debug application code binary or source classes, then debugging of compiled code is possible, but debugging of models and meta-models is not possible
Solution Approach 1:
The patent introduces an intermediary component that maps between the model layer and the compiled code layer. This intermediary enables debugging information to be transmitted from the execution environment back to the model-oriented debugging view, allowing developers to debug models indirectly through their compiled representations while maintaining model-level visibility.
Solution Approach 2:
The patent adds a new dimension to debugging by creating a model-oriented debugging view that operates parallel to the traditional code-level debugging. This additional debugging dimension allows simultaneous viewing of execution state both at the model level and the code level, enabling comprehensive debugging without losing model-level information.
2Ease of manufacture
If model-oriented development is used to provide code-free development platform, then ease of development is improved, but ability to debug models is lost
Solution Approach 1:
Instead of requiring developers to debug compiled code to find model issues (the conventional approach), the patent inverts the debugging flow by capturing execution information and mapping it back to the model layer. This allows developers to debug models directly in their familiar model-oriented environment without needing to understand the underlying compiled code.
Solution Approach 2:
The patent creates a copy of the execution state and debugging information in the model-oriented debugging view. This virtual copy mirrors the actual execution state at the model level, allowing developers to interact with and debug model elements directly without affecting or needing to understand the compiled code representation.
3Measurement precision
If traditional debugger is used to debug application code, then code-level debugging is possible, but model-level debugging is not possible
Solution Approach 1:
The patent merges model-oriented debugging capabilities with traditional code-level debugging into a unified debugging system. The model-oriented debugging view integrates with the existing debugger infrastructure, allowing developers to switch between or simultaneously view both model-level and code-level debugging information within a single integrated environment.
Data Source
AI summary
A system and method for debugging a business application that has been generated according to a model are disclosed. A system includes a debugger that generates a model-oriented debugging view based on a model-oriented development environment that generates the business application. The model-oriented debugging view uses debugging information determined from a Java virtual machine that executes the business application to generate one or more breakpoints in the model-oriented debugging view.


