Verticalization Layer for Terminology Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing ERP applications face inefficiencies in development cycles due to the need for software developers and linguistics professionals to work together on incorporating different terminologies, leading to paused development and the requirement for new software versions when terminology changes occur.

Innovation Solution

Implementing an application layer and a verticalization layer with a verticalization data structure that allows for the rendering of source objects using text strings associated with the current terminology, enabling independent development and easy modification of terminology without requiring new software versions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If software developers and linguistics professionals work together to incorporate different terminologies, then terminology accuracy is improved, but development cycle time increases

Engineering Contradiction:
Improveterminology accuracyVSAvoiddevelopment cycle time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent segments the software architecture into distinct layers: an application layer containing business logic and a presentation layer containing terminology. This segmentation allows linguistics professionals to work on the presentation layer independently while developers focus on the application layer, eliminating the need for coordinated pauses and enabling parallel development workflows.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a terminology repository as an intermediary component that stores terminology data separately from the application logic. This repository acts as a mediator between the presentation layer and the application layer, allowing terminology to be updated independently and automatically reflected in the application without requiring developer intervention or coordination.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If new software versions are released to support terminology changes, then terminology adaptability is improved, but software version complexity increases

Engineering Contradiction:
Improveterminology adaptabilityVSAvoidsoftware version complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts terminology from the core application code and places it in a separate presentation layer with its own repository. This extraction allows terminology to be modified, added, or removed without affecting the application layer, eliminating the need to release new software versions for terminology changes and reducing version complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements a dynamic terminology system where the presentation layer can be configured at runtime to use different terminology sets from the repository. This dynamic configuration allows the software to adapt to different terminologies without requiring recompilation or new versions, providing flexibility while maintaining a single stable application version.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20240303136A1Text verticalization in a software application
Publication Date: 2024.09.12 SAP SE
  • US20240303136A1 patent drawing
  • US20240303136A1 patent drawing
  • US20240303136A1 patent drawing

AI summary

Various examples are directed to systems and methods of generating a user interface in a computing system. The computing system may execute a software application comprising a plurality of source objects. A verticalization layer of the software application may receive a request to modify a terminology used by the software application to render source objects from a first terminology to a second terminology. The verticalization layer may access a verticalization object associated with the first source object and the second terminology to obtain at least one second terminology text string associated with the first source object and the second terminology. The verticalization layer may replace the at least one text string at the verticalization data structure with the at least one second terminology text string.