GenAI Software Architecture Diagrams from Siloed Communications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large organizations face challenges in maintaining synchronized and up-to-date software architecture diagrams across siloed systems, leading to inefficiencies in internal management and external audits, as architects often work in isolation and audits rely on outdated diagrams.

Innovation Solution

A generative artificial intelligence (GenAI) model is trained on software architecture documents to understand correlations between text and diagram components, generating accurate, real-time diagrams from runtime data and integrating partial views to identify missing components and provide recommendations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If architects work in siloed environments managing individual software systems, then each architect can focus on their specific system, but the overall software architecture ecosystem becomes disconnected and outdated diagrams are produced

Engineering Contradiction:
Improvearchitect workflowVSAvoidarchitecture ecosystem visibility
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent combines multiple partial architecture diagrams from different siloed systems into a single comprehensive architecture diagram. The system automatically integrates diagrams from various software systems (email system, database system, etc.) to create a unified view of the entire architecture ecosystem, eliminating information loss while maintaining individual architect workflows.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If external audits are performed using traditional architecture diagrams, then licensing rights and compliance gaps can be verified, but the diagrams are often outdated and do not reflect the current real-time software system state

Engineering Contradiction:
Improveaudit accuracyVSAvoiddiagram update timeliness
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent transforms static architecture diagrams into dynamic, automatically updating diagrams that reflect the current state of software systems in real-time. The system continuously monitors and updates the architecture diagram based on current system configurations and runtime data, ensuring audit accuracy without time delays.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary actions by continuously maintaining updated architecture diagrams before audits are conducted. Rather than creating diagrams at the time of audit, the system proactively keeps diagrams current through automated updates, ensuring readiness for any audit at any time.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If comprehensive software architecture diagrams are manually created and maintained, then complete architecture views can be achieved, but the process is time-consuming and diagrams become outdated quickly

Engineering Contradiction:
Improvearchitecture completenessVSAvoiddiagram maintenance efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent implements self-service automation where the system automatically generates, updates, and maintains comprehensive architecture diagrams without requiring manual intervention. The system autonomously collects data from software systems, processes runtime information, and updates diagrams, eliminating the time-consuming manual process while maintaining complete architecture information.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system establishes continuous feedback loops between software systems and architecture diagrams. Runtime data and system changes automatically feed back into the diagram generation process, ensuring diagrams remain synchronized with the actual software architecture state without manual updates.

Inventive Principle:
Principle #23Feedback

4Loss of information

If multiple software systems are integrated into a unified architecture view, then complete ecosystem visibility is achieved, but the complexity of managing and synchronizing all systems increases

Engineering Contradiction:
Improveecosystem visibilityVSAvoidarchitecture management complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent applies segmentation by maintaining a modular structure where the comprehensive architecture diagram is composed of integrated partial diagrams from individual systems. Each system's architecture diagram remains a separate, manageable unit that can be independently updated, while the system automatically assembles them into a unified view, reducing management complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12399687B2Generating software architecture from conversation
Publication Date: 2025.08.26 THE TORONTO DOMINION BANK
  • US12399687B2 patent drawing
  • US12399687B2 patent drawing
  • US12399687B2 patent drawing

AI summary

An example operation may include one or more of receiving and recording electronic communications that occur between users of an organization within a data store, receiving an input via a user interface, retrieving the electronic communications of the organization and software architecture documents from the data store in response to receipt of the input, generating a diagram of a software architecture of the organization based on execution of a generative artificial intelligence (GenAI) model on the electronic communications of the organization and the software architecture documents, and displaying the diagram of the software architecture via a user interface.