Self-Constructing Service-Oriented Software Platform

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for building software platforms for service-oriented development and management do not leverage self-produced, service-oriented artifacts, making customization and construction impractical or impossible at a granular level, missing out on the benefits of service-oriented architecture.

Innovation Solution

A method that constructs a software system using its own service-oriented artifacts and functionality, allowing users to customize and extend features by applying the same tools provided to end-users, with a core module (Kernel) managing metadata, logging, cache, and other services, enabling transparent distribution and event broadcasting across distributed nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service-oriented artifacts are not used in system construction, then system construction follows traditional methods, but customization and construction become impractical or impossible at granular level

Engineering Contradiction:
ImprovecustomizabilityVSAvoidconstruction practicality
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system uses its own service-oriented artifacts and functionality to construct itself. The Kernel and management tools are built using the same service modules and frameworks that they provide to end users, enabling the system to customize and extend its own capabilities through self-service mechanisms.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The service-oriented artifacts serve dual purposes: they are both the building blocks for constructing the system and the deliverables provided to end users. This universality allows the same frameworks and modules to be reused for both system construction and user-facing functionality, enabling granular customization.

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

2Productivity

If traditional construction methods are used, then system structure is simpler, but construction and customization time increases significantly

Engineering Contradiction:
Improveconstruction speedVSAvoidcustomization time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system pre-configures the Kernel and management tools with service-oriented frameworks and artifacts during system initialization. These pre-prepared components can be rapidly deployed and customized later, significantly reducing both initial construction time and subsequent customization time compared to building from scratch.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements nested service modules where core functionality is embedded within reusable frameworks. This nested structure allows higher-level services to inherit and build upon lower-level services, enabling rapid construction through composition and reducing overall development time.

Inventive Principle:
Principle #7Nested doll (Nesting)

3Reliability

If service-oriented artifacts are leveraged in system construction, then system quality and flexibility improve, but system complexity increases

Engineering Contradiction:
Improvesystem qualityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments its architecture into distinct service modules and frameworks that can be independently developed, deployed, and managed. This segmentation allows complex functionality to be broken down into manageable units, improving system quality through modular verification while managing complexity through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The Kernel acts as an intermediary layer that manages the complexity of service-oriented artifacts. It provides standardized interfaces and coordination mechanisms that simplify the interaction between multiple service modules, maintaining system quality while abstracting away the underlying architectural complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7581205B1System and method of implementing a customizable software platform
Publication Date: 2009.08.25 NEXTAXIOM TECH
  • US7581205B1 patent drawing
  • US7581205B1 patent drawing
  • US7581205B1 patent drawing

AI summary

Methods, systems, frameworks and software products are disclosed for the construction of a service-oriented software platform that can be used for the management, development and service-oriented composition of any software service. The innovative aspect of the system outlined is its uniqueness in using the development capability that it provides to the end-users of the system and its artifacts in constructing the functionality of the system. The result is a highly customizable platform where the behavior of the platform can be overwritten or easily customized at a granular level using the basic functionality of the platform.