Build-independent Software Framework for Cloud Adapter Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing frameworks for adding custom adapters in cloud computing environments require a specific Integrated Development Environment (IDE), making the process cumbersome and increasing the Total Cost of Ownership (TCO), and necessitate continuous support for the latest IDE versions, which is time-consuming and error-prone.

Innovation Solution

A build-independent software framework that accesses information from a build automation tool via an implementation registry, automatically creates and validates custom adapters using APIs, and deploys them in the cloud computing environment, eliminating the need for a particular IDE.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If a specific IDE is required for adapter development, then adapter creation can be standardized, but developer flexibility decreases and TCO increases

Engineering Contradiction:
Improveadapter creation standardizationVSAvoiddeveloper flexibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent introduces a build automation tool as an intermediary between the adapter creation process and the final adapter product. This intermediary handles the build process independently of any specific IDE, allowing developers to use their preferred IDE while maintaining standardized adapter creation through the build automation tool's configuration files and build scripts.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the framework supports the latest IDE versions continuously, then compatibility is maintained, but maintenance time and error risk increase

Engineering Contradiction:
ImproveIDE version compatibilityVSAvoidmaintenance time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent extracts the build process from the IDE environment entirely, placing it in the hands of a standalone build automation tool. This separation means the framework no longer needs to support or track multiple IDE versions, as the build automation tool handles compilation and assembly independently. Compatibility is maintained through the build tool's configuration rather than IDE version support.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If manual IDE configuration is used for adapter development, then fine-grained control is achieved, but development time and complexity increase

Engineering Contradiction:
Improveconfiguration controlVSAvoiddevelopment process complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent employs preliminary action by using configuration files and build scripts that are prepared in advance. These pre-configured files contain all necessary build instructions, dependencies, and settings, allowing the build automation tool to automatically execute the adapter creation process without requiring manual IDE configuration during development. This reduces both development time and process complexity.

Inventive Principle:
Principle #10Preliminary action

4Extent of automation

If build automation tools are integrated into the framework, then adapter creation is automated, but initial setup complexity increases

Engineering Contradiction:
Improveadapter creation automationVSAvoidframework setup complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent uses copying by leveraging existing, well-established build automation tools and their standard configuration formats. Rather than creating a custom build system from scratch, the framework adopts and adapts proven build automation approaches, reducing initial setup complexity while maintaining high automation capabilities. The build automation tool's existing infrastructure handles the complexity, not the framework itself.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11740894B2Build-independent software framework for creating custom adapters
Publication Date: 2023.08.29 SAP SE
  • US11740894B2 patent drawing
  • US11740894B2 patent drawing
  • US11740894B2 patent drawing

AI summary

According to some embodiments, methods and systems may be associated with a cloud computing environment having an integration service (e.g., associated with a Software-as-a-Service or a Platform-as-a-Service). The system may include a build automation tool and a build-independent software framework coupled to the build automation tool. The build-independent software framework may access, via an implementation registry, information from the build automation tool that represents a custom adapter for the integration service. The build-independent software framework may then automatically create the custom adapter via a build Application Programming Interface (“API”) and automatically validate the created custom adapter via a validation API. The system can then arrange to deploy a concrete implementation of the custom adapter in the cloud computing environment. According to some embodiments, the software framework is “build-independent” because it does not require that an adapter designer use a particular Integrated Development Environment (“IDE”).