Dynamic Enterprise Application Optimization via Service Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing optimized enterprise applications is challenging due to sparse information on their impact on business processes, requiring effective capture and recording of both functional and non-functional business requirements, and the need for seamless integration and maintenance of platform services and business rules, especially for non-technical users.

Innovation Solution

A computer-implemented system that captures user requirements, including non-functional aspects, and generates customizable computer-accessible objects using Service-Oriented Architecture (SOA), optimizing enterprise applications by creating a deployment model and dynamically customizing processes and services to improve reliability and performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If enterprise applications are developed using traditional methods, then development capability is maintained, but integration of platform services and business rules becomes complex and difficult to maintain

Engineering Contradiction:
Improveease of integrationVSAvoidcomplexity of service integration
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The system segments the enterprise application into reusable business services and platform services. Each service is independently developed, tested, and deployed, allowing for easier integration and maintenance. The business rules are separated as configurable parameters rather than hard-coded logic, enabling independent modification without affecting other services.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The platform services are designed with universal interfaces that can serve multiple business services. The service-oriented architecture allows the same platform service to be reused across different business processes, reducing overall system complexity and improving ease of integration.

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

2Reliability

If detailed business requirements are captured and recorded, then application optimization is improved, but the complexity of requirement analysis and configuration increases

Engineering Contradiction:
Improvereliability of applicationVSAvoidcomplexity of requirement configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces a configuration management layer that acts as an intermediary between business requirements and service configuration. This layer automatically maps business rules to service parameters, translating high-level requirements into actionable configuration settings without requiring manual complex configuration by users.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Business requirements are captured as configurable parameters rather than complex logic. The system allows users to define business rules through parameter changes in a unified configuration interface, simplifying the complexity of requirement analysis while maintaining detailed optimization capabilities.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If non-functional requirements are captured and optimized, then application performance improves, but the difficulty of detecting and measuring performance increases

Engineering Contradiction:
Improveapplication performanceVSAvoiddifficulty of performance measurement
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements automated performance monitoring and feedback mechanisms that continuously measure non-functional requirements such as response time, throughput, and resource utilization. The feedback loop automatically adjusts service configurations based on measured performance, making performance detection and measurement systematic rather than manual.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Manual performance measurement methods are replaced with automated instrumentation and monitoring systems. The system embeds measurement capabilities within services themselves, allowing performance data to be collected automatically without requiring separate manual measurement processes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Adaptability or versatility

If enterprise applications are dynamically optimized, then adaptability improves, but the complexity of deployment and maintenance increases

Engineering Contradiction:
Improveadaptability of applicationVSAvoidcomplexity of deployment
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system enables dynamic optimization by allowing service configurations to be modified at runtime without requiring application redeployment. Business rules and service parameters can be adjusted dynamically based on changing requirements, improving adaptability while maintaining deployment simplicity through centralized configuration management.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary configuration setup during the development phase, where service templates and default configurations are pre-defined. This preliminary action simplifies subsequent deployment and maintenance operations, as only minimal configuration changes are needed for dynamic optimization rather than complete reconfiguration.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10402399B2Computer implemented system and method for dynamically optimizing business processes
Publication Date: 2019.09.03 NUWAFIN HLDG
  • US10402399B2 patent drawing
  • US10402399B2 patent drawing
  • US10402399B2 patent drawing

AI summary

A computer implemented system for dynamically optimizing enterprise applications, have been disclosed. The system includes a capturing module configured to capture at least the user requirements including non functional requirements, and definitions corresponding to an enterprise application to be deployed. The system further includes an identifier for identifying at least the processes and services corresponding to each of the user requirements. The identified processes are subsequently customized and, a plurality of customizable computer accessible objects are generated. A model, comprising the customizable computer accessible objects is created. The model is a representation of the computer infrastructure required for successful deployment of the application. The computer accessible objects are dynamically and iteratively optimized depending upon their performance.