Collaborative Annotations for Dynamic Service Modification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Service-based software systems require significant time and effort to modify their functionality, as changes necessitate redevelopment, analysis of system architecture, testing, and redeployment, which is costly and time-consuming.

Innovation Solution

The introduction of a collaborative annotation framework that allows users to dynamically modify existing standard-based systems by associating annotations with messages, specifying constraints for service interactions, invocation orders, and conditions, enabling real-time interpretation and execution of these annotations to alter system functionality without redeveloping the system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If service-based systems are configured according to a specified standard with extensive planning, coding, and testing, then the system reliability and functionality are improved, but the development time and cost increase significantly

Engineering Contradiction:
Improvesystem functionalityVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-defining service templates with standard interfaces, behaviors, and configurations before actual system deployment. These templates are created in advance and can be automatically instantiated when needed, eliminating the need for extensive planning and coding during system development. The templates encapsulate common service patterns that can be reused across different service-based systems.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent utilizes parameter changes by allowing service templates to be configured through parameter specification rather than full system redesign. When system requirements change, individual service parameters can be modified independently without affecting the entire system architecture. This enables rapid adaptation to new requirements while maintaining system stability and reducing redevelopment time.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If service-based systems undergo redevelopment to meet changed requirements, then the system adaptability is improved, but the redevelopment cost and complexity increase

Engineering Contradiction:
Improvesystem adaptabilityVSAvoidredevelopment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the service-based system into independent, modular service templates. Each template represents a discrete functional unit that can be developed, modified, and deployed independently. When requirements change, only the affected service templates need to be updated rather than the entire system, significantly reducing redevelopment complexity. The segmentation also enables parallel development and easier testing of individual services.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements universality through service templates that are designed to be multi-functional and reusable across different contexts. A single service template can serve multiple purposes by configuring different parameters, eliminating the need to create separate services for similar functions. This universal approach reduces the number of services needed and simplifies system maintenance while maintaining high adaptability to changing requirements.

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

3Reliability

If extensive testing and analysis are performed during system redevelopment, then the system reliability is maintained, but the time and skill requirements increase

Engineering Contradiction:
Improvesystem reliabilityVSAvoidease of redevelopment
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies preliminary action by pre-configuring service templates with built-in validation rules, standard interfaces, and proven configurations that have already been tested and verified. This preliminary preparation ensures that services instantiated from these templates inherit reliability characteristics without requiring extensive re-testing. The templates encapsulate best practices and known working configurations that maintain system reliability while reducing testing effort during redevelopment.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If service-based systems are modified to add new functionality, then the system versatility is improved, but the deployment time and effort increase

Engineering Contradiction:
Improvesystem versatilityVSAvoiddeployment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent utilizes parameter changes to add new functionality by modifying service template parameters rather than creating entirely new services. When new functionality is needed, existing service templates can be instantiated with different parameter values or configurations, enabling rapid deployment of new capabilities. This approach avoids the time-consuming process of developing, testing, and deploying new service code from scratch.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent applies preliminary action by pre-defining service templates that can be quickly instantiated with different configurations to provide new functionality. These templates are prepared in advance with all necessary code, interfaces, and validation logic, allowing new services to be deployed by simply configuring parameters rather than writing code. This dramatically reduces deployment time while adding system versatility.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9021456B2Using collaborative annotations to specify real-time process flows and system constraints
Publication Date: 2015.04.28 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9021456B2 patent drawing
  • US9021456B2 patent drawing
  • US9021456B2 patent drawing

AI summary

A method of modifying an existing standard-based system using collaborative annotations can include associating an annotation with a message of the standard-based system. The message can correspond to a first service and the annotation can specify at least one of a second service. The method further can include intercepting the message and executing the annotation. At least one of the second service can be automatically invoked according to the annotation.