Service Adaptation Layer for Enterprise Software Entities

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is a need for systems and methods that bridge the gap between scenario-specific user interface requirements and business logic encapsulated in business objects during the user interface construction process, while also enabling adaptation of service entities using a declarative approach in a service framework to harmonize fine-granular user interface views with coarse external service levels.

Innovation Solution

The solution involves a method and system for adapting software entities using a declarative approach in a service framework, which includes retrieving software entities from a repository, receiving user declarations for adaptation, adapting the entities based on these declarations, and storing the adapted entities in another repository. This is facilitated by a computer program product with instruction sets for entity retrieval, declaration reception, adaptation, and storage, utilizing a service adaptation layer and user interface pattern engine to enable adaptation of service entities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service entities are designed to expose functionality of individual applications, then they provide stable interfaces and maximum reusability, but they are too limited to be efficient building blocks for enterprise-wide business processes

Engineering Contradiction:
Improveenterprise-wide business process efficiencyVSAvoidservice entity structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments service entities into two distinct layers: adapted service entities (fine-grained, scenario-specific) and original service entities (coarse-grained, reusable). This segmentation allows the system to maintain reusable core service entities while creating specialized adapted versions for specific business scenarios without modifying the original entities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an adaptation layer as an intermediary between the original service entities and user interface scenarios. This adaptation layer contains adaptation logic that transforms generic service entities into scenario-specific adapted service entities, enabling enterprise-wide processes without directly modifying the core service entities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If business logic is encapsulated in business objects with stable interfaces, then maximum reusability is achieved, but scenario-specific user interface requirements cannot be met

Engineering Contradiction:
Improveuser interface scenario adaptabilityVSAvoiduser interface construction
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent performs adaptation actions in advance by creating adapted service entities from original service entities before they are needed in specific user interface scenarios. The adaptation layer pre-processes service entities to match various scenario requirements, so when user interfaces need to access business logic, pre-adapted entities are already available.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The adaptation layer acts as an intermediary that sits between the stable business logic layer and the variable user interface layer. It translates between the stable business object interfaces and scenario-specific UI requirements without requiring changes to either side, enabling ease of operation for UI construction.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If service entities are adapted to meet specific scenario requirements, then user interface requirements are satisfied, but the stability and reusability of original service entities may be compromised

Engineering Contradiction:
Improvescenario-specific adaptabilityVSAvoidservice entity stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent creates adapted service entities as copies or derivatives of original service entities rather than modifying the originals. The adaptation layer generates new entity instances that inherit from or reference the original entities, ensuring that scenario-specific adaptations do not compromise the stability and reusability of the source entities.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

By segmenting the service entity system into original entities and adapted entities, the patent ensures that modifications and adaptations occur in the derived entities while the original entities remain unchanged and stable. This segmentation maintains reliability of core entities while enabling adaptability in derived entities.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7810102B2Service adaptation of the enterprise services framework
Publication Date: 2010.10.05 SAP SE
  • US7810102B2 patent drawing
  • US7810102B2 patent drawing
  • US7810102B2 patent drawing

AI summary

Systems, methods, and computer program products are provided for adapting service entities using a declarative approach in a service framework. In accordance with one implementation, a method is provided for adapting service entities. The method includes the steps of retrieving at least one software entity from a first repository in response to a first input and receiving a declaration from a user for adapting the software entity. The method further includes the steps of adapting the software entity to an adapted software entity based on the declaration and storing the adapted software entity in a second repository.