Composite Application Framework for Context-Specific Service Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing integration platforms for composite applications, such as the SAP Enterprise Portal, face challenges in adapting generic services to various business objects, as these services are not directly applicable and require customization, failing to adapt to the specific collaboration intent and naming conventions of different business contexts.

Innovation Solution

A computer-implemented framework for composite applications that includes an object access layer, a business object modeling layer with a collaboration services module, and a service layer, enabling the derivation of object-specific services from generic collaboration services based on modeled contexts, allowing for customization and adaptation to specific business objects and intents.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If generic collaboration services are used for multiple business objects, then service reusability is improved, but adaptability to specific business contexts deteriorates

Engineering Contradiction:
Improveservice reusabilityVSAvoidadaptability to business context
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent applies local quality by allowing generic collaboration services to be customized with business-specific properties, naming conventions, and context-specific behaviors. Each business object can have tailored service instances that inherit from generic services while adding local adaptations for specific business contexts, workflows, and semantics.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements dynamics by enabling the collaboration service framework to adapt its behavior based on the specific business object and context. The system dynamically configures service parameters, naming, and functionality according to the business context, allowing the same generic service to behave differently for different business objects while maintaining a unified underlying structure.

Inventive Principle:
Principle #15Dynamics

2Device complexity

If generic collaboration services are used across different business objects, then system complexity is reduced, but customization requirements increase

Engineering Contradiction:
Improvesystem complexityVSAvoidcustomization requirements
Core Design Contradiction:
Device complexityVSEase of manufacture

Solution Approach 1:

The patent applies segmentation by dividing the collaboration service functionality into hierarchical layers: generic base services providing core functionality, and business-specific extensions adding customization. This segmentation allows the system to maintain a simple generic core while enabling targeted customization through modular additions for specific business objects.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements universality by designing a framework where a single generic collaboration service infrastructure can serve multiple business objects with different requirements. The universal service layer provides common functionality that can be configured and adapted for various business contexts without requiring separate implementations for each business object.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If collaboration services are directly linked to business objects, then service applicability is improved, but implementation complexity increases

Engineering Contradiction:
Improveservice applicabilityVSAvoidimplementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-configuring generic collaboration services with standard functionality and interfaces before they are linked to business objects. The framework prepares service templates, naming conventions, and contextual configurations in advance, so that when services are linked to specific business objects, the implementation is streamlined rather than requiring complex customization from scratch.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8069437B2Framework for a composite application and a method of implementing a frame work for a composite application
Publication Date: 2011.11.29 SAP SE
  • US8069437B2 patent drawing
  • US8069437B2 patent drawing
  • US8069437B2 patent drawing

AI summary

Methods and apparatus, including computer program products, for a framework for composite applications. A computer-implemented framework for a composite application includes an object access layer to exchange data with enterprise base systems and to present the data to a composite application through a uniform interface, a business object modeling layer including a business object modeler to provide a user interface (UI) for constructing a business object, and a service layer to enable services to the composite application, the service layer including a collaboration services module to enable collaboration services to the composite application, the business object modeling layer linking at least one of the collaboration services associated with the business object to the business object.