Application Dependency Visualization Through Runtime Flow Monitoring

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Organizations face challenges in visualizing and updating application dependency diagrams across different formats and locations, leading to inefficiencies and risks of sharing outdated information, which requires time-consuming manual redraws and resource wastage.

Innovation Solution

An application mapping engine monitors and analyzes process and data flows during runtime to generate dependency visualization maps, leveraging existing sources of dependency information and incorporating machine learning for updates and improvements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual redrawing of dependency maps is performed, then diagrams can be updated to reflect current state, but time consumption and resource wastage increase significantly

Engineering Contradiction:

Improveaccuracy of dependency informationVSAvoidtime for manual redrawing

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system automatically monitors application runtime execution and self-updates dependency maps without requiring manual intervention. The application mapping engine continuously tracks process and data flows, generating updated dependency visualizations autonomously as applications evolve.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The dependency mapping process becomes continuous through automated runtime monitoring. Instead of periodic manual updates, the system operates continuously to capture dependency changes as they occur during application execution.

Inventive Principle:

Principle #20Continuity of useful action

2Adaptability or versatility

If dependency diagrams are created in various formats and stored in multiple locations, then flexibility in representation is achieved, but complexity of management and interpretation increases

Engineering Contradiction:

Improveformat flexibilityVSAvoidcomplexity of diagram management

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system establishes a universal dependency map format that serves multiple purposes: visualizing dependencies, documenting architecture, communicating with stakeholders, and updating automatically. This single standardized format replaces the need for multiple different diagram styles and storage locations.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Productivity

If existing dependency information sources are leveraged, then existing work is utilized, but outdated and inaccurate information may be propagated

Engineering Contradiction:

Improveutilization of existing informationVSAvoidaccuracy of dependency information

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system implements feedback loops where runtime monitoring continuously validates and updates dependency information. Execution traces and monitored process flows provide feedback that corrects and updates dependency maps, ensuring accuracy while leveraging existing information sources.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS12353856B2Application dependency visualization

Publication Date: 2025.07.08 BANK OF AMERICA CORP

AI summary

An application mapping engine may determine dependencies in existing executable application by monitoring and analyzing process flow and data flow of the application during runtime execution. The application mapping engine may generate dependency visualization maps that illustrate dependency interaction information.