Projected Business Objects for Role-Specific SOA Modeling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In Service-Oriented Architecture (SOA), designing and developing business objects that function in multiple roles within an application is complex and requires significant time and resources, leading to confusion and inefficiency due to the need for multiple business objects with role-specific data and behaviors, which hinders the creation of reusable object architectures.

Innovation Solution

A system and method for implementing a reusable template entity within a software system, where a template entity with elements related to multiple roles is retrieved from a repository, and based on metadata, a list of elements is determined for state modification to yield a projected entity, allowing for efficient modeling and instantiation of business objects across various roles.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple role-specific business objects are created to handle different functional roles, then the system can accurately model role-specific data and behaviors, but the device complexity and development time increase significantly

Engineering Contradiction:
Improverole-specific functionalityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a parent business object template that can function in multiple roles through configuration rather than instantiation. A single business object template (e.g., Person template) can be projected into different role-specific objects (Employee, Customer, Contractor) by enabling or disabling specific elements based on the desired role, eliminating the need for separate class definitions for each role.

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

Solution Approach 2:

The patent segments the business object into configurable elements that can be independently enabled or disabled through projection. Each business object template contains multiple elements (data fields, behaviors, associations) that can be selectively activated based on the specific role requirements, allowing fine-grained control over role-specific functionality without duplicating the entire object structure.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If multiple role-specific business objects are created to handle different functional roles, then the system can accurately model role-specific data and behaviors, but the development time and resources increase significantly

Engineering Contradiction:
Improverole-specific functionalityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs preliminary configuration by creating comprehensive business object templates that include all possible elements for all potential roles. During development, architects pre-define the template structure with all conceivable data fields, behaviors, and associations, then simply project the appropriate elements for each specific role rather than building from scratch, significantly reducing development time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses projection to create role-specific business objects by copying and adapting elements from parent templates. Instead of creating entirely new objects for each role, the system copies the necessary elements from pre-defined templates and modifies them through configuration, reducing the effort required for object creation and ensuring consistency across roles.

Inventive Principle:
Principle #26Copying

3Device complexity

If a single business object template is used for multiple roles with selective element projection, then the device complexity is reduced, but ensuring data accuracy and completeness for each role becomes more difficult

Engineering Contradiction:
Improvesystem complexityVSAvoiddata accuracy
Core Design Contradiction:
Device complexityVSManufacturing precision

Solution Approach 1:

The patent applies local quality by enabling specific elements within the business object template based on the required role. Each projection configures which data fields, behaviors, and associations are active for that particular role, ensuring that only relevant and accurate elements are present for each specific use case while maintaining the unified template structure.

Inventive Principle:
Principle #3Local quality

4Adaptability or versatility

If elements are selectively enabled or disabled in projected business objects, then the adaptability to different roles is improved, but the difficulty of detecting and measuring the correct configuration increases

Engineering Contradiction:
Improverole flexibilityVSAvoidconfiguration verification
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent incorporates validation mechanisms that provide feedback on the configuration of projected business objects. The system validates that the projected object contains the necessary elements for its intended role and rejects configurations that would result in incomplete or incorrect objects, making it easier to detect and correct configuration errors automatically.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS7890478B2Projected business objects
Publication Date: 2011.02.15 SAP SE
  • US7890478B2 patent drawing
  • US7890478B2 patent drawing
  • US7890478B2 patent drawing

AI summary

A computer-readable medium including instructions for performing a method for implementing a reusable template entity within a software system. The method includes retrieving a template entity from a repository in response to a request, wherein the template entity contains a plurality of elements related to a plurality of roles associated with the template entity and determining, based on metadata related to the at least one template entity and the request, a list of elements from the plurality of elements to undergo state modification. The method further includes adapting the template entity according to the list of elements to yield a projected entity and providing an instance of the projected entity.