Transformation Nodes for Flexible Business Object Data Presentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Model-driven user interfaces in computer-based business systems lack flexibility in data presentation and cannot display the same data in multiple formats, as they are directly tied to the services exposed by business objects, limiting the ability to create sophisticated user interfaces and introduce redundancy issues.

Innovation Solution

The introduction of transformation nodes within the business object hierarchy allows for controlled redundancy and different data presentation modes, enabling multiple formats for user interfaces without requiring redundancy in the backend databases or business objects, and synchronizes data across interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If model-driven user interfaces are used to reflect business object structure, then data integrity and consistency are maintained, but flexibility in data presentation and ability to display multiple formats is lost

Engineering Contradiction:
Improvedata integrityVSAvoiddata presentation flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces transformation nodes as intermediary components between business objects and user interfaces. These transformation nodes act as mediators that receive data from business objects and transform it into different presentation formats, allowing the same data to be displayed in multiple formats (e.g., tabular, graphical, detailed views) without altering the underlying business object structure or compromising data integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If user interface is directly tied to business object services, then implementation complexity is reduced, but ability to create sophisticated interfaces with multiple data formats is limited

Engineering Contradiction:
Improveinterface implementation complexityVSAvoidinterface sophistication
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent segments the interface layer from the business object layer by introducing transformation nodes as independent components. This segmentation allows the business objects to remain simple and focused on data storage while transformation nodes handle the complexity of data transformation and presentation. Each transformation node can be independently configured to provide different interface sophistication levels without affecting the core business object structure.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If redundancy is introduced in user interface to provide multiple data formats, then presentation flexibility is improved, but data redundancy and consistency issues arise

Engineering Contradiction:
Improvedata presentation flexibilityVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

Transformation nodes serve as single points of truth that receive data from business objects and generate all necessary redundant representations. This intermediary approach ensures that only one source of truth exists in the business object, while transformation nodes create the necessary redundancy in presentation formats without introducing data consistency issues, as all transformations are derived from the same source.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7730412B2System and method for model-based user interface using transformation nodes
Publication Date: 2010.06.01 SAP SE
  • US7730412B2 patent drawing
  • US7730412B2 patent drawing
  • US7730412B2 patent drawing

AI summary

Methods and systems to include transformation nodes in a business system are provided. A transformation node may provide controlled redundancy of data within the business object hierarchy. Transformation nodes may store data from core nodes without persistency, and permit different data presentation modes than for the core nodes. When a service call is placed to a transformation node, the transformation node may call corresponding services from associated core nodes.