Service Mapping Blueprints for Efficient Customization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing applications and services lack sufficient customization options, requiring a profound understanding of underlying processing logic and are inefficient and error-prone to rebuild, limiting user customization and adaptation.
Innovation Solution
A service mapping and composition infrastructure (SMACI) that recomposes services based on metadata and traced interactions, allowing users to create tailored services and applications efficiently, leveraging metadata and business semantics to derive insights and automate service mapping and composition.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If applications and services are rebuilt manually to achieve customization, then specific user needs can be met, but the process is inefficient, error-prone, and requires profound understanding of underlying processing logic
Solution Approach 1:
The patent uses service blueprints that capture and store the processing logic of existing services as reusable templates. These blueprints copy the essential service logic, data flows, and processing steps into a standardized format that can be referenced and modified without manually rebuilding services from scratch, thereby improving both customization capability and rebuilding efficiency
Solution Approach 2:
The system performs preliminary analysis and decomposition of service logic into standardized blueprints before customization is needed. By pre-processing services into reusable templates with defined processing steps, data entities, and logic flows, the system eliminates the need for time-consuming manual analysis during customization, significantly improving productivity
2Adaptability or versatility
If manual rebuilding of services is performed to achieve desired customization, then specific service requirements can be met, but costs increase and errors are introduced
Solution Approach 1:
Service blueprints copy proven, working service logic into standardized templates that can be reused across multiple customizations. This copying mechanism ensures that proven processing logic is preserved accurately while allowing controlled modifications, reducing errors compared to manual rebuilding and lowering implementation costs
Solution Approach 2:
The system enables customization through parameter changes within the standardized blueprint framework rather than structural modifications. Users can adjust service parameters, data mappings, and configuration settings within the template, maintaining reliability by preserving the core proven logic while achieving desired customizations
3Ease of operation
If predefine adaptation options are used for service customization, then implementation is straightforward, but customization scope is limited and insufficient for desired modifications
Solution Approach 1:
The patent segments service logic into discrete, standardized components within blueprints, including processing steps, data entities, and logic flows. This segmentation allows users to modify specific segments independently while maintaining the overall service structure, providing both ease of operation through modular changes and extended customization scope beyond predefined options
Solution Approach 2:
Service blueprints act as an intermediary layer between predefined service templates and user customization requirements. The blueprints provide a standardized intermediate representation that bridges the gap between rigid predefined options and flexible customizations, enabling straightforward implementation through the template framework while achieving extensive customization through blueprint modifications
Data Source
AI summary
A system and method including receiving a request to map a first service accessible on a first application stack; determining, based on a combination of metadata of the first service and other services in the first application stack that are related to the first service, metadata associated with entities in the first application stack, and trace data associated with data flows between the entities, a complete mapping of the first service, the other services, and the entities comprising business object representations of the first service and business object representations of other services in the first application stack; deriving, based on the determined complete mapping, service mapping information for the first application stack; and persisting the generated service mapping information and the determined complete mapping in a persistency.


