Systems for application and data dependency identification, visualization, and management

Patent metadata

Field	Value
Publication number	US-12436748-B2
Application number	US-202318181132-A
Country	US
Kind code	B2
Filing date	Mar 9, 2023
Priority date	Mar 9, 2023
Publication date	Oct 7, 2025
Grant date	Oct 7, 2025

Abstract

Systems for application and data dependency identification, visualization, and management. In some embodiments, a plurality of dependency harvester applications/plugins may be utilized to automatically source dependency data that is then translated and/or converted into a standardized format that is utilized to generate and/or identify dependency relationships, e.g., across disparate computing platforms and/or environments. The results of these automatically-identified dependencies may then be utilized, for example, to provide an interface to project implementation personnel that can point out and/or quantify predicted errors. Such an automated dependency identification/harvesting system can dramatically reduce both personnel and time-to-implementation costs of projects implemented in a computing environment, particularly where the computing environment comprises a plurality of complex data and/or application interdependencies and/or relationships.

First claim

What is claimed is:

1. A system for automatic application dependency mapping, comprising:
at least one electronic processing device; and
at least one non-transitory memory device in communication with the at least one electronic processing device, the at least one non-transitory memory device storing (i) a plurality of extensible dependency harvester plugin modules, (ii) rules defining a dependency harvester engine, (iii) rules defining a dependency data transformation engine, (iv) dependency visualization interface rules, and (v) operating instructions, that when executed by the at least one electronic processing device, result in:
executing a first calling, by an execution by the at least one electronic processing device of the rules defining the dependency harvester engine, of each extensible dependency harvester plugin module of the plurality of extensible dependency harvester plugin modules;
identifying, by each extensible dependency harvester plugin module of the plurality of extensible dependency harvester plugin modules and in response to the first calling, and by activating a first subsystem in communication with the respective extensible dependency harvester plugin module of the plurality of extensible dependency harvester plugin modules, a first application dependency, wherein the first subsystem resides in a first environment;
generating, by each extensible dependency harvester plugin module of the plurality of extensible dependency harvester plugin modules, data descriptive of the identified first application dependency;
translating, by the execution by the at least one electronic processing device of the rules defining the dependency harvester engine, the data descriptive of the identified first application dependencies into a standardized format that represents the identified first application dependencies;
storing, by the execution by the at least one electronic processing device of the rules defining the dependency harvester engine and in a database, the data descriptive of the identified first application dependencies in the standardized format that represents the identified first application dependencies;
processing, by an execution by the at least one electronic processing device of the rules defining the dependency data transformation engine, the stored data descriptive of the identified first application dependencies in the standardized format that represents the identified first application dependencies, wherein the processing comprises generating processed first application dependency data by executing at least one functionality of (i) aggregating portions of the stored data that are descriptive of an identical dependency and (ii) creating a relationship between two or more portions of the stored data that share a common dependency; and
outputting, via a graphical user interface (GUI) and by an execution by the at least one electronic processing device of the dependency visualization interface rules, a graphical mapping of a set of the processed first application dependency data.

2. The system for automatic application dependency mapping of claim 1 , wherein the processing of the stored data descriptive of the identified first application dependencies in the standardized format that represents the identified first application dependencies, further comprises:
identifying, for each identified first application dependency, a characteristic of the identified first application dependency; and
computing, based on the identified characteristic of the identified first application dependency and for each identified first application dependency, a score.

3. The system for automatic application dependency mapping of claim 2 , wherein the graphical mapping of the set of the processed first application dependency data comprises a graphical indication of the scores for the identified first application dependencies of the set of the processed first application dependency data.

4. The system for automatic application dependency mapping of claim 2 , wherein the identified characteristic of the identified first application dependency comprises a number of times that the identified first application dependency is found within the stored data descriptive of the identified first application dependency in the standardized format that represents the identified first application dependencies, and wherein the score comprises a confidence level score.

5. The system for automatic application dependency mapping of claim 2 , wherein the identified characteristic of the identified first application dependency comprises a measure of an amount of errors identified for communications pursuant to the identified first application dependency, and wherein the score comprises a resiliency score.

6. The system for automatic application dependency mapping of claim 2 , wherein the identified characteristic of the identified first application dependency comprises a measure of a volume of messages identified for communications pursuant to the identified first application dependency, and wherein the score comprises a critical path score.

7. The system for automatic application dependency mapping of claim 2 , wherein the execution of at least one of (i) the plurality of extensible dependency harvester plugin modules, (ii) the rules defining the dependency harvester engine, (iii) the rules defining the dependency data transformation engine, (iv) the dependency visualization interface rules, and (v) the operating instructions, by the at least one electronic processing device, further results in:
computing, by the at least one electronic processing device and based on a plurality of scores for the identified first application dependencies, a health metric for the at least one of the first subsystems.

8. The system for automatic application dependency mapping of claim 7 , wherein the graphical mapping of the set of the processed first application dependency data comprises a graphical indication of the health metric for the at least one of the first subsystems.

9. The system for automatic application dependency mapping of claim 7 , wherein the at least one non-transitory memory device further stores (vi) artificial intelligence (AI) application dependency architecture analysis rules, and wherein the generating of the processed first application dependency data further comprises:
identifying, by an execution by the at least one electronic processing device of the AI application dependency architecture analysis rules, a pattern among the identified first application dependencies;
comparing, by the execution by the at least one electronic processing device of the AI application dependency architecture analysis rules, the identified pattern to stored data descriptive of historic application dependency patterns; and
generating, by the execution by the at least one electronic processing device of the AI application dependency architecture analysis rules and based on the comparing, an error prediction for at least one of (a) the first subsystems and (b) at least one of the identified first application dependencies.

10. The system for automatic application dependency mapping of claim 7 , wherein the generating of the processed first application dependency data further comprises:
identifying, by the at least one electronic processing device and based on the health metric for the at least one of the first subsystems, at least one application dependency error.

11. The system for automatic application dependency mapping of claim 10 , wherein the execution of at least one of (i) the plurality of extensible dependency harvester plugin modules, (ii) the rules defining the dependency harvester engine, (iii) the rules defining the de

Assignees

• Travelers Indemnity Co

Inventors

• Michelsen Yushen C
• Li Chunlei
• Maharjan Subash
• Su Yuan
• Lin Andrew
• Rollins David

Classifications

• G06F9/44526

  Plug-ins; Add-ons · CPC title

• G06F8/433 Primary

  Dependency analysis; Data or control flow analysis · CPC title