Database Entity Relationship Visualization Module

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for visualizing relationships between entity instances in databases are time-consuming, require specialized skills, and produce reports that are not intuitive or easily interpretable, necessitating a mechanism to provide intuitive and flexible visualization of relationships without modifying existing database software.

Innovation Solution

A method that accesses relationship data structures to generate a summary view on a display device, presenting relationship icons and information about unique entity instances, allowing users to rapidly understand relationships between different entity types without requiring modifications to the database software.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If specialized programs are developed to extract relationship information from the database, then accurate relationship reporting is achieved, but development time and cost increase significantly

Engineering Contradiction:
Improverelationship reporting accuracyVSAvoidreport generation time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The database system performs relationship extraction and visualization automatically without requiring external specialized programs. The system queries its own relationship data structure and generates visualizations autonomously, eliminating the need for third-party software development while maintaining accurate relationship reporting.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The database pre-organizes relationship information in a dedicated relationship data structure before reports are needed. This pre-processing of relationship data allows the system to quickly generate accurate relationship reports without time-consuming extraction processes when users need the information.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If specialized database skills are required to generate relationship reports, then report accuracy is maintained, but accessibility to users is reduced

Engineering Contradiction:
Improvereport accuracyVSAvoiduser accessibility
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The system provides self-service relationship visualization capabilities that do not require specialized database skills. Users can access and interpret relationship information through intuitive graphical interfaces and pre-defined queries, eliminating the need for technical expertise while maintaining report accuracy through the system's automated processing.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If existing database software is modified to provide relationship visualization, then customization is achieved, but system complexity increases

Engineering Contradiction:
Improvevisualization customizationVSAvoidsoftware modification complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The relationship visualization functionality is segmented as a separate, modular component within the database system. This dedicated relationship data structure and visualization module can be customized independently without affecting the core database software, allowing adaptability while minimizing overall system complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11693890B2Methods and apparatus for visualizing entity instance relationships in a database
Publication Date: 2023.07.04 SENJALIA BHARGAV
  • US11693890B2 patent drawing
  • US11693890B2 patent drawing
  • US11693890B2 patent drawing

AI summary

A method, apparatus, and non-transitory computer-readable storage medium for generating and presenting information identifying relationships between entity instances in a database that has a plurality of entity structures.