Execution Path Tracking for Dynamic Software Transparency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software applications lack transparency in their algorithms, making it difficult for users to understand how calculations are performed and which data or functions contribute to the final output, leading to user frustration and potential inaccuracies.

Innovation Solution

A computer-implemented method that tracks and displays the execution path of dynamic functions in a software system, allowing users to visualize how changes in input values or calculation attributes affect the final results, and providing a summary of attribute value changes between execution runs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software applications use complex algorithms with multiple functions and intricate calculations, then the functionality and processing capability are improved, but the transparency and understandability of the algorithms deteriorate

Engineering Contradiction:
ImprovefunctionalityVSAvoidtransparency
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces an execution path tracker as an intermediary component that monitors and records the execution flow of complex algorithms. This tracker captures function calls, parameter values, and calculation steps, presenting them in a structured format that maintains the full functionality of complex algorithms while making the execution process transparent and traceable to end users.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If software systems hide underlying calculations in hidden and non-transparent code, then the system complexity is reduced and ease of operation is improved, but the ability to identify contributing data and functions deteriorates

Engineering Contradiction:
Improveease of operationVSAvoidtraceability
Core Design Contradiction:
Ease of operationVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements preliminary action by pre-instrumenting the software system with tracking code that automatically records execution paths, function calls, and parameter values before the actual calculations occur. This allows the system to maintain simple, hidden code for ease of operation while simultaneously capturing detailed traceability information about which data and functions contribute to final results.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If software applications provide detailed information about algorithm execution, then the transparency and user understanding are improved, but the device complexity and information processing requirements increase

Engineering Contradiction:
ImprovetransparencyVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the execution path tracking into distinct modular components: function call interceptors, parameter value capture modules, calculation step recorders, and result presentation interfaces. Each segment handles a specific aspect of transparency provision, allowing detailed information to be delivered without overwhelming system complexity, as each module can be independently managed and optimized.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250139550A1Autonomous mechanism for tracking execution paths in dynamic systems
Publication Date: 2025.05.01 ORACLE INT CORP
  • US20250139550A1 patent drawing
  • US20250139550A1 patent drawing
  • US20250139550A1 patent drawing

AI summary

Systems, methods, and other embodiments associated with tracking execution paths in dynamic systems are described. In one embodiment, a method includes, for a first set of input values, executing a first execution of dynamic functions to generate a first final result, wherein calculation attributes have a first set of values during run-time. In response to a change, re-executing the dynamic functions to generate a second final result in a second execution. During the second execution, track the dynamic functions that were executed and determine an execution path during the second execution. The method determines, from the functions that were executed, how calculation expressions are calculated during the second execution. The execution path is visually displayed that visually shows a sequence of executed dynamic functions and/or a summary of tracking results to visually identify attribute value changes between the first execution and the second execution.