Web Service Composition Folksonomy for Dynamic Adaptation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In service-oriented architecture, composition applications built using web services become outdated due to changes in business processes, requiring manual and time-consuming redesign, prone to human error, and existing ontologies fail to provide a complete picture of relationships between web services due to lack of seamless automation for maintaining relationships.

Innovation Solution

A system that collects usage history and user input to build and modify composition applications, utilizing a folksonomy to recommend candidate services based on system knowledge, including a data collection component, monitoring component, and composition design application that interacts with users to enhance service relationships.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual review and redesign of composition applications is performed to keep up with business process changes, then the composition applications can be updated to reflect current business needs, but the process is time-consuming and prone to human error

Engineering Contradiction:

Improveability to update composition applicationsVSAvoidtime required for manual redesign

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system enables automatic self-updating of composition applications by monitoring web service changes and business process definitions, then automatically adjusting the composition applications without requiring manual intervention. The system serves itself by detecting changes and applying updates autonomously.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system implements continuous monitoring of web service changes and business process definitions, using this feedback to automatically update composition applications. The monitoring component provides real-time feedback about changes, enabling the system to adapt dynamically without manual review.

Inventive Principle:

Principle #23Feedback

2Adaptability or versatility

If manual review and redesign of composition applications is performed to keep up with business process changes, then the composition applications can be updated to reflect current business needs, but human error increases the risk of incorrect updates

Engineering Contradiction:

Improveability to update composition applicationsVSAvoidaccuracy of updates

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs automatic self-updating by monitoring web service changes and business process definitions, then automatically adjusting composition applications without human intervention. This eliminates human error in the update process while maintaining high reliability through automated, deterministic updates.

Inventive Principle:

Principle #25Self-service

3Stability of the object's composition

If a rigid ontology format is used to define web service relationships, then the ontology structure remains stable and manageable, but new services cannot be seamlessly associated or relationships cannot be dynamically updated

Engineering Contradiction:

Improveontology structure stabilityVSAvoidability to associate new services

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system transforms the rigid ontology into a dynamic structure that can automatically adapt to new web services and relationships. The ontology is continuously updated based on monitored changes in web service definitions and business process requirements, enabling seamless association of new services while maintaining structural stability through automated processes.

Inventive Principle:

Principle #15Dynamics

4Ease of manufacture

If existing ontologies are used to define web service relationships, then the ontology provides a framework for organizing services, but the ontology does not provide a complete picture of relationships due to lack of automated maintenance

Engineering Contradiction:

Improveontology framework availabilityVSAvoidcompleteness of service relationships

Core Design Contradiction:

Ease of manufactureVSLoss of information

Solution Approach 1:

The system implements continuous monitoring of web service changes and business process definitions, using this feedback to automatically update and complete the ontology. The monitoring component provides real-time information about actual service relationships, enabling the ontology to reflect the complete and current picture of service relationships rather than relying on static, potentially incomplete definitions.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS9098799B2Tooling for implementing business processes using web services

Publication Date: 2015.08.04 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

Business processes are implemented using a collection component for storing system knowledge comprising usage history and user input relative to activities within community of users, where the system knowledge comprises at least a folksonomy. At least one of a user client component interacts with the data collection component to enable a corresponding user to contribute user-derived information to the folksonomy and a monitoring component monitors activities associated with the community of users and interacts with the data collection component to contribute usage information to the system knowledge. Still further, a composition design application interacts with a user to build and/or modify processes built using services, wherein the composition design application recommends candidate services that can implement aspects of the business processes based upon information derived from the system knowledge.