Venn Diagram Interface for Database Relationship Visualization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional database systems confuse users when presenting relationships, making it difficult to understand and correctly construct data relationships, leading to errors and increased cognitive load during report generation.

Innovation Solution

A visual representation system using geometric shapes, such as ovals, to indicate data objects and their relationships, providing a Venn diagram-like interface that highlights overlapping areas to represent common data contributions, along with a thumbnail sketch of the expected report, facilitating easier understanding and correction of relationships.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional database systems present relationships using text-based queries and tables, then data retrieval functionality is maintained, but user confusion and cognitive load increase

Engineering Contradiction:
Improveease of useVSAvoidrelationship construction complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent creates visual copies of data relationships using Venn diagrams where sets represent data objects and overlapping regions represent relationships. This visual copying transforms complex text-based relationship constructions into intuitive graphical representations, allowing users to understand and construct relationships without dealing with complex query syntax or table structures.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The Venn diagram serves as an intermediary between the user and the complex database relationship structure. By representing relationships through visual set theory notation, the intermediary translates user-friendly visual selections into the underlying complex query logic, shielding users from the complexity while maintaining functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If detailed relationship specifications are provided, then query accuracy is improved, but user understanding and error detection become more difficult

Engineering Contradiction:
Improvequery accuracyVSAvoiderror detection difficulty
Core Design Contradiction:
Measurement precisionVSDifficulty of detecting and measuring

Solution Approach 1:

The patent employs color-coding within the Venn diagrams to indicate different data objects and their relationships. By assigning distinct colors to different sets and using shading to indicate overlaps, the system provides visual feedback that helps users detect errors in relationship specifications without requiring them to parse complex text-based queries, thus maintaining accuracy while improving error detection.

Inventive Principle:
Principle #32Color changes

3Adaptability or versatility

If multiple data objects are related together, then comprehensive data retrieval is achieved, but cognitive load and confusion increase

Engineering Contradiction:
Improvedata retrieval capabilityVSAvoidease of use
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent segments complex multi-object relationships into individual Venn diagram components, where each data object is represented as a separate set. Users can selectively combine these segmented visual representations to build comprehensive queries, making the process more manageable and less confusing compared to dealing with monolithic relationship specifications.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8959443B2Method and system for presenting a visual representation of the portion of the sets of data that a query is expected to return
Publication Date: 2015.02.17 SALESFORCE INC
  • US8959443B2 patent drawing
  • US8959443B2 patent drawing
  • US8959443B2 patent drawing

AI summary

In an embodiment, a user is provided with a data representation covered by a relationship. For example, the data representation may include a collection of data objects representations. In an embodiment, the data object representations are arranged in a manner so as to indicate rows or records of different data objects that are associated with one another. In an embodiment, portions of the data objects in the collection are indicated as representing the data that is covered by the relationship. In an embodiment, a report representation that is expected to be generated by the report type defined by the user defined relationship is also provided. In an embodiment, a correspondence in indicated between elements of the report representation (e.g., columns in a thumbnail sketch of a report) and the data object representations (e.g., ovals in a Venn diagram).