Functional Dependency Trees for BI Abstraction Layers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current abstraction layers in Business Intelligence tools do not effectively represent dependencies between analysis objects and dimension objects, leading to ambiguity and a lack of intuitive understanding of underlying relationships, which complicates data querying and analysis.

Innovation Solution

Implementing a functional dependency tree within the abstraction layer that expresses relationships between dimension objects through properties, allowing for the definition of functionally-dependent analysis objects and enabling explicit or implicit navigation between them.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If analysis objects are considered orthogonal to one another in the abstraction layer, then the abstraction layer provides a simplified interface for users, but it fails to represent actual relationships between dimension objects in the underlying physical tables

Engineering Contradiction:
Improveease of queryingVSAvoidloss of relationship information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent introduces functional dependency trees as an intermediary structure between the abstraction layer and the physical database schema. This mediator captures relationships between dimension objects (such as transitive dependencies and fan traps) that are lost in the orthogonal abstraction layer, while still allowing users to query using simplified analysis objects. The functional dependency tree acts as a bridge that preserves relationship information without exposing database complexity to users.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If functional dependencies are declared only between dimension objects associated with the same analysis object, then the system maintains simplicity in dependency management, but it cannot represent relationships between dimension objects of different analysis objects

Engineering Contradiction:
Improvecomplexity of dependency managementVSAvoidability to represent relationships
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent implements nested functional dependency trees where dimension objects can have dependencies on other dimension objects through multiple levels of analysis objects. The functional dependency tree structure allows dimension objects from different analysis objects to be linked through transitive dependencies, creating a nested hierarchy that represents complex relationships while maintaining manageable complexity through the tree structure.

Inventive Principle:
Principle #7Nested doll (Nesting)

3Loss of information

If complex static aliases are used to represent relationships between dimension objects, then relationships can be represented explicitly, but the system becomes more complex and less intuitive

Engineering Contradiction:
Improverepresentation of relationshipsVSAvoidcomplexity of abstraction layer
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent extracts relationship information from the physical database schema and represents it separately in functional dependency trees within the abstraction layer. By taking out the relationship representation from the complex static alias approach and placing it in a dedicated functional dependency structure, the system maintains explicit relationship representation while reducing overall abstraction layer complexity. Users can navigate relationships through the functional dependency tree without dealing with complex alias management.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8260825B2Functionally-dependent analysis objects
Publication Date: 2012.09.04 SAP IRELAND LTD
  • US8260825B2 patent drawing
  • US8260825B2 patent drawing
  • US8260825B2 patent drawing

AI summary

A system may include a database of physical data tables, a logical database schema of logical entities associated with the physical data tables, and an abstraction layer comprising a plurality of dimension objects mapped to the logical entities, at least one of the plurality of dimension objects comprising one or more properties associating the at least one of the plurality of dimension objects to one or more others of the plurality of dimension objects.