Modularized Application Framework for Enterprise Software

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The development of software updates and new features in existing systems often requires editing the core software, leading to increased development time, potential disruptions to existing functions, and extensive testing that may inconvenience users, as commercial software may not meet specific company needs effectively.

Innovation Solution

A modularized application framework allows for the development and deployment of software updates and new features as separate modules, which can be tested and deployed without altering the core software, enabling selective activation and deactivation of features, remote development, and cloud-based distribution, along with a graphical user interface that decouples modules from the core layout for user accessibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If core software is edited to add new features, then software functionality is improved, but development time increases and system stability deteriorates

Engineering Contradiction:

Improvesoftware functionalityVSAvoiddevelopment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the software into a core framework and separate module. The core framework contains stable, reusable code that should not be modified, while new features are implemented as independent modules that can be added without editing the core. This segmentation allows functionality to be improved through module addition rather than core modification, thereby reducing development time and maintaining system stability.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If core software is edited to add new features, then software functionality is improved, but system stability deteriorates

Engineering Contradiction:

Improvesoftware functionalityVSAvoidsystem stability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extracts new features into a separate module that is independent from the core framework. This extraction ensures that modifications to new features do not affect the stability of the core system. The module can be developed, tested, and deployed separately, maintaining system reliability while adding functionality.

Inventive Principle:

Principle #2Taking out (Extraction)

3Reliability

If extensive testing is performed on new updates, then software reliability is improved, but user access time is lost

Engineering Contradiction:

Improvesoftware reliabilityVSAvoiduser access time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent implements partial testing by allowing the core framework to remain in production while only the new module undergoes testing. This can be achieved through feature flags, A/B testing, or staged rollouts where the module is tested with a subset of users or in a controlled environment. This partial action approach maintains software reliability through thorough module testing while minimizing impact on user access to the overall system.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The patent introduces an intermediary deployment mechanism that allows the module to be tested in isolation from the core framework. This intermediary layer enables controlled testing where the module can be validated without requiring complete system shutdown or user disconnection. The intermediary facilitates gradual integration and reduces user access loss during testing.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Productivity

If modularized framework is used, then development time is reduced, but device complexity increases

Engineering Contradiction:

Improvedevelopment speedVSAvoidsystem architecture complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal module structure that can serve multiple functions and be reused across different features. The module is designed with standardized interfaces and a flexible architecture that allows it to accommodate various functionalities without requiring separate custom code for each feature. This universality reduces development time through code reuse while managing complexity through standardization.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10338908B2Modularized application framework

Publication Date: 2019.07.02 SAP SE

AI summary

Disclosed herein are system, method, and computer program product embodiments for a modularized application framework. The embodiments disclosed herein may be used in enterprise software and development platforms to quickly deploy new applications and updates, using a decoupled modular configuration executed by a core framework. An embodiment operates by loading a first and second module into a framework. Information and/or services may be transferred from the first module to the second module or vice versa using the framework. Then, the first or second module is unloaded from the framework while the other module remains functional.