Declarative Model for Service Data Transformations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The drafting of custom code for data transformations between services in a sequence of services is time-consuming and requires skilled programmers, especially when multiple transformations are needed for complex tasks.

Innovation Solution

A declarative model is used to specify transformations at the input and output of each service, employing a transformation class field and parameter fields, allowing services to interpret and perform transformations without altering underlying code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If custom code is drafted for each data transformation between services, then the transformations can be performed accurately, but the development time increases and skilled programmers are required

Engineering Contradiction:
Improvetransformation accuracyVSAvoiddevelopment time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent uses templates to define transformation operations. Instead of writing custom code for each transformation, pre-defined transformation templates are copied and configured with specific parameters. This allows accurate transformations to be performed without writing new code, thus reducing development time while maintaining transformation accuracy.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent allows transformation operations to be configured by changing parameters within templates rather than modifying the underlying code structure. By parameterizing transformations, the system can adapt to different data formats and services without requiring custom programming, thereby reducing both development time and the need for skilled programmers while preserving transformation accuracy.

Inventive Principle:
Principle #35Parameter changes

2Manufacturing precision

If custom code is drafted for each data transformation between services, then the transformations can be performed accurately, but the complexity of the system increases

Engineering Contradiction:
Improvetransformation accuracyVSAvoidsystem complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent implements universal transformation templates that can handle multiple transformation scenarios. Instead of creating separate custom code for each transformation type, a single template system serves multiple purposes by configuring different parameters. This reduces system complexity while maintaining the ability to perform accurate transformations across various services and data formats.

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

Solution Approach 2:

The patent introduces transformation templates as an intermediary layer between services. Rather than having services directly communicate with custom-coded transformations, the templates act as a standardized mediator that simplifies the transformation process. This reduces system complexity by providing a uniform interface for all transformations while preserving accuracy through proper configuration.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If transformation declarations are made available at each service, then transformations can be performed without modifying underlying code, but the system requires a declarative model infrastructure

Engineering Contradiction:
Improvecode flexibilityVSAvoidinfrastructure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent establishes transformation declarations and templates in advance, before the actual transformation operations are needed. By pre-defining transformation logic and parameters, the system enables flexible adaptations without requiring code modifications during runtime. The preliminary setup creates a reusable framework that simplifies future transformations while managing infrastructure complexity through standardization.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7869585B2Declarations for transformations within service sequences
Publication Date: 2011.01.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7869585B2 patent drawing
  • US7869585B2 patent drawing
  • US7869585B2 patent drawing

AI summary

A declarative model for specifying appropriate transformations that may occur at the input and output of each service of a sequence of services that accomplish a more complex task. Each of the services may have access to the appropriate transformation declarations, and may interpret the declarations to thereby be appropriate directed on transforms to occur in its input data and/or output data. In order to change a transformation, the transformation declaration may be altered.