Automated Web Service Code Generation via Pre-built Frameworks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The development of web services is a time-consuming and human-intensive process, often resulting in monolithic applications that are tightly coupled and difficult to modify, leading to increased development costs and a competitive disadvantage for organizations.

Innovation Solution

A holistic system and method that uses pre-built, abstract frameworks for automated code generation across multiple layers, allowing for dynamic assembly of web services without manual coding, and enabling modification of business rules without affecting other application layers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If web services are built manually at application level, then business rules and information can be hard coded, but the development process becomes time-consuming and human-intensive

Engineering Contradiction:
Improvebusiness rules encapsulationVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by providing pre-built abstract frameworks and code templates before the actual web service development begins. The system pre-defines service layers, data access objects, and business rule structures that can be automatically instantiated, eliminating the need to manually code these foundational elements and significantly reducing development time while maintaining business rule encapsulation

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements self-service through automated code generation capabilities where the system automatically generates web service code, data access layers, and business rule implementations based on high-level service definitions. This automation reduces human intervention and accelerates the development process while ensuring consistent encapsulation of business rules across all generated services

Inventive Principle:
Principle #25Self-service

2Ease of manufacture

If web services are built manually, then applications can be created, but they become monolithic and tightly coupled making subsequent modifications difficult

Engineering Contradiction:
Improveapplication creationVSAvoidmodifiability
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent applies segmentation by dividing the web service architecture into distinct, loosely-coupled layers including service definition layer, data access layer, business rule layer, and presentation layer. Each layer is independently developable and modifiable through automated code generation, allowing specific layers to be modified without affecting others, thus maintaining ease of application creation while dramatically improving adaptability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements universality through a unified framework that can generate multiple types of web services across different layers using the same automated code generation engine. The system provides universal templates and patterns that work across various service scenarios, enabling consistent application creation while allowing flexible adaptation through configuration rather than structural changes

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

3Productivity

If services are built without automated tools, then development can proceed, but any modification requires costly re-engineering

Engineering Contradiction:
Improveservice deployment speedVSAvoidre-engineering complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements self-service through automated code generation that continuously maintains and updates web service code based on service definitions. When modifications are needed, the system automatically regenerates the affected code layers, eliminating the need for manual re-engineering and reducing both productivity losses and complexity of modifications

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent applies feedback through an automated code generation system that continuously monitors service definitions and generates appropriate code updates. The system provides feedback loops where changes in service definitions automatically trigger code regeneration, ensuring consistency and eliminating the need for costly manual re-engineering while maintaining high productivity

Inventive Principle:
Principle #23Feedback

4Stability of the object's composition

If micro level architecture is made rigid, then system stability is achieved, but expansion and modification become extremely difficult

Engineering Contradiction:
Improvesystem stabilityVSAvoidexpansion capability
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent applies dynamics by making the micro-level architecture flexible through automated code generation. The system allows service definitions and configurations to be dynamically modified, and the code generation engine automatically adapts the underlying code structure to reflect these changes, maintaining system stability through consistent generation while enabling easy expansion and modification

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8631386B2System and method for automating the development of web services
Publication Date: 2014.01.14 EOS SOFTWARE
  • US8631386B2 patent drawing
  • US8631386B2 patent drawing
  • US8631386B2 patent drawing

AI summary

A system and method for developing web services that includes three frameworks: a Design Time Framework, an Object-Service Framework, and a Run Time Framework. In the Design Time Framework, the system and method includes receiving a schema in a descriptive markup language from a user and generating source code artifacts in an object oriented programming language based on the schema. In the Object-Service Framework, the system and method includes relating the generated source code artifacts to a set of pre-built runtime services. Finally, in a Run Time Framework, the system and method includes providing the set of runtime services, wherein the runtime services interact with the generated source code artifacts through the relationship defined by the Object-Service Framework.