Application Lineage Metadata Registration via Code Annotation Scanning

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current tools fail to efficiently register and maintain application metadata across hybrid cloud environments, leading to unsustainable manual governance processes and outdated metadata, which diverts software engineers from coding and hampers business value.

Innovation Solution

A system and method that automatically generates and stores application lineage metadata by scanning code for annotation markers, generating registry information, and providing visualization data, enabling efficient registration and governance through an interactive interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual portfolio management and governance processes are used to track application metadata, then software engineers can maintain registration metadata, but the processes become unsustainable and divert engineers from coding

Engineering Contradiction:

Improvemetadata accuracyVSAvoidsoftware engineering productivity

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system enables self-service by having the code scan itself for annotation markers and automatically generate registry information. The build process initiates the scanning and generation without human intervention, allowing the system to maintain its own metadata automatically.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

Annotation markers are embedded in the code during the development phase, preparing the metadata information in advance. The build process then automatically retrieves this pre-prepared information to generate registry data before deployment, eliminating the need for manual post-deployment metadata management.

Inventive Principle:

Principle #10Preliminary action

2Loss of information

If conventional tools are used to register component level metadata, then some metadata can be tracked, but the tools fail to provide a view into dependencies and require manual maintenance

Engineering Contradiction:

Improveapplication lineage visibilityVSAvoidmetadata management complexity

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The system provides multi-functionality by simultaneously scanning code for annotation markers, generating registry information, visualizing application lineage, and analyzing dependencies all through a single automated build process, replacing multiple manual tools with one unified system.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Annotation markers serve as intermediaries between the code and the metadata generation system. These markers embed lineage information directly in the code, allowing the build process to automatically extract and process dependency relationships without manual intervention.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Measurement precision

If software engineers manually maintain registration metadata to ensure it is up to date, then metadata accuracy can be maintained, but engineers spend extra time away from coding

Engineering Contradiction:

Improvemetadata currencyVSAvoidsoftware engineer time

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The code maintains its own metadata by scanning for annotation markers during the build process. This self-service approach ensures metadata is automatically updated whenever code is built, eliminating the need for engineers to manually maintain registration information.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The automated metadata generation is integrated into the continuous build process, ensuring metadata is continuously updated whenever code changes. This continuous action replaces discrete manual maintenance efforts, keeping metadata current without requiring dedicated engineer time.

Inventive Principle:

Principle #20Continuity of useful action

4Adaptability or versatility

If manual governance processes are used in hybrid cloud environments, then some level of control can be maintained, but the processes become unsustainable as the application landscape grows

Engineering Contradiction:

Improvegovernance scalabilityVSAvoidgovernance efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system replaces manual mechanical governance processes with an automated computational system. The build process automatically scans code, generates registry information, and produces visualizations, substituting human manual work with automated mechanical processes that scale efficiently.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

Annotation markers are embedded in code during development, preparing governance information in advance. This preliminary action allows the automated system to process metadata efficiently at build time, enabling scalable governance without manual intervention as the application landscape grows.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11762636B2Method and system for implementing application lineage metadata and registration

Publication Date: 2023.09.19 JPMORGAN CHASE BANK NA

AI summary

The invention relates to a system that implements application lineage metadata and registration. An embodiment of the present invention is directed to auto-generating Application Lineage data. This may be accomplished by implementing code markers, such as @Annotations, within the code. An embodiment of the present invention may scan the code each time a build is kicked off by a continuous integration and continuous delivery (CI/CD) pipeline. At the end of the build, the documentation may be automatically generated with application lineage information.