Enhancement Object Models for Flexible Metadata Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional techniques for modifying existing object models in application platforms require advanced technical skills and result in global changes that affect all instances, necessitating recompilation of the database system and reprogramming of application clients, limiting flexibility and coherence.

Innovation Solution

The introduction of enhancement object models that allow for hierarchical management and isolation of changes, enabling customers to add nodes, actions, and queries at the object model level without affecting the entire system, using metadata repositories and editors to create and merge enhancement object models dynamically.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If APPEND mechanisms are used to change object model definitions at the data dictionary level, then the object model can be modified, but the entire database system must be recompiled and all instances are affected globally

Engineering Contradiction:
Improveobject model modifiabilityVSAvoidsystem recompilation requirement
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the object model into base object models and enhancement object models. Changes are isolated to specific enhancement modules rather than affecting the entire database system. This allows localized modifications without requiring global recompilation, resolving the contradiction between model modifiability and system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts customization capabilities from the core object model definition and places them in separate enhancement object models. These enhancements are stored as distinct metadata entities that can be added, removed, or modified independently, eliminating the need to recompile the entire database system when making changes.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If APPEND mechanisms are used to add fields to object models, then the field can be added, but reprogramming of application clients is required

Engineering Contradiction:
Improvefield addition capabilityVSAvoidclient reprogramming requirement
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent uses metadata copying mechanisms where enhancement object models define additional fields and nodes that are copied or merged into the runtime object model. Application clients interact with the enhanced model through the same metadata interface, eliminating the need for client reprogramming while still adding new fields and functionality.

Inventive Principle:
Principle #26Copying

3Stability of the object's composition

If global changes are made to object models, then system-wide consistency is maintained, but flexibility for localized changes is reduced

Engineering Contradiction:
Improvesystem coherenceVSAvoidlocalized change capability
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent segments changes into localized enhancement modules that can be independently developed, versioned, and activated. Each enhancement object model maintains its own scope and can be applied to specific base object models without affecting other parts of the system, enabling both system coherence and localized flexibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a hierarchical dimension to object model management by introducing enhancement object models that operate at a different level than base object models. This layered approach allows simultaneous maintenance of global system coherence through the base model while enabling localized changes through enhancements, effectively resolving the contradiction by operating in multiple dimensions.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS8650534B2Metaobject enhancement objects
Publication Date: 2014.02.11 SAP SE
  • US8650534B2 patent drawing
  • US8650534B2 patent drawing
  • US8650534B2 patent drawing

AI summary

A system may include acquisition of metadata defining a first object model, the first object model comprising an instance of a metaobject, acquisition of enhancement object metadata defining one or more enhancements to the first object model and associating each of the one or more enhancements with one of one or more stable anchors of the first object model, and creation, based on the metadata defining the object model and the metadata defining the one or more enhancements, of metadata defining an extended object model, the extended object model comprising an instance of the metaobject.